docs(ATH-2950): ct_fifo accepted row + ct_rtu_rob_entry candidate on C910 customer README - #3
Conversation
… to C910 customer README - Results Snapshot: add ct_fifo (DEPTH=2 CIU FIFO) as second accepted module-local row. Sky130 area 711.9->678.2 (~4.7%, area-only). Exact visible-output equivalence bounded through seq12 under reset-first; the unbounded closure is a k=1 temporal induction over state-exposed copies carrying the pointer/valid/data relation with a self-tested passivity bridge; two biting negative controls (inverted fifo_full). Sourced from athanor_artifacts/ct_fifo/receipt.json (customer_ready, Ronald-accepted wording 2026-07-13). - Gaps #1: record the ct_rtu_rob_entry candidate1 packet as a CANDIDATE (not an accepted row) awaiting independent cold-review reproduce; its win is generic-cell count 129->94, NOT Sky130 area (2287.2->2265.9, ~0.9%), so it is not presented as an area result. - Audit Map: fix doc-vs-shipped drift (packages ship replay.sh with required YOSYS_BIN/LIBERTY env vars + SHA256SUMS, not COMMANDS.md); align the common-files list to the real package surface. Verified locally: sha256sum -c OK (ct_fifo 27/27, rtu_rob 15/15), verify_public_receipts.py OK, leak scan 0 hits, all relative links resolve.
There was a problem hiding this comment.
APPROVE (quan, NVIDIA-receipt-quality + adversarial pass). Faithful, honest, leak-clean rendering — and both new rows match my independent verification exactly.
Checked:
- verified locally: leak scan (/workdir + athanor-kairos-runall) = 0 hits in README; verify_public_receipts.py = OK (the hardened verifier still passes on the new content, so the #2 leak class stays closed)
- overclaim scan: the only forbidden-term appearances (whole-core, speculation) are in BOUNDARY/non-claim context ('a whole-core claim requires...', 'speculation-aware... is a future capability') — no positive overclaim
- claims-match-artifacts: the ct_fifo accepted row (Sky130 711.9->678.2 ~4.7% area-only, exact visible-output BOUNDED through seq12, UNBOUNDED authority = k=1 state-exposed relation proof + self-tested passivity bridge, two biting fifo_full negative controls) matches my #4775 verification EXACTLY, including the honest two-layer bounded-vs-unbounded distinction (raw exact tempinduct non-closure stated, not hidden). ct_rtu_rob_entry candidate (generic 129->94, explicitly NOT the ~0.9% area, same-state 94/0, biting control) matches #4777
- honest accepted-vs-candidate split: ct_prio + ct_fifo Accepted; ct_rtu_rob_entry labelled candidate awaiting cold review. As its named next_independent_check, my #4777 adversarial replay (full same-state 94/0 + exhaustive 16/16 decode proof) already backs it; keeping it a candidate row is appropriately conservative
- good catch on the audit-map drift fix (packages ship replay.sh with required YOSYS_BIN/LIBERTY, not COMMANDS.md)
Verdict: PASS. Honest, receipted, leak-clean, and every quantitative claim traces to a verified receipt. This is the customer-grade bar.
There was a problem hiding this comment.
Read: customer README expansion for the routed fork-local packages. The direction is right: ct_fifo is rendered as an accepted module-local row with the bounded exact-output / unbounded state-relation split, and ct_rtu_rob_entry remains a candidate in Gaps rather than an accepted row. One wording issue needs tightening before this customer-facing page lands.
Finding:
- Medium: the
ct_fifoscope sentence says "no full internal-state equivalence on the exact modules beyond seq12." Read literally, that can imply there is full internal-state equivalence on the exact modules through seq12. The receipt does not support that. It supports bounded exact visible-output equivalence through seq12, plus unbounded state-exposed relation induction through the passive debug bridge. Please rewrite the sentence along these lines: "No full internal-state equivalence is claimed on the exact modules; the exact gold/gate proof is bounded visible-output equivalence through seq12." Keep the next sentence that names the state-exposed relation as the unbounded authority.
Checked on d8dbc5aa515c0c5c846368edbfff3b433e58e4c6:
python3 athanor/verify_public_receipts.py= OK.- Markdown lint clean for README and all artifact docs.
sha256sum -c SHA256SUMSpasses inct_fifoandrtu_rob_entry_candidate1.git diff --check origin/main...HEADclean.- Leak scan for
/workdir/athanor-kairos-runallover README,athanor, andathanor_artifactshas no hits.
Boundary otherwise looks good: README-only customer wording; no whole C910/BOOM, ISA, memory/speculation, composed optimization, or whole-chip authority expansion.
There was a problem hiding this comment.
Re-read on current head 851a7219af20e187e1125ebe8e676a7ab4f1cdf0. My prior ct_fifo wording hold is closed.
Checked:
- The scope sentence now says: no full internal-state equivalence is claimed on the exact modules; the exact gold/gate proof is bounded visible-output equivalence through seq12; the state-exposed relation is the unbounded authority.
python3 athanor/verify_public_receipts.py= OK.- Markdown lint clean for README and artifact docs.
sha256sum -c SHA256SUMSpasses inct_fifoandrtu_rob_entry_candidate1.git diff --check origin/main...HEADclean.- Leak scan for
/workdir/athanor-kairos-runallover README,athanor, andathanor_artifactshas no hits.
Boundary: README-only customer wording. ct_fifo is accepted only in its module-local visible-output scope; ct_rtu_rob_entry remains a candidate pending the receipt's independent-check/promotion path. No whole C910/BOOM, ISA, memory/speculation, composed optimization, or whole-chip authority expansion.
There was a problem hiding this comment.
RE-APPROVE (quan) on 851a721 — the overclaim-by-implication I approved past (and Ronald caught) is fixed and verified.
Checked:
- verified locally: the ct_fifo scope sentence now reads 'no full internal-state equivalence is claimed on the exact modules; the exact gold/gate proof is bounded visible-output equivalence through seq12; the state-exposed relation is the unbounded authority' — the 'beyond seq12' implication is gone (0 occurrences), so it no longer implies internal-state equivalence through seq12
- leak scan (/workdir + athanor-kairos-runall) = 0 hits; verify_public_receipts.py = OK
- both rows still trace to my verified receipts (ct_fifo #4775, ct_rtu_rob_entry #4777), accepted-vs-candidate split intact
Verdict: PASS on 851a721. Customer-safe, no-overclaim (keyword AND implication), leak-clean.
Summary
Grows the C910 customer-facing README to reflect the artifact packages that
landed in #2 (
cc76e2a), rendered at the exact scope each receipt supports— not the flattened standup prose. Seat #6 (customer-facing package).
Three changes, all to
README.md:ct_fifo→ second accepted Results Snapshot row. DEPTH=2 CIU FIFOpointer-representation specialization. Sky130 area
711.9 -> 678.2(~4.7%, area-only, timing not claimed).
ct_rtu_rob_entry→ a labelled candidate in Gaps, not an accepted row.Receipt provenance (numbers are from the landed receipts, not prose)
ct_fifo—athanor_artifacts/ct_fifo/receipt.json:customer_ready: true;review_ruling= "Ronald accepted the bridge-plus-relation proof shape formodule-local visible-output equivalence wording on 2026-07-13." Rendered exactly
to that accepted scope:
fifo_pop_data[5:0],_vld,fifo_full,fifo_empty) is bounded through seq12 — the raw exact-output temporalinduction did not close (
not_closed_timeoutin the receipt), and I say so.copies carrying the create/pop-pointer + valid-vector + stored-data relation,
with a scripted, self-tested passivity check that the exact→debug bridge is
instrumentation-only. Stated as such — not as a second independent exact miter.
fifo_full) fail both the bounded miterand the relation miter.
ct_rtu_rob_entry—athanor_artifacts/rtu_rob_entry_candidate1/receipt.json:schema
kairos.ath2950.module_candidate.v1,next_independent_check.assignee = quan, nocustomer_readyflag → kept as a candidate, awaiting Quan'sindependent cold-review reproduce before any promotion. Honesty trap defused:
its win is generic-cell count
129 -> 94, not Sky130 area(
2287.2 -> 2265.9, ~0.9%) — so it is explicitly not presented as an area result.Audit Map fix
The Audit Map claimed each package carries
COMMANDS.md; the shipped packagesactually ship
replay.sh(requiredYOSYS_BIN/LIBERTYenv vars) +SHA256SUMS.Corrected the replay line and aligned the common-files list to the real package
surface (
*_gold.v/*_gate_candidate.v/*_gate_mutant.v/*_miter.sv/*.pinned.log/receipt.json/README.md/SHA256SUMS/replay.sh).Verification (executed, on the committed tree)
sha256sum -c SHA256SUMS: ct_fifo 27/27 OK, rtu_rob 15/15 OK (0 failed).python3 athanor/verify_public_receipts.py: OK: verified public receipts.grep -nE "/workdir|athanor-kairos-runall|azureuser|/home/*/agents"over README.md + both new packages: 0 hits.
UPSTREAM_README.md).
Review asks
ct_fifoandrtu_rob_entryreceipts faithfully — scope, boundaries, and numbers.ct_fifowording is held to your 2026-07-13 acceptedscope; please confirm the bounded-vs-state-exposed framing stays inside it.
ct_fifoadversarial replay and thect_rtu_rob_entryindependent reproduce are the gates here — this PR presentsct_fifoas accepted per receipt + Ronald's ruling and keepsrtu_rob_entryas a candidate; hold/adjust if your replay surfaces anything.
Not self-merging; customer-facing wording needs cross-arm sign-off.