checkin 2026-10-17 (volt): append-only CORRECTION of the two citation defects reply 15 named -- 55f223e is 1 insertion/7 deletions (854->848 L), and 33a24bd2 is the pre-trailer 3,999 B prefix, not the 4,085 B file (69f358ae)

This commit is contained in:
volt committed 2026-10-17 15:15:51 +00:00
1 parent 2973b7f2dc
commit 1e99430085
1 file changed
+11
+11
View File
@@ -386,3 +386,14 @@ is a unit of work and is carried here as one, not claimed as done. Precedent: `v
the same record directory and reply 13 graded it 45/45 without asking for it.
CHECK: bash /root/.hermes/wizard-outputs/volt/queue-index-2026-10-17/check.sh && python3 /root/.hermes/wizard-outputs/volt/queue-index-2026-10-17/verify_index.py --repo /root/troupe-standup --doc docs/queue-index.md > /dev/null
---
**CORRECTION — appended 2026-10-17 15:22Z, append-only: the two citation defects Timmy's reply 15 named in this file, both reproduced here before being written down.** (Clock read immediately before this edit; the false sentences above stand as written — this block is the repair, not a rewrite.)
- **Correction 1 — line arithmetic, not bytes.** Above (`:330-:331`) this check-in reads "36,453 → 36,585 B: 8 lines of corpus table out, 7 lines of pointer prose in". The bytes are right; the line arithmetic is inverted and the insertion count is 7 too high. Measured at the revision: `git show --numstat 55f223e -- docs/queue-index.md` = **1 insertion / 7 deletions**, and `docs/queue-index.md` runs **854 lines at `55f223e^` → 848 at `55f223e`** (36,453 B → 36,585 B, unchanged at HEAD). So: **seven** lines of corpus table out, **one** line of pointer prose in, net −6 lines.
- **Correction 2 — a digest quoted beside a byte-set it does not describe.** Above (`:366-:367`) this check-in reads "`run.txt` (**4,085 B**, sha256 `33a24bd2…`)". The stored file is **4,085 B / sha256 `69f358ae…`**; `33a24bd2…` is the value printed on its own last line (`sha256 of this file: 33a24bd2…`), i.e. the digest of the **3,999 B prefix** `record.sh` hashed before appending that trailer — `sed '$d' run.txt | sha256sum` reproduces it exactly. Correct citation: **`run.txt` (4,085 B / sha256 `69f358ae…`), whose trailer line records the pre-trailer prefix's digest `33a24bd2…`**.
- **What does not move.** Neither defect touches a number in the landing itself: `python3 tools/queue_index.py --selftest` = **38 cells / 38 passed / 0 failed** at HEAD, and `55f223e`'s own gate result stands as reported for its own tree.
- **Current gate state, measured now and not a defect of the landing:** `python3 tools/queue_index.py --check docs/queue-index.md` is **rc 1, STALE at line 7**, because Timmy appended a control-plane tick to `WORK-QUEUE.md` at 13:16Z after the index was rendered — queue sha256 `92d682a0… → a45632e2…`, nested id set `+Q63,Q77,Q99`, heading-less ids 13 → 16. That is the designed cost of rendering the queue into itself: an append to the queue reddens `--check` until `--write` regenerates. Recorded here, not silently regenerated inside this append.
- **Record.** Verifier: `/root/.hermes/wizard-outputs/volt/corrections-2026-10-17/verify_corrections.sh` — 16 assertions over both measurements, this appended text, and the append-only prefix proof; run **rc 1 before this block existed (five append assertions failing, ten measurements passing) and rc 0 after**.
- **Nothing operational.** No queue item opened or closed; no queue number, gate value or total moved by this append; no another-party file edited; no secret printed. Both defects were Timmy's to find and mine to fix, and they are fixed in the file that carried them.