volt: path-claims adjudication -- six pending-work rows in the ledger (8 new -> 2), and the record's two-character remedy measured false

WORK-QUEUE.md

@@ -11169,3 +11169,11 @@ The class: an invocation-shaped reference to the file exists from nowhere in the
 - **`tools/verify.py --repo .` at `d712de3`: 8 legs, 7 pass, 1 fault, 0 ungradable** — `path-claims` only, and now 8 new paths wide. `index-current` and `append-audit` PASS.
 - **Sphinx's archive is the tick's strong artifact and I verified it from live arXiv, not from its own gate:** archived `paper.html` is byte-identical to live `arxiv.org/html/2510.13276v1` (284,688 B, sha256 `605b1f5cabe9…`), the archived Atom abstract equals live v2 (1,435 chars, `2,280` / `8 tasks` / `16K to 128K`), and the v1-only tokens (`8 distinct tasks`, `6 context length intervals`, `LVLMs`) are in the v1 rendering and absent from v2. `CHECK.sh` → GREEN, 39 checks, 3 negative controls RED as designed. One number needs its rule: `claims.json` holds **8** entries while the report's method says *"seven claims"* and §3 tabulates 7 — 7 page-pinned plus 1 abstract claim. Recorded, not edited.
 - **No item opened or closed beyond the forge row; the open set is unchanged** (`Q37`, `Q53`, `Q64` Alexander's, `Q57` null's, `Q58` sol's, `Q60`, `Q62`, `Q63`). No decision for Alexander: nothing above is a design question. Nothing from `inbox/` is quoted here; `decisions/` re-read and unexecuted, item 13's decided note controlling. Appended at the foot; `docs/queue-index.md` re-rendered in the same commit.
+
+**path-claims adjudicated at `a259960` (volt) — the six pending-work rows are in the ledger, 8 new → 2, and the record's two-character remedy is measured false: forge's fix alone leaves the leg red.**
+
+- **The eight rows are two populations, and only one of them is a tolerance.** Six exist in this worktree untracked and are named by `wizard-work/sol/daily-local-pipe-triage-2026-10-25.md`'s bucket table — a census whose own header measures `untracked: 119` and whose "newest" column names one file per bucket. Six `NOT_ADDED` rows are appended to `tools/path_claim_baseline.tsv` (`6 0`, 34 → 40 lines), each carrying its citing line, byte count and sha256 prefix, every one of those facts re-derived at write time (`?? ` in `git status`; `git log --all --diff-filter=A` → 0 commits; precedent `docs/deepseek-cost-routing.md`). The ledger then reads **1788 distinct paths, 25 missing, 2 new**; `path_claim_check --selftest` **31/31**.
+- **The other two are a live wrong claim and stay red.** `wizard-work/forge/SMELL_CHECK_MONOTONIC_REFACTOR_VERIFICATION.md:95-96` names two files without the leading underscore that `4f76eaa`'s numstat adds with it; the token is on no ref and on no disk, so it is not a tolerance case. Forge's file, `STANDING-AGREEMENT.md:86` — untouched.
+- **"The gate dies at two characters" is false, and this is the measurement.** Scratch clone of `d712de3`: unmodified **8 new**; with the six rows **2 new**; with the six rows **and** forge's two characters at `:95-96` **still 2 new**, `verify` still 8 legs / 7 pass / 1 fault. After the fix the token is still minted at **five sites, six occurrences** — `WORK-QUEUE.md:11134` (both), `:11148`, `replies/2026-10-25-to-forge-18.md:37`, `:38`, `wizard-work/volt/q65-2026-10-25-residual.md:139` — four of them append-sanctioned under `tools/append_only_audit.py:58`, so no permitted edit can clear them. Every one of the five is a sentence *about* the defect, which is the condition `replies/2026-10-25-to-zephyrus-96.md:24-29` set for quotation-of-a-defect rows; it does not fire yet, because `:95-96` is still an Artifacts list asserting two files that are not there.
+- **No item opened or closed, nothing closed early.** `tools/verify.py --repo .` with these six rows in the tree at `a259960`: **8 legs, 7 pass, 1 fault, 0 ungradable** — `path-claims`, `FAIL: 2 missing path(s)`, and that is the honest state. The six rows clear the day their owners commit the files; the two do not clear by bookkeeping.
+- **Evidence:** `wizard-work/volt/path-claims-2026-10-25-adjudication.md` (§1 the split with per-file digests, §2 the four-step clone table, §3 what was deliberately not done); `checkins/2026-10-25-volt.md`; `git diff --numstat` `6 0` on the ledger. No other lane's file edited. Appended at the foot; `docs/queue-index.md` re-rendered in this commit.

checkins/2026-10-25-volt.md

@@ -0,0 +1,13 @@
+# 2026-10-25 — volt
+
+**Did:**
+- Adjudicated the `path-claims` fault at `a259960`. Eight new rows against the ledger split into two populations: six files that exist untracked in this worktree and are named by `wizard-work/sol/daily-local-pipe-triage-2026-10-25.md`'s bucket table (its own header measures 119 untracked), and two that exist on no ref and no disk — `wizard-work/forge/`'s Artifacts list drops the leading underscore from `_smell_check_monotonic.py` and `_smell_check_monotonic_refactored.py`.
+- Appended six `NOT_ADDED` rows to `tools/path_claim_baseline.tsv` (`6 0`, 34 → 40 lines), each generated from a re-measurement of the file (size, sha256, `?? ` status, `git log --all --diff-filter=A` → 0 commits) rather than transcribed. `path_claim_check --selftest` 31/31 after. New rows: **8 → 2**.
+- Measured the record's stated remedy and found it false. In a scratch clone of `d712de3`: unmodified → 8 new; +the six rows → 2 new; +forge's two characters at `:95-96` → **still 2 new**, gate still `FAULT`. The prefix-less token survives at five sites, four of them append-sanctioned (`tools/append_only_audit.py:58`): `WORK-QUEUE.md:11134` and `:11148`, `replies/2026-10-25-to-forge-18.md:37-38`, plus my own `q65-2026-10-25-residual.md:139`. Every one of the five is a sentence *about* the defect — the condition `replies/2026-10-25-to-zephyrus-96.md:24-29` set for quotation-of-a-defect rows, not yet met because `:95-96` is still a live wrong claim.
+- Record: `wizard-work/volt/path-claims-2026-10-25-adjudication.md` (§1 the split with per-file digests, §2 the four-step clone table, §3 what I deliberately did not do). No other lane's file edited; the ledger append is the only change to a shared instrument.
+
+**Blocked:** the six remaining rows wait on owners, not on me. Forge's `:95-96` is another party's file (`STANDING-AGREEMENT.md:86`) and the live claim; the two tolerance rows wait on that fix, by reply 18's refusal and reply 96's shape.
+
+**Next:** re-measure when forge's edit lands — the residue should be exactly the five sites in §2, all descriptions, and then the quotation-of-a-defect rows can be written from that reading.
+
+**Ask:** none. No item opened or closed; the open set is unchanged.

docs/queue-index.md

@@ -63,7 +63,7 @@
 | 53 | Q60 | 10830-10889 | 9719 | opening | Every truncated identifier in the archive: which ones can still be checked *(pipe tooling; opened 2026-10-24 by the pipe, per reply 86 §6 and reply 87 §1)* | open and unclaimed. |
 | 54 | Q61 | 10890-10945 | 9624 | opening | beam's `topo_sort` drops generator dependencies, and its gate imports a copy outside the repo *(beam lane; opened 2026-10-24 by the pipe, per reply 88 to zephyrus)* | open and unclaimed. |
 | 55 | Q62 | 10946-10993 | 3717 | opening | 147 committed gates read `/root/.hermes/wizard-outputs`; two of them cannot pass from a clone *(no lane owns it; opened 2026-10-24 by the pipe, per reply 89 to zephyrus)* | open and unclaimed. |
-| 56 | Q63 | 10994-11171 | 55678 | opening | Six committed verifiers print PASS while asserting nothing, and eight are run by no gate *(no lane; opened 2026-10-24 by the pipe, per reply 90 to zephyrus)* | open and unclaimed. |
+| 56 | Q63 | 10994-11179 | 58533 | opening | Six committed verifiers print PASS while asserting nothing, and eight are run by no gate *(no lane; opened 2026-10-24 by the pipe, per reply 90 to zephyrus)* | open and unclaimed. |
 
 ## Ids with no `## ` heading
 
@@ -260,9 +260,9 @@ The block below is the parse this document renders, byte for byte. `--check` com
   "end_line": 8,
   "line": 1
  },
- "queue_bytes": 1565365,
- "queue_lines": 11171,
- "queue_sha256": "ca276c427cfb273f6429f296e5570927134d2d447fed003c2896b8f338255656",
+ "queue_bytes": 1568220,
+ "queue_lines": 11179,
+ "queue_sha256": "cc8d69a98349aecfabb15a3980e04167615e2ee5f58afcbf8d4d3b3509932c72",
  "sections": [
   {
    "bytes": 3139,
@@ -925,11 +925,11 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "title": "147 committed gates read `/root/.hermes/wizard-outputs`; two of them cannot pass from a clone *(no lane owns it; opened 2026-10-24 by the pipe, per reply 89 to zephyrus)*"
   },
   {
-   "bytes": 55678,
-   "end_line": 11171,
+   "bytes": 58533,
+   "end_line": 11179,
    "id": "Q63",
    "line": 10994,
-   "lines": 178,
+   "lines": 186,
    "role": "opening",
    "role_detail": "",
    "status": "open and unclaimed.",

tools/path_claim_baseline.tsv

@@ -32,3 +32,9 @@ replies/2026-10-15-to-timmy-58.md	RENAMED	renamed to replies/2026-10-15-to-merli
 replies/2026-10-15-to-merlin-58.md	RENAMED	renamed to replies/2026-10-15-to-merlin-67.md at 7d18269 (DUPLICATE_NUMBER fix: 5d00265's rename had put two 58s in merlin's series, the 10-14 reply 58 and this 10-15 one; 67 is that series' measured next free integer -- 59 through 66 are all taken; filename and the heading's number token renumbered, numstat 1/1, body byte-identical); cited at career-lane/daily-2026-10-24.md:12 and :92 and replies/2026-10-24-to-zephyrus-86.md:90 as the name that rename created
 replies/2026-10-24-to-mercury-11.md	RENAMED	renamed to replies/2026-10-24-to-mercury-12.md at 7d18269 (DUPLICATE_NUMBER fix: 2026-10-22-to-mercury-11.md already held 11 in that series; filename and the heading's number token renumbered, numstat 1/1, body byte-identical); cited at replies/2026-10-24-to-zephyrus-87.md:35 and :118 while naming the collision
 career-lane/daily-2026-10-23.md	NOT_ADDED	the citing line asserts it does not exist (career-lane/daily-2026-10-24.md:14: no career-lane/daily-2026-10-23.md exists on main); git log --all --diff-filter=A -> 0 commits, so no ref ever held it; the dailies are 10-20, 10-21, 10-22, 10-24
+recoveries/apply-queue-status-2026-10-25.md	NOT_ADDED	pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-25.md:25 names it as a bucket's "newest" row over that report's own untracked census (its header measures 119 untracked files); untracked in this worktree (6271 B, sha256 12da1c5ef134a2f3, git status -> "?? "), and git log --all --diff-filter=A -> 0 commits, so no ref holds it; the row clears when its owner commits it
+wizard-work/forge/_repro_bounds_original.py	NOT_ADDED	pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-25.md:21 names it as a bucket's "newest" row over that report's own untracked census (its header measures 119 untracked files); untracked in this worktree (900 B, sha256 498a42813df9a3d3, git status -> "?? "), and git log --all --diff-filter=A -> 0 commits, so no ref holds it; the row clears when its owner commits it
+wizard-work/null/README-gatehygiene.md	NOT_ADDED	pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-25.md:20 names it as a bucket's "newest" row over that report's own untracked census (its header measures 119 untracked files); untracked in this worktree (7478 B, sha256 0c9e3060f15c37bd, git status -> "?? "), and git log --all --diff-filter=A -> 0 commits, so no ref holds it; the row clears when its owner commits it
+wizard-work/null/_probe_repro7.py	NOT_ADDED	pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-25.md:24 names it as a bucket's "newest" row over that report's own untracked census (its header measures 119 untracked files); untracked in this worktree (1449 B, sha256 093b88d3cac7f587, git status -> "?? "), and git log --all --diff-filter=A -> 0 commits, so no ref holds it; the row clears when its owner commits it
+wizard-work/null/gatehygiene.py	NOT_ADDED	pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-25.md:23 names it as a bucket's "newest" row over that report's own untracked census (its header measures 119 untracked files); untracked in this worktree (21867 B, sha256 e1d964ed3c380c54, git status -> "?? "), and git log --all --diff-filter=A -> 0 commits, so no ref holds it; the row clears when its owner commits it
+wizard-work/sphinx/lcmm-claim-index-2026-10-24/DOSSIER.md	NOT_ADDED	pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-25.md:26 names it as a bucket's "newest" row over that report's own untracked census (its header measures 119 untracked files); untracked in this worktree (21874 B, sha256 cea2a26c1684d0d6, git status -> "?? "), and git log --all --diff-filter=A -> 0 commits, so no ref holds it; the row clears when its owner commits it

wizard-work/volt/path-claims-2026-10-25-adjudication.md

@@ -0,0 +1,97 @@
+# path-claims at `a259960` — six rows adjudicated, and the two-character remedy measured false
+
+Measured 2026-10-25 by volt, at `d712de3` and again at `a259960`. One fault in the gate, eight
+new rows against the ledger, two populations inside them. Six are now adjudicated and the ledger
+carries them; the other two are one party's live wrong claim and stay red.
+
+## 1. The fault, split
+
+`python3 tools/verify.py --repo .` → **8 legs, 7 pass, 1 fault**, `path-claims`
+(`FAIL: 2 missing path(s) the baseline does not name` after this change; **8** before it).
+`tools/path_claim_check.py --repo .` at `d712de3`: **1781 distinct paths, 25 missing, 8 new**.
+Every one of the eight is a path absent from every ref — the split is *why* it is absent.
+
+**(a) Six that exist, untracked, named by a pending-work snapshot — adjudicated `NOT_ADDED`.**
+
+`wizard-work/sol/daily-local-pipe-triage-2026-10-25.md` (sol, `5cae75b`) is a census of this
+worktree's pending work; its header states `untracked: 119`, and its bucket table's "newest"
+column names one file per bucket. Those names are the report's *subject*, not a claim that the
+archive holds them. Re-derived here, per path: present on disk, `git status --porcelain` → `?? `,
+`git log --all --diff-filter=A` → 0 commits.
+
+| citing line | path | bytes | sha256 (16) |
+|---|---|---|---|
+| `:20` | `wizard-work/null/README-gatehygiene.md` | 7478 | `0c9e3060f15c37bd` |
+| `:21` | `wizard-work/forge/_repro_bounds_original.py` | 900 | `498a42813df9a3d3` |
+| `:23` | `wizard-work/null/gatehygiene.py` | 21867 | `e1d964ed3c380c54` |
+| `:24` | `wizard-work/null/_probe_repro7.py` | 1449 | `093b88d3cac7f587` |
+| `:25` | `recoveries/apply-queue-status-2026-10-25.md` | 6271 | `12da1c5ef134a2f3` |
+| `:26` | `wizard-work/sphinx/lcmm-claim-index-2026-10-24/DOSSIER.md` | 21874 | `cea2a26c1684d0d6` |
+
+Six `NOT_ADDED` rows appended to `tools/path_claim_baseline.tsv` (`6 0`, 34 → 40 lines), each row
+carrying its own citing line, size and digest, so the row cannot drift from the measurement. The
+precedent is the ledger's own `docs/deepseek-cost-routing.md` row — a file that sits in the
+worktree untracked and is named by a record. A row clears the day its owner commits the file.
+
+**(b) Two that exist nowhere — not touched.**
+
+`wizard-work/forge/` carries `_smell_check_monotonic.py` and `_smell_check_monotonic_refactored.py`
+(`git ls-files`, added at `4f76eaa`). `wizard-work/forge/SMELL_CHECK_MONOTONIC_REFACTOR_VERIFICATION.md:95-96`
+names both without the leading underscore: token present on no ref **and** on no disk, so it is a
+live wrong claim in the document's own Artifacts list, which is what a reader follows. Forge's file,
+`STANDING-AGREEMENT.md:86` — not overwritten here, and not tolerated here.
+
+## 2. The remedy on the record is false, and this is the measurement
+
+`WORK-QUEUE.md:11134` and `replies/2026-10-25-to-forge-18.md` both say the gate stays red **until
+forge fixes two characters**. I tested that in a scratch clone of `d712de3`, in four steps:
+
+| step | path-claims reading | verify |
+|---|---|---|
+| clone at HEAD, unmodified | 25 missing, 8 new | 8 legs, 7 pass, 1 fault |
+| + the six rows above | 25 missing, **2 new** | — |
+| + forge's two characters at `:95-96` | 25 missing, **2 new** | — |
+| after both | — | **8 legs, 7 pass, 1 fault**, `2 missing path(s)` |
+
+The two characters are not sufficient. After the doc is fixed, the prefix-less token is still
+minted at **five sites, six occurrences**, and `tools/append_only_audit.py:58` lists four of those
+paths as append-sanctioned — a record may be appended to, never rewritten:
+
+| site | creator | append-sanctioned |
+|---|---|---|
+| `WORK-QUEUE.md:11134` (both tokens) | timmy | yes |
+| `WORK-QUEUE.md:11148` | timmy | yes |
+| `replies/2026-10-25-to-forge-18.md:37` | Timmy | yes |
+| `replies/2026-10-25-to-forge-18.md:38` | Timmy | yes |
+| `wizard-work/volt/q65-2026-10-25-residual.md:139` | volt | no |
+
+Every one of the five sentences is *about* the defect: each says the doc spells the name wrongly.
+That is exactly the condition Timmy set in `replies/2026-10-25-to-zephyrus-96.md:24-29` for
+"rows tagged as a quotation of a defect — not a clean tolerance row". The condition is not met
+*yet*, and the reason is specific: `:95-96` is still an Artifacts list asserting two files that do
+not exist under those names, and that line is forge's to fix. Once it is fixed, the residue is the
+five sites above and nothing else — all of them descriptions of the defect, none of them a place a
+reader would go looking for a file.
+
+## 3. Not done, deliberately
+
+- **Forge's `:95-96`** — another party's file (`STANDING-AGREEMENT.md:86`), and the live claim.
+- **Tolerance rows for the two tokens** — refused at `0868c6b` and still refused while `:95-96`
+  stands; the right rows, when they come, are the quotation-of-a-defect rows reply 96 defined, not
+  a clean tolerance.
+- **My own residual record at `:139`** — the only non-sanctioned site, and it is a past reading.
+  Rewriting a past reading to remove the token would make the record disagree with what the tool
+  printed that day. The names it should have carried are `_smell_check_monotonic.py` and
+  `_smell_check_monotonic_refactored.py`.
+
+## 4. Evidence
+
+- `tools/verify.py --repo .` at `a259960` with the six rows in the tree: **8 legs, 7 pass, 1 fault**,
+  fault `path-claims`, `2 missing path(s)` — the two in §1(b).
+- `tools/path_claim_check.py --repo . --rev WORKTREE`: **1788 distinct paths, 25 missing, 2 new**,
+  rc 1. `--selftest`: **31 cells, 31 passed**.
+- `tools/path_claim_check.py --repo . --selftest` before and after the ledger append: 31/31 both.
+- Scratch clone readings: `clone_lab.txt` (the four steps in §2 verbatim); site table re-derived by
+  scanning `git ls-files` for the token and resolving each hit's creator with
+  `git log --diff-filter=A`.
+- The six-row block is appended, not rewritten: `git diff --numstat` on the ledger reads `6 0`.