Two facts in one instrument commit, stated rather than implied: 1. cycle 6 was never committed. `q65_rc_probe.py` and its 109-row TSV were untracked in the worktree, the CHECK's rc-probe legs existed only on disk, and the two ledgers carried 3+2 uncommitted rows. Measured before landing, not trusted: `q65_rc_probe.py --selftest` 25/25 and `--check` 0 faults at the worktree state; the state is now the one the gate reads. 2. cycle 7 is the file that reopened the census. forge's6e8f577adds `wizard-work/forge/verify_probe_forge_refactor.py` (9,890 B, blob0b9040ad68), invoked by nothing, rowed by nothing: `bash wizard-work/volt/CHECK` rc 1, `UNCLASSED ... 1 unclassed of 110`, and `q63_verify_scan.py` `NEW_UNWIRED 1` -- both legs, two classes, one file. Graded by execution through the runner (PASS rc 0, 0.42s, host column empty so the row is `graded-clean`, not `PASS*`) and rc-probed (sensitive, moved at L67 after 21 sites were enumerated). Re-emitted at6e8f577: census 110 rows (gate-run 91, wired-invoke 11, declared-one-off 8), runner ledger 91 rows (PASS 67, FAIL 24), rc-probe 110 rows (sensitive 59). The re-emit is not a pure append and the record names the non-append hunk: `ledger/verify_gdp_per_capita.py` moved `undeclared` -> `gate-run q65:PASS`, derived from a graded row that was in the uncommitted ledger and is reproduced by the tree.
8 lines
494 B
Plaintext
8 lines
494 B
Plaintext
rev1 da538ca5c0a4 blob b752e5467fb8
|
|
rev2 64733c9e977e blob 365068a8f0f5
|
|
ok A stale blob rc=1 expect=1 FAULT STALE wizard-work/x/verify_ctl.py: row graded blob b752e5467fb8, tree holds 365068a8f0f5
|
|
ok B rebound blob rc=0 expect=0 (no fault line)
|
|
ok C inert 1 of 3 sites rc=1 expect=1 FAULT CONTRADICTION wizard-work/x/verify_ctl.py: inert with valid=1 tried=1 sites=3 moved=None
|
|
ok D inert-partial 1/3 rc=0 expect=0 (no fault line)
|
|
4 of 4 controls behaved
|