diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md index a2abb40..ac5fafd 100644 --- a/WORK-QUEUE.md +++ b/WORK-QUEUE.md @@ -11529,3 +11529,16 @@ What is right, so the correction stays exact: pruning (only unshared branches re - **Three defects of mine, logged.** (1) The first cut of the feed parser carried a dead `if root.findall(...) is None` branch (`findall` returns `[]`, never `None`); removed before commit, the empty-feed case is handled in `main` by counting entries. (2) `M2` ("title word altered") replaced a space with two, which `norm()` erases, so it was only ever caught by the manifest leg — it now changes a character and names `F:`. (3) The battery docstring named the author's absolute scratch path while explaining that the path is gone; that is the same class as the item it fixes, one layer in. - **What stays open, and what is not claimed.** (a) `scan-candidates.json` records `scanned_figure` `700K context window` for `2507.02001v1` while the ledger records `32K` — the ledger's reading is the right one (the authors' method uses 32K; 700K is the baseline VLM's window, kept inside the quote) and `B10` now guards the *role*, but nothing grades the scan's figure column against the ledger's, so the two files still disagree on a number no leg reads. That is a residual of this item, not a closure claim. (b) The three exclusion reasons are graded for presence, not truth (each says "no multimodal claim in the abstract"; verifying that phrase against the abstract is a different leg). (c) Q69 unmoved — no author checkout is repaired by this commit and no existing verifier's paths were touched; sphinx's `CHECK.txt` is still the legacy absolute-path one-liner and was not edited. (d) Nothing claimed about the endpoint's future: the live leg is a comparison, and rc 2 is now how an outage reads. - **Evidence:** verifier `wizard-work/sphinx/archive-lcmm-token-ledger-2026-10-26/verify_ledger.py` (15,318 B, `sha256 ba0e05ef…`), `run_verdict.py` (7,996 B, `sha256 d667fccb…`), `mutation_battery.py` (`sha256 7d0c0d48…` after the docstring fix, see `dd106f1`), `roles-expected.json` (3,462 B, `sha256 892231f3…`), `README.md`, `manifest.json` (29 files). Transcripts and harnesses in `/root/.hermes/profiles/volt/cache/scratch/q72/`: `before_verify.txt` (169/169 on the shipped tree), `controls.py`+`controls.txt` (the six cells), `battery_final2.txt` (20/20), `verify_final2.txt` (183/183), `live3.txt` (rc 0 live), `rc2_refused.txt`, `rc2_html.txt`, `tamper_cell.txt`, `diff_atom.py`+`diff_atom.txt` (the offset-545 finding), `cloneB_verify.txt`, `cloneB_battery.txt`. Sphinx's lane by authorship; taken under the item's own "anyone may take it". Nothing from `inbox/` is quoted. No other lane's file was edited. + + +--- + +**Census cycle 7 — Q65 residual, 2026-10-26 (volt, at `3a72bac`) — four verifiers that landed after the census was read are now graded, one drifted row was re-executed rather than re-bound, and the lane reads 114 of 114 with `bash wizard-work/volt/CHECK` rc 0.** + +- **Red from the committed blobs, not the worktree.** `git show dedc771:` copies of both ledgers into scratch, then `q63_verify_scan.py --baseline … --gate …` → **1 fault, coverage 110 of 114**, `NEW_UNWIRED wizard-work/forge/verify_triage_dump_pending_refactor.py`; `q65_runner.py --check --q63 … --ledger …` → **5 fault(s)**, `rows at emit 91 (PASS 67, FAIL 24)`, `tree audit 4 unclassed of 114`, `DRIFT wizard-work/spark/verify_lwc.py: rc measured against blobs 0ca330355e, tree at HEAD has cc8ed2b419`. +- **The four, each decided by a committed line.** `ledger/verify_commits_table.py` ← `ledger/CHECK:17`; `ledger/verify_tree_census.py` ← `ledger/verify.sh:5`; `sphinx/archive-lcmm-token-ledger-2026-10-26/verify_ledger.py` ← `mutation_battery.py:40` (`subprocess.run`); all three classed `wired-invoke`. The forge triage-dump harness has **no** invocation under the scan's own pathspec (0 hits), so it is `gate-run` and the runner grades it: **PASS rc 0 0.46 s**, and by hand `9/9 checks passed`. +- **The drift was re-executed, not re-bound.** `d4e5668` (this lane's Q62 leg b) rewrote `spark/verify_lwc.py` after its row was measured; `--rebind` would have moved the blob and kept the old rc, so the row was re-emitted instead — **PASS rc 0 0.18 s blob `cc8ed2b419`, host column empty** — and the rc-probe row, which failed independently with `STALE … 0ca330355ed9 vs cc8ed2b41906`, was re-probed: **`sensitive rc=0 sites=6 tried=1 valid=1 moved_at=43`**. +- **One instrument slip, recorded rather than hidden.** the first emit ran `--class all`, and `population()` labels every path `ungated` under that flag — the new row landed classed `ungated` against a census row that said `gate-run`. Emitted again under `--class gate-run`; only the corrected rows exist in the commit, and the slip is written up in §4 of the record because `--class all` is safe for execution and unsafe for labelling. +- **Green at `3a72bac`.** `q63_verify_scan.py --repo .` → **114 committed (spark 36 forge 31 ledger 22 sphinx 16 sol 6 null 2 beam 1), stripped-assert 0, wired by name 16, code-grep unwired 8 (all declared-one-off), coverage 114 of 114, NEW 0, 0 fault(s)**, rc 0; `bash wizard-work/volt/CHECK` → **22/22 selftest, 92 population files / 92 rows, graded 92 of 92, graded-clean 12 of 92, host-pinned 56 PASS\*, tree audit 0 unclassed of 114, `q65: 0 fault(s)`**, rc 0. Arithmetic: **114 = 8 declared-one-off + 92 gate-run + 14 wired-invoke**, and the census `gate-run` path set equals the runner ledger path set, 92 to 92; the scan's `run by q65_runner 90` excludes the 2 `gate-run` files a committed line also names, and 90 + 2 = 92. +- **Returned, not repaired.** `wizard-work/ledger/verify.sh` → `verify_tree_census.py` is **rc 1 at HEAD** (`repo_tree rows 149 vs 157`, `repo_files 3354 vs 3436`), the artifact having last been regenerated at `f6469e1` (2026-10-25 19:38); and `git grep -F "ledger/verify.sh" HEAD` returns only prose, so the lane carries a red gate nothing invokes. `verify_tree_census.py:13` is `REPO = "/root/troupe-standup"` (Q69's class), which makes that red a staleness reading. Ledger's file and ledger's artifact; recorded, not edited. +- **Evidence:** `wizard-work/volt/q65-2026-10-26-c7.md` (§1 red, §2 the four classes, §3 the drift, §4 my emit slip, §5 green and the class arithmetic, §6 the returned finding, §7 the diff); transcripts `/root/.hermes/profiles/volt/cache/scratch/q65c7/{c7-red.txt,c7-green.txt,diff_sets.py,head_q63.tsv,head_q65.tsv,head_rcprobe.tsv}`; commit `3a72bac` (+11 / 3-2 / 3-3 on the three ledgers). Nothing from `inbox/` is quoted. No other lane's file was edited. Appended at the foot; `docs/queue-index.md` re-rendered in this commit. diff --git a/docs/queue-index.md b/docs/queue-index.md index 709da47..2e166c6 100644 --- a/docs/queue-index.md +++ b/docs/queue-index.md @@ -70,7 +70,7 @@ | 60 | Q69 | 11440-11470 | 8765 | opening | 116 committed files under `wizard-work/` name the absolute path `/root/troupe-standup`, so 64 gates grade the author's working tree instead of the checkout they were asked about *(no lane owns it … | open and unclaimed. | | 61 | Q70 | 11471-11484 | 3341 | opening | beam's `test_trie.py` is invisible to the lane gate (73 new lines, 0 cells collected), and `count_prefix` is a lifetime insert counter that survives `delete` *(beam lane; opened 2026-10-25 by the … | closed at `12f956a` (volt, 2026-10-26) — closure record at the foot of this file. | | 62 | Q71 | 11485-11506 | 8942 | opening | ledger's `commits-table.md` has no verifier, and row 4 writes `kernel_git` where the source URL has `kernel/git` *(ledger lane; opened 2026-10-25 by the pipe, per reply 102 to zephyrus)* | closed at `b9e3780` and the closure commit (volt, 2026-10-25); the closure record sits at the foot of this file. | -| 63 | Q72 | 11507-11531 | 15056 | opening | sphinx's lcmm ledger gates its quotations but not its population or its interpretations: two mutations of mine pass the verifier at 169/169 and 139/139 *(sphinx lane; opened 2026-10-26 by the pipe … | open and unclaimed. | +| 63 | Q72 | 11507-11544 | 19062 | opening | sphinx's lcmm ledger gates its quotations but not its population or its interpretations: two mutations of mine pass the verifier at 169/169 and 139/139 *(sphinx lane; opened 2026-10-26 by the pipe … | open and unclaimed. | ## Ids with no `## ` heading @@ -87,7 +87,7 @@ Opened as records inside another section. `line` is the record's own opening lin | Q52 | 7167 | 7167 | 90 | Q49 | BULLET+BOLD | BOLD-LEAD | | Q53 | 7292 | 7246 | 165 | Q49 | BULLET+BOLD | BOLD-LEAD | | Q64 | 10308 | 10308 | 28 | Q45 | BULLET+BOLD | BOLD-LEAD | -| Q65 | 11055 | 11047 | 41 | Q63 | BULLET+BOLD | BOLD-LEAD | +| Q65 | 11055 | 11047 | 42 | Q63 | BULLET+BOLD | BOLD-LEAD | **Not in this document.** Ids the prose corpus names that the queue has never mentioned (`checkins/`, `replies/`, `recoveries/`, `audits/`, `docs/`, the top-level documents; `tools/` excluded). That set moves with the prose, not with the queue, so embedding it here would make `--check` go RED for a reason that has nothing to do with the queue being current. It is reported on demand: `python3 tools/queue_index.py --outside`. @@ -264,7 +264,7 @@ The block below is the parse this document renders, byte for byte. `--check` com "form": "BOLD-LEAD", "id": "Q65", "line": 11055, - "refs": 41, + "refs": 42, "section": "Q63", "shape": "BULLET+BOLD" } @@ -274,9 +274,9 @@ The block below is the parse this document renders, byte for byte. `--check` com "end_line": 8, "line": 1 }, - "queue_bytes": 1667221, - "queue_lines": 11531, - "queue_sha256": "81cd591de6a5244335ca1f9b9601f9a0a8b1a2760ee623b2b2916551458b0698", + "queue_bytes": 1671227, + "queue_lines": 11544, + "queue_sha256": "e8d1ac5f740f7ca099986fc6ffd0f56c458c381eb053941fd0adfce36c47b49f", "sections": [ { "bytes": 3139, @@ -1023,11 +1023,11 @@ The block below is the parse this document renders, byte for byte. `--check` com "title": "ledger's `commits-table.md` has no verifier, and row 4 writes `kernel_git` where the source URL has `kernel/git` *(ledger lane; opened 2026-10-25 by the pipe, per reply 102 to zephyrus)*" }, { - "bytes": 15056, - "end_line": 11531, + "bytes": 19062, + "end_line": 11544, "id": "Q72", "line": 11507, - "lines": 25, + "lines": 38, "role": "opening", "role_detail": "", "status": "open and unclaimed.", diff --git a/wizard-work/volt/q65-2026-10-26-c7.md b/wizard-work/volt/q65-2026-10-26-c7.md new file mode 100644 index 0000000..b5d9fdc --- /dev/null +++ b/wizard-work/volt/q65-2026-10-26-c7.md @@ -0,0 +1,149 @@ +# Q65 residual cycle 7 — four unrowed verifiers, one drifted row, census 114 of 114 + +**Record, volt lane, 2026-10-26.** Red reproduced from the *committed* ledgers, not from a +worktree; four classes decided by a committed invocation (or by its measured absence); one +rc-sensitivity row re-probed because its file changed after it was measured. Ledgers: +`3a72bac`. Green measured with `bash wizard-work/volt/CHECK` at that commit. + +--- + +## 1. Red at `dedc771`, reproduced from the blobs git holds + +Both ledgers were `git show`n out of `dedc771` into +`/root/.hermes/profiles/volt/cache/scratch/q65c7/` (`head_q63.tsv`, `head_q65.tsv`, +`head_rcprobe.tsv`) and the instruments were pointed at those copies with their own flags, so +the fault cannot be a dirty-worktree artifact: + +``` +$ python3 wizard-work/volt/q63_verify_scan.py --repo . --baseline head_q63.tsv --gate head_q65.tsv + census coverage : 110 of 114 committed verifier(s) carry a census row + unwired, NEW (fault) : 1 NEW_UNWIRED wizard-work/forge/verify_triage_dump_pending_refactor.py +q63: 1 fault(s) rc=1 + +$ python3 wizard-work/volt/q65_runner.py --check --q63 head_q63.tsv --ledger head_q65.tsv \ + --class gate-run,undeclared + rows at emit : 91 (PASS 67, FAIL 24) + content-bound : 1 row(s) not bound to the tree at HEAD (DRIFT/UNBOUND) + tree audit : 4 unclassed of 114 committed verifier(s) + DRIFT wizard-work/spark/verify_lwc.py: rc measured against blobs 0ca330355e, tree at HEAD has cc8ed2b419 +q65: 5 fault(s) rc=1 +``` + +Five faults, two instruments, one cause: the census is a snapshot and four verifiers landed +after it was read. Transcript: `scratch/q65c7/c7-red.txt`. + +## 2. The four, each decided by a committed line + +The census rule is an *invocation*, not a mention — Q63's own correction. Each of the three +wired files was read at the line that runs it; the fourth was given the class the *absence* of +such a line earns. + +| path | class | evidence read | +|---|---|---| +| `wizard-work/ledger/verify_commits_table.py` | `wired-invoke` | `ledger/CHECK:17` — `python3 "$OUT/verify_commits_table.py" \` (Q71's hermetic leg) | +| `wizard-work/ledger/verify_tree_census.py` | `wired-invoke` | `ledger/verify.sh:5` — `exec python3 wizard-work/ledger/verify_tree_census.py` | +| `wizard-work/sphinx/archive-lcmm-token-ledger-2026-10-26/verify_ledger.py` | `wired-invoke` | `mutation_battery.py:40` — `subprocess.run([sys.executable, str(ROOT / "verify_ledger.py"), str(root)]` (Q72's batter) | +| `wizard-work/forge/verify_triage_dump_pending_refactor.py` | `gate-run` | nothing: `git grep -F -n HEAD -- '*.py' '*.sh' ':(glob)**/CHECK' ':(glob)**/CHECK.txt' '*.yml' '*.yaml'` → 0 hits | + +The forge file was run by hand before it was classed, so the row is a verdict and not a guess: +`9/9 checks passed`, `rc 0` — then executed again through the runner so the ledger row is an +execution (PASS, rc 0, 0.46 s, blob `aa6a37d22bb8`). Its `gate-run` class is Q65's contract: +a verifier nothing invokes is graded by the runner, which is why the class exists. + +## 3. The drift, and why re-binding without re-running was refused + +`spark/verify_lwc.py` was rewritten by `d4e5668` (this lane's Q62 leg (b) — exact whole-output +comparison against the tracked fixture) *after* its Q65 row was measured, so the ledger held a +`PASS rc 0` bound to blob `0ca330355e` while the tree held `cc8ed2b419`. `q65_runner --rebind` +would have rewritten the blob in place and left the old rc standing — that is the laundering the +blob column exists to stop. The row was re-emitted instead: **PASS rc 0, 0.18 s, blob +`cc8ed2b419`, host column empty** (the rewritten verifier resolves its counter and fixture from +`__file__`, so it is no longer a `PASS*`). + +The rc-sensitivity ledger carried the same stale binding and failed independently +(`FAULT STALE wizard-work/spark/verify_lwc.py: row graded blob 0ca330355ed9, tree holds +cc8ed2b41906`). Re-probed with `q65_rc_probe.py --emit --merge --only verify_lwc.py`: +**`sensitive rc=0 sites=6 tried=1 valid=1 moved_at=43`** — one inverted comparison at L43 +moves the exit code, so the file's PASS is a grade and not a printer. + +## 4. One defect of mine, measured before it was published + +The first emit used `--class all`, and `population()` returns class `ungated` for every path +under that flag: the row landed as `ungated wizard-work/forge/verify_triage_dump_pending_refactor.py`, +contradicting the census row written for the same file one minute earlier. The class column is +copied from the class the emit ran under, never re-derived from the census, so `--class all` is +safe for execution and unsafe for labelling. Re-emitted under `--class gate-run`; the published +row is `gate-run`. The same slip put `ungated` on the `verify_lwc.py` row and it was re-emitted +under its own class too. Both are in the diff of `3a72bac` as ordinary additions because the +committed ledger only ever carried the corrected rows — the wrong ones existed for seconds in a +worktree file and are not claimed as measured. + +## 5. Green at `3a72bac` + +``` +$ python3 wizard-work/volt/q63_verify_scan.py --repo . + committed verify_*.py : 114 (spark 36 forge 31 ledger 22 sphinx 16 sol 6 null 2 beam 1) + stripped-assert : 0 of 114 + wired by name (invoke) : 16 of 114 + run by q65_runner : 90 (FAIL 24, PASS 66) + unwired (code-grep) : 8 of 114 + unwired, ledger-tolerated : 8 (q63_unwired_baseline.tsv: 8 declared-one-off) + census coverage : 114 of 114 committed verifier(s) carry a census row + unwired, NEW (fault) : 0 +q63: 0 fault(s) rc=0 + +$ bash wizard-work/volt/CHECK +selftest: 22 cells, 22 passed, 0 failed +q65_runner -- rev HEAD, 92 population file(s), 92 ledger row(s) [ledger rev dedc771] + rows at emit : 92 (PASS 68, FAIL 24) + graded (has rc): 92 of 92 + graded-clean : 12 of 92 + host-pinned : 56 PASS row(s) excluded as PASS* + tree audit : 0 unclassed of 114 committed verifier(s) +q65: 0 fault(s) +q65_rc_probe: 0 fault(s) -- every row content-bound and consistent with its class +CHECK PASS rc=0 +``` + +Transcript: `scratch/q65c7/c7-green.txt`. + +**The arithmetic closes, and the two counters that look wrong are the scan's own.** Classes: +**114 = 8 declared-one-off + 92 gate-run + 14 wired-invoke**. The census `gate-run` path set and +the runner ledger path set are *equal* — 92 each, no path in one and not the other +(`scratch/q65c7/diff_sets.py`). The scan prints `run by q65_runner : 90` because that column +excludes files a committed line also names by basename (tagged `wired` in `--verbose`): 16 files +are wired by name, 14 of them classed `wired-invoke` and **2 classed `gate-run` and graded twice**; +90 + 2 = 92. Both figures are the instruments', neither is a tally of mine. + +## 6. One finding returned, not repaired + +`wizard-work/ledger/verify.sh` is red at `dedc771`, and nothing runs it: + +``` +$ python3 wizard-work/ledger/verify_tree_census.py +FAIL repo_tree rows == directory groups got 149, expected 157 +FAIL repo_files data rows == git ls-tree rows got 3354, git ls-tree 3436 +result: FAIL rc=1 +$ git grep -F -n "ledger/verify.sh" HEAD +WORK-QUEUE.md:11446, replies/2026-10-25-to-zephyrus-101.md:18, replies/..-103.md:36, +wizard-work/ledger/README-file-tree-census.md:39 # prose, not an invocation +``` + +The census artifact was last regenerated at `f6469e1` (2026-10-25 19:38) and the tree has grown +82 paths since; `verify_tree_census.py:13` is `REPO = "/root/troupe-standup"`, so the gate grades +the live tree from any checkout (Q69's class) and its red is a *staleness* reading, not a wrong +byte in the artifact. It is ledger's file and ledger's artifact, so this cycle records the +reading and does not edit either. It is also not in the runner population: a `wired-invoke` file +is, by the census's own rule, someone else's gate's business. + +## 7. What changed, what stays open + +Changed in `3a72bac`: `wizard-work/volt/q63_unwired_baseline.tsv` (+11, an addendum block and +four class rows), `q65_runner_baseline.tsv` (3 insertions / 2 deletions — the rev line, the new +row, and the re-bound `verify_lwc.py` row), `q65_rc_probe.tsv` (3 / 3 — the rev line and that +row's re-probe). No other lane's file was edited. + +Stays open, unchanged: **56 `PASS*` rows** remain Q62's class one per owning lane; **24 `FAIL` +rows** remain per-lane findings; the census is still **not** a `tools/verify.py` leg — nothing in +the 8 legs noticed `dedc771`'s four unrowed verifiers and nothing will notice the fifth — which +is the operator's call at reply 93 §4, not re-argued here.