replies: 2026-10-22-to-null-01 -> -03 (duplicate series number: the gate's last red leg); lands the pending artifact-claims queue append

reply_check.py read DUPLICATE_NUMBER on replies/2026-10-20-to-null-01.md and
replies/2026-10-22-to-null-01.md, so verify.py's reply-headings leg read
"FAIL: 2 file(s) carry a class the baseline does not tolerate" (rc 1), the only
faulting leg of six. The numbering key is the recipient's series, not the day
(reply_check.py:39-41), and null's series already held 01 and 02 at 2026-10-20.

The fix is identity, not prose: git mv to -03.md and the heading's "# Reply 01"
-> "# Reply 03"; 1 changed line of 18, the other 17 byte-identical. Nothing in
the tree cites the old path (grep -rn '2026-10-22-to-null-01' -> 0 hits outside
the file), so no citation moves.

Measured after: reply_check DUPLICATE_NUMBER 0, faults 1 (the baseline-carried
HEADER_RECIPIENT at 2026-10-15-to-timmy-58.md), series 15 recipients /
268 numbered files / timmy hole [59] unchanged, --selftest 49/49 rc 0.

Also carried: the Workhorse artifact-claims record already at the foot of
WORK-QUEUE.md (measured before this append, unchanged by it) and the matching
docs/queue-index.md re-render. Carries nothing of forge's four uncommitted
tools/ refactors, which stay in the worktree as that lane left them.

WORK-QUEUE.md

@@ -10552,3 +10552,37 @@ Verification, read at `6cd2114` (the revision this record was written against; a
 6. **What it does not claim.** `WORKTREE` is a literal name, so a branch of that name is shadowed by the sentinel. The mode grades tracked files: a tool that has not been `git add`ed is not a row — the same blind spot one step earlier, and why the usage line says "as it will be committed". The currency cell stays `HEAD`-scoped by design. The sweep's missing `--repo` is recorded, not repaired: another lane's instrument, and a fix there needs its own red-first evidence. No Q-item state changed, and nothing here decides anything Alexander holds.
 
 — Volt
+
+**Artifact claims 2026-10-21 (volt, Workhorse) — the lane's artifact paths were the one class no tool graded: 23 records name an artifact directory, one names one that does not exist, and two of ten checksum manifests hash another tree instead of the artifact they sit in — graded now by a 17-cell tool, with all four defects left unrepaired on purpose.** No item opened or closed; the open set is as the previous record left it (`Q37`'s pipe span, the career-lane `Q53` decision held for Alexander, `Q64`'s design question Alexander's). Appended at the foot; `docs/queue-index.md` re-rendered in the same commit.
+
+1. **The gap, as an absence.** `tools/path_claim_check.py` grades a path only when it is relative to the checked tree; a token whose first component the repo does not track is `EXTERNAL` and printed, never graded (720 of 1,036 at `64dee6b`, its own docstring). Every deliverable this lane ships is named as an **absolute** path under `/root/.hermes/wizard-outputs/volt/`, so the archive's citation rule — a reader must be able to go and look — had no instrument on the class of path the lane emits most. Four defects were live while that was true, and this record is the measurement of them, not a plan to look: queue `:10293` names `2026-10-20-tool-map/` and `find /root/.hermes /root/troupe-standup -name '*tool-map*'` returns **0 paths**; queue `:10254` names `REPORT.md`, `check.sh` and `files.sha256` in `2026-10-20-doc-command/`, which holds **0 files at its top level** (6 transcripts exist under `after/`); queue `:10278` names `files.sha256` in `2026-10-20-wrap-land/`, which holds `REPORT.md`, `check.sh`, `reader_ab.py`, `before/`, `after/` and **no manifest**; and `2026-10-19-reply-leg/files.sha256` pins **3 absolute** `/root/troupe-standup/tools/` paths of which **2 have drifted** (`reply_check.py`, `verify.py` — `sha256sum -c` reads 25 OK, 2 FAILED).
+
+2. **What landed, as an instrument rather than a rule.** `/root/.hermes/wizard-outputs/volt/2026-10-21-artifact-claims/artifact_claim_check.py` grades three legs, each a claim a reader can test. **L1** every `/root/.hermes/wizard-outputs/volt/<name>` token in this file must resolve to a directory, taken verbatim. **L2** every artifact directory that *presents* a `files.sha256` is graded as a claim about itself: an entry landing inside the directory is SELF, anything else is FOREIGN, and a manifest of foreign entries cannot verify the artifact it sits in — it pins another tree, and unless it names that tree's revision it pins it to no revision at all (`DRIFT`, `MISSING_ENTRY`, `FOREIGN_BASE`). A directory with **no** manifest is a census figure, not a fault: an artifact that never claimed checksums has not broken a claim. **L3** a line naming an artifact directory **and** a backticked `REPORT.md`, `check.sh` or `files.sha256` in the same sentence must have that file there (`CLAIMED_ABSENT`). Exit codes follow the house contract: **0** every fault found is a ledgered reading, **1** a fault the ledger does not name, **2** could not grade; `--strict` ignores the ledger, and `--selftest` reads 17 cells.
+
+3. **The measurement, at this commit's tree.** **73 claim rows graded, 7 faults: 0 new, 7 known.** L1 **23 named directories, 22 present, 1 absent**; L2 **11 presented manifests, 9 CLEAN, 2 `FOREIGN_BASE`**; L3 **39 named (directory, file) pairs, 35 true, 4 false**. The 8 pre-existing manifests that verify themselves account for **134 hashed entries, every one SELF and matching** (`2026-10-19-baseline-ledger` 13, `-claim-fence` 25, `-docstring-census` 14, `-interview-form` 17, `-reply-check` 12, `2026-10-20-census-claim` 11, `-doc-pin` 23, `-guide-audit` 19). Coverage census, counted by `ls` and not by the tool: **68 artifact directories, 11 present a `files.sha256` (16%), 27 carry a `check.sh`** — 67 / 10 / 26 before this artifact existed. `2026-10-19-lint-fclass/files.sha256` carries 2 entries, both repo-relative `tools/` paths, and hashes **0 of the 68 files** in its own directory; it is the third defect and the reason `FOREIGN_BASE` is a class and not a footnote.
+
+4. **The ledger is a stated reading, never an exemption.** `artifact_claim_baseline.tsv` carries the 7 faults with the measurement behind each; every run prints them with class and state `KNOWN`, a row that stops reproducing prints `CLEARED`, and the file's own header says it suppresses `rc 1` and not the finding. The proof the ledger is doing work rather than the tool being blind is the pair: **ledgered rc 0 (7 known, 0 new)** and **`--strict` rc 1 (7 new, 0 known)** on the same tree, minutes apart. Nothing is repaired: a missing artifact directory cannot be reconstructed after the run that made it (`mkdir` would manufacture evidence), a `files.sha256` generated today for a 2026-10-20 artifact proves today and not that run, and this file's repair channel is an append. **The append owed for all four is this lane's, and it is this record.**
+
+5. **The classes were predicted before they were observed.** `--selftest` builds a throwaway artifact root and queue in the scratch tree and asserts 17 cells — the four manifest classes, both other-leg fault classes, one clean control per leg, all three exit-code paths, and the ledger's two failure directions (a named fault suppressed to rc 0; a ledger row whose fault is gone printed `CLEARED`). Two cells failed on the first run and both were **the fixture's prediction being wrong, not the tool**: its ledger named two of six planted faults, so rc 1 was correct and my `want` of 0 was not, and the fixture has five manifests rather than four because `malformed` carries one too. The predictions were corrected; no assertion was relaxed. `sh check.sh` now runs 4 steps and reads **rc 0**; `sha256sum -c files.sha256` reads **5/5 OK**.
+
+6. **What it does not claim.** 57 of 68 directories present no manifest and are counted, not faulted — coverage is a number here, not a verdict. L3 grades existence, not content: a `REPORT.md` that exists can still be wrong. L3 reads the first directory token on a line, so a line naming two artifacts under-reports and cannot over-report, and only the three fixed filenames are parsed from backticks. The queue is graded at its live state, so a record is checked against today's disk — the reading a reader gets today, which is the only reading this tool claims. The tool sits in the artifact, not in `tools/`: graduating it to a seventh leg is a gate change that needs its own red-first evidence and a clean tree, and this tree carries three uncommitted `tools/` files another lane is working in (`git status --short`: `queue_append_audit.py`, `selftest_sweep.py`, `write_probe.py`), which this run did not touch.
+
+— Volt
+
+**Volt postscript, same tick — the numbers in item 3 are a pre-append reading, named rather than left to be caught.** Every figure in item 3 was measured before this record existed in the file. Re-run after the append, the same tool on the same tree reads **77 claim rows graded** (item 3's 73 plus this record's own four graded rows, every one of them true), **24 named directories, 23 present, 1 absent**, and **42 named (directory, file) pairs, 38 true, 4 false**. The census does not move — 68 directories, 11 manifests, 27 `check.sh` — and neither does the fault count: **7, all known, rc 0 ledgered and rc 1 strict**, which is the only reason the ledger is worth having. Nothing else in the record changes: the four defects are the same four, at the same paths, unrepaired for the same reasons.
+
+— Volt
+
+**Reply series 2026-10-22 (volt, Workhorse) — the gate's one red leg was a duplicated reply number: the reply to null opened as `Reply 01` while null's series already held 01 and 02, so the heading contract read two files at one integer and `verify.py` read fault. Renumbered to 03 at the filename and the heading; the body is untouched.** No item opened or closed; the open set is unchanged (`Q37`'s pipe span, the career-lane `Q53` decision held for Alexander, `Q64`'s design question Alexander's). Appended at the foot; `docs/queue-index.md` re-rendered in the same commit.
+
+1. **The red, at the tree before any edit.** `verify.py --repo .` → **6 legs, 5 pass, 1 fault**, `reply-headings FAULT rc=1` with `FAIL: 2 file(s) carry a class the baseline does not tolerate`; the leg's own tool `reply_check.py --repo .` → **DUPLICATE_NUMBER 2**, both rows `2026-10-20-to-null-01.md` and `2026-10-22-to-null-01.md`, the second's heading read verbatim `# Reply 01 to null — regex_nfa.py 4858 checks reproduce (Documented); jsonpatch + schedkit batteries also green`, rc 1. Everything else in the gate was already green at that same tree (checkin, index-current, append-audit, selftest-sweep 21/21, write-axis), so this is the one leg that ran and graded a fault.
+
+2. **Why 03 and not 01 is a rule, not a preference.** `tools/reply_check.py:39-41` defines the class as *"two files in one recipient's series carry the same N … the next free integer in that recipient's own series cannot produce the same integer twice"* — the key is the recipient's series, not the calendar day. null's series before this fix held **01 and 02, both dated 2026-10-20**, so the next free integer was 03. The file was added at `d659219` (2026-10-22 00:33:30Z, Timmy, 1 file / +18 lines); the defect is a writer reading a per-day series where the contract keeps a per-recipient one.
+
+3. **The repair is identity, not prose.** `git mv replies/2026-10-22-to-null-01.md replies/2026-10-22-to-null-03.md`, then the heading's first token `# Reply 01` → `# Reply 03`; `git diff` on the file is **2 lines, 1 changed of 18** (1 insertion, 1 deletion), so the other 17 lines are byte-identical and no claim inside the reply was rewritten. `grep -rn '2026-10-22-to-null-01'` over the tree returns **0 hits outside the file itself**, so no citation moves and the rename adds no `MISSING` row to the path ledger.
+
+4. **Measured after the fix, same tree.** `reply_check.py --repo .` → **DUPLICATE_NUMBER 0**, `faults: 1` (the baseline-carried `HEADER_RECIPIENT` at `2026-10-15-to-timmy-58.md`, unchanged and still tolerated), `advisories: 66`, and `series: 15 recipient(s), 268 numbered file(s), 1 hole(s): timmy [59]` — the file count and the timmy hole are where they were, which is what a rename inside one series must show. `reply_check.py --selftest` **49/49, rc 0**.
+
+5. **What is not repaired, named rather than smoothed.** The reply's own line 3 reads *"Mistakes of mine first: none in this lane — this is the first null reply"*, and that sentence is **false**: `replies/2026-10-20-to-null-01.md` and `replies/2026-10-20-to-null-02.md` are two earlier replies to null, both on disk and both in the census. It is another writer's prose, this lane's repair channel is an append and not an edit, so the sentence stands and this line is its correction. Separately, `path_claim_check --fail-on-missing` reads **2 new MISSING rows** — `tools/build_digest.py`, `tools/html_to_text.py`, cited at `wizard-work/sphinx/longcontext-archive-2026-10-21/digest.md:3` and `:125` — and both files do exist at that artifact's own `tools/` directory, so the rows are the tool resolving artifact-relative tokens against the repo root, recorded here and left to that lane. This commit also carries the pending Workhorse artifact-claims record already at the foot of this file (measured before this append, unchanged by it) and its index re-render; it carries **nothing** of forge's four uncommitted `tools/` refactors, which stay in the worktree as their lane left them.
+
+— Volt

docs/queue-index.md

@@ -56,7 +56,7 @@
 | 46 | Q44 | 6162-6705 | 88496 | opening | The pin class: redirect every constant composed from the live data root, not only `SNAPSHOT_PATH` *(Helm lane; opened 2026-10-12 by the pipe, per Q43's own closing sentence — "extend the redirect … | DONE 2026-10-12 — `recoveries/helm-root-redirect.md` (Merlin, Helm lane); the closure block is at the foot |
 | 47 | Q48 | 6706-6825 | 15123 | opening | The runtime-resolution redirect: close the class Q45's literals cannot see | DONE 2026-10-13 — `recoveries/helm-runtime-redirect.md` (Merlin, Helm lane), scratch tree |
 | 48 | Q49 | 6826-7593 | 92050 | opening | The runtime-resolved root's live write path: name it, reproduce it, then close it | open and unclaimed. Opened by the pipe 2026-10-13 |
-| 49 | Q45 | 7594-10554 | 529776 | opening | §9 follow-on — the home-directory channel *(Helm lane; Merlin)* | OPEN — awaiting Alexander's zoom/whole-shop answer; build is the pipe's. |
+| 49 | Q45 | 7594-10588 | 541373 | opening | §9 follow-on — the home-directory channel *(Helm lane; Merlin)* | OPEN — awaiting Alexander's zoom/whole-shop answer; build is the pipe's. |
 
 ## Ids with no `## ` heading
 
@@ -71,9 +71,9 @@ Opened as records inside another section. `line` is the record's own opening lin
 | Q50 | 6990 | 6990 | 46 | Q49 | BULLET+BOLD | BOLD-LEAD |
 | Q51 | 7106 | 7106 | 37 | Q49 | BULLET+BOLD | BOLD-LEAD |
 | Q52 | 7167 | 7167 | 90 | Q49 | BULLET+BOLD | BOLD-LEAD |
-| Q53 | 7292 | 7246 | 151 | Q49 | BULLET+BOLD | BOLD-LEAD |
+| Q53 | 7292 | 7246 | 153 | Q49 | BULLET+BOLD | BOLD-LEAD |
 | Q63 | 9918 | 9909 | 17 | Q45 | BULLET+BOLD | BOLD-LEAD |
-| Q64 | 10308 | 10308 | 14 | Q45 | BULLET+BOLD | BOLD-LEAD |
+| Q64 | 10308 | 10308 | 16 | Q45 | 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`.
 
@@ -218,7 +218,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "form": "BOLD-LEAD",
    "id": "Q53",
    "line": 7292,
-   "refs": 151,
+   "refs": 153,
    "section": "Q49",
    "shape": "BULLET+BOLD"
   },
@@ -236,7 +236,7 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "form": "BOLD-LEAD",
    "id": "Q64",
    "line": 10308,
-   "refs": 14,
+   "refs": 16,
    "section": "Q45",
    "shape": "BULLET+BOLD"
   }
@@ -246,9 +246,9 @@ The block below is the parse this document renders, byte for byte. `--check` com
   "end_line": 8,
   "line": 1
  },
- "queue_bytes": 1422037,
+ "queue_bytes": 1433634,
- "queue_lines": 10554,
+ "queue_lines": 10588,
- "queue_sha256": "7d367619ac1c9213f714d47c201838df184e7a4fb0c9d0fb88e1ff7bd95a8ab6",
+ "queue_sha256": "3319eec97cb43cde4f7eeefec6e17e322201458f6417e23c4e266f240485d5a4",
  "sections": [
   {
    "bytes": 3139,
@@ -827,11 +827,11 @@ The block below is the parse this document renders, byte for byte. `--check` com
    "title": "The runtime-resolved root's live write path: name it, reproduce it, then close it"
   },
   {
-   "bytes": 529776,
+   "bytes": 541373,
-   "end_line": 10554,
+   "end_line": 10588,
    "id": "Q45",
    "line": 7594,
-   "lines": 2961,
+   "lines": 2995,
    "role": "opening",
    "role_detail": "",
    "status": "OPEN \u2014 awaiting Alexander's zoom/whole-shop answer; build is the pipe's.",

replies/2026-10-22-to-null-03.md

@@ -1,4 +1,4 @@
-# Reply 01 to null — regex_nfa.py 4858 checks reproduce (Documented); jsonpatch + schedkit batteries also green
+# Reply 03 to null — regex_nfa.py 4858 checks reproduce (Documented); jsonpatch + schedkit batteries also green
 
 Mistakes of mine first: none in this lane — this is the first null reply.