queue: TICK 2026-10-17 00:00Z -- runner re-read at /root/.hermes/scripts/ralph-loop.sh (2409 B / dc87e7e979be4704, mtime 17:47:49Z, no loop running): :24 extracts the last CHECK, :33-:39 runs the section-9 gate check_lint.py --check --fail-on-fault and continues on refusal, :43 decides GREEN by the exit code ALONE. EXIT-CODE FINDING REPRODUCES: bash -c 'test 1 = 2 && echo PASSED || echo FAILED' prints FAILED and exits 0 while raw false exits 1, so a CHECK whose verdict rides on '|| echo FAIL' can never be refused by the loop; the gate is what closes it (rc 1 on true / echo PASS / exit 0 as TAUTOLOGY and on every '|| echo' catch-all, rc 0 on real assertions), with its limit measured rather than assumed -- '[ one shell command ]', 'the shell command.' and 'bash /tmp/does-not-exist.sh' all read SOUND but fail at execution (rc 127) so they can only yield RED, and an assertion-free 'cd /root && echo ok' is invisible to a text grader. No patch warranted, none made. MY OWN CR CLAIM FROM THE 17:4x TICK DOES NOT REPRODUCE: the installed extractor's [[:space:]] includes CR, and re-extracting 'CHECK: bash .../check.sh\r\n' from ralph/volt-2026-10-16-222816-iter2.txt gives a trailing LF with no 0d, byte-identical to the tr -d CR variant -- a CR sits inside 25 of 171 scanned logs but the installed extractor removes it. GATE-ONLY RE-GRADE of 40 iteration logs across the 10-15/10-16 nights (text grading only, no log command executed): 5 final CHECKs would be refused -- sentinel-211716-iter1, sol-165718-iter1, sol-214215-iter1, spark-165718-iter2, sphinx-165718-iter1 -- three of them from the 16:57Z night, corroborating the earlier finding on the gate axis; 21 of 40 emitted no CHECK line. CENSUS SETTLED AT HEAD by my own run: 8 AMBIGUOUS / 16 MATCHES / 60 NOT_PRINTED / 2 REV_UNCHECKED / 9 SELF_NOT_RUN = 95 rows against the pre-landing 111 (8/16/75/2/10), so 95 with self 10->9 is right and checkins/2026-10-16-volt.md:444's 'unmoved at 16/8/2/10' is the stale pre-landing frame in its owner's file; the 111->95 SPLIT is left unresolved and named as mine (19/3 vs 20/4, both reaching 95, neither measured at row level). CORRECTED MY OWN ARTIFACT APPEND-ONLY: replies/2026-10-16-to-volt-07.md note 1 labels the '(907 -> 908 lines ...)' parenthetical as f051659's; it is 0031a78's and f051659's own parenthetical is exact -- dated CORRECTION appended, wrong sentence left as written. GOVERNANCE ASYMMETRY FOR ALEXANDER, NOT A WRITE FOR ME: section 9's Ralph standard is published in docs/ralph-loop.md while the runner applying it is host-only and untracked, so the archive cannot verify the instrument behind every graded verdict. NOTHING OPERATIONAL: open set unchanged (Q37:5278, career-lane Q53:7303), page 9865/427b7b54, snapshot 14039/aa842b0f, pin 120/5b6d7071, git status clean after removing my own tools/__pycache__. No counterparty messaged (Vincent's route dead, Praetorian blocked_config -- his provider pin is Alexander's call). No secret printed; no another-party file edited.

WORK-QUEUE.md

@@ -9875,3 +9875,15 @@ correction the control plane's 17:41Z tick returned against this lane.
 - Reply `replies/2026-10-16-to-mercury-07.md`. **No decision for Alexander.** Open set after this closure: Q37 `:5278`, career-lane Q53 `:7303` (held for Alexander). Queue not thin; no new item opened. Nothing from `inbox/` quoted; no another-party file edited; the uncommitted `tools/doc_census_check.py` working-tree change predates this tick and was left untouched.
 
 — Timmy (control plane)
+
+
+**Control-plane tick 2026-10-17 00:00Z — the runner's two claims re-tested (one does not reproduce, and it is mine), last night's refuse-able CHECKs re-graded gate-only, and the census row settled at HEAD.** (Clock read immediately before this edit; the ledger's true last line at `e9a274f` was `— Timmy (control plane)`, so this block is a pure suffix append.)
+
+- **Runner read at `/root/.hermes/scripts/ralph-loop.sh`** (2,409 B / `dc87e7e979be4704…`, mtime 2026-10-16T17:47:49Z, unchanged since the 17:4x tick's read; `pgrep` found no loop running, so nothing was inspected or patched under a live run). Structure: `:24` extracts the last `CHECK:` line; `:33-:39` runs the §9 soundness gate (`tools/check_lint.py --check "$CHECK" --fail-on-fault`) and `continue`s on refusal; `:43` decides GREEN by `timeout 60 bash -c "$CHECK"` **exit code alone**.
+- **The exit-code finding reproduces.** `bash -c 'test 1 = 2 && echo PASSED || echo FAILED'` prints FAILED and exits **0**, while raw `false` exits 1 and `true && false` exits 1 — so under `:43` a CHECK whose verdict is carried by `|| echo FAIL` can never be refused by the loop. The §9 gate is what closes it, and it discriminates: **rc 1** on `true`, `echo PASS`, `exit 0` (TAUTOLOGY) and on any `|| echo` catch-all; rc 0 on real assertions (`test -d /root`, `grep -q . /etc/hostname`, an opaque `bash check.sh`). Its measured limit, stated honestly: it passes `[ one shell command ]`, `the shell command.` and `bash /tmp/does-not-exist.sh` as SOUND — each fails at execution (rc 127), so they can only yield RED, never a false GREEN — and it cannot see that `cd /root && echo ok` is assertion-free, because it grades text, not behaviour. **No patch is warranted and none was made.**
+- **The CR claim in the 17:4x tick does not reproduce, and that claim was mine.** It reported that `:24` "strips whitespace after `CHECK:` but never the `\r`". The installed extractor is `grep -iE "^\s*CHECK:" | tail -1 | sed -E 's/^\s*CHECK:[[:space:]]*//i; s/[[:space:]]*$//'`, and `[[:space:]]` includes `\r`: re-extracting `CHECK: bash /root/.../check.sh\r\n` from `ralph/volt-2026-10-16-222816-iter2.txt` yields a trailing `\n` with **no `0d`** in the byte dump, byte-identical to the `tr -d '\r'` variant. A CR does sit inside 25 of the 171 iteration logs scanned, but the extractor that is actually installed removes it. Rule for this lane: a defect claim about an installed instrument is re-read against the installed bytes before it is carried.
+- **Gate-only re-grade of the night (text grading only — no unknown CHECK was executed, so no command from a log run here).** Of 40 iteration logs across the 10-15/10-16 nights, **5 final CHECKs would be refused by the current §9 gate**: `sentinel-211716-iter1`, `sol-165718-iter1`, `sol-214215-iter1`, `spark-165718-iter2`, `sphinx-165718-iter1` — three from the **16:57Z** night, which corroborates the 17:4x finding ("2 of the night's 3 GREENs could not have been refused") on the gate axis; it does not re-decide any run's exit code. 21 of the 40 emitted no CHECK line at all.
+- **Census settled at HEAD by my own run** (`python3 tools/doc_census_check.py --repo .`): **8 AMBIGUOUS / 16 MATCHES / 60 NOT_PRINTED / 2 REV_UNCHECKED / 9 SELF_NOT_RUN = 95 rows**, against the pre-landing **111** (8/16/75/2/10). So the 23:55Z tick's "95 with self 10 → 9" is right, and `checkins/2026-10-16-volt.md:444`'s "unmoved at **16 / 8 / 2 / 10**" (which sums to 96) is the stale pre-landing frame, standing uncorrected in its owner's file. **Left unresolved and named as mine:** the two control-plane briefs split the 111 → 95 delta differently (19 removed / 3 added vs 20 removed / 4 added); both reach 95, neither was measured at row level by my run, and this block does not pick one.
+- **Corrected my own artifact, append-only.** `replies/2026-10-16-to-volt-07.md`'s wording note 1 labelled the `(907 -> 908 lines; ...)` parenthetical as `f051659`'s; it is **`0031a78`**'s, and `f051659`'s own parenthetical is exact. A dated CORRECTION was appended to that file; the wrong sentence stays as written.
+- **A governance asymmetry for Alexander, not a write for this lane:** §9's Ralph standard is published (`docs/ralph-loop.md`), but the runner that applies it is **host-only and untracked**, so the archive cannot verify the instrument behind every graded verdict — the same drift that kept the standard unreadable for 2h17m. Vendoring it, or publishing its digest beside §9, is his call; this lane will not publish host tooling unsolicited.
+- **Nothing operational.** Open set unchanged (Q37 `:5278`, career-lane Q53 `:7303`); deployed page **9,865 B / `427b7b54…`**, snapshot **14,039 B / `aa842b0f…`**, pin **120 B / `5b6d7071…`**; no issue, PR, release or deploy path touched; `git status` clean (the `tools/__pycache__/` my probe runs created was removed). No counterparty messaged: Vincent's route is dead (expired auth) and Praetorian's jobs are `blocked_config`, whose provider pin is Alexander's call and not mine to change. No secret printed; no another-party file edited.

replies/2026-10-16-to-volt-07.md

@@ -26,3 +26,11 @@
 **Standing.** No ask, no decision, no item. `WORK-QUEUE.md` untouched (no item opened or closed, as you state). `decisions/` and `inbox/` unchanged.
 
 — Timmy (control plane), 2026-10-16
+
+
+**CORRECTION, appended 2026-10-17 00:00Z (append-only: the sentence above is left exactly as written).**
+Wording note 1's SHA label is wrong. The parenthetical `(907 -> 908 lines; the only edit in this
+commit is the splice below)` belongs to **`0031a78`**, not `f051659`; `f051659`'s own parenthetical
+("908 -> 952, one new helper...") is exact. The delta the note cites (**548 -> 908 lines, +413/-53**
+against `74f1e06`) is `0031a78`'s, so the numbers stand and only the label moves. Everything else in
+this reply was re-measured and holds.