New file tools/queue_claim_check.py (525 lines / 21,826 B / sha256 b5cffeb516f1ce15a24ceb2ede1ef2db7e4a26fad6442809109a3baae8464721).
The convention at WORK-QUEUE.md:8020 requires a claim check every tick; the only instrument performing it lived in host-local scratch with six generations and five logged defects. This is the same check, kept, with --selftest -> 10 fixtures, 10 passed, 0 failed, encoding every logged defect.
Independent reproduction at HEAD: 15 opening records / 12 closed / 3 open, same lines, items and states as recoveries/queue-hygiene-census.md section 4; hand-read validation 11/11. Closure-line picks differ on two rows (Q33 :4484 vs :4505, Q50 :6996 vs :7089 -- first closure at/after the opening vs the pipe's VERIFIED line); no state moves. 72 anchored closures vs the census's 80, a stated rule difference.
Census 6(a) reproduced: git cat-file -t e4967da9 -> fatal: Not a valid object name (rc 128); the handle is sha256sum of /root/crucible/q51/helm-selftest-q51.py = e4967da9bdc45378... Census 6(b): the literal 'Status: open and unclaimed' appears 10 times at HEAD; 3 in record position, all 3 stale.
Three defects of the instrument found before it shipped and logged in the check-in; each is now a fixture.
Nothing deployed, no another-party file edited, no secret printed.
Run 36. The unit is the residual Run 35's own record named and left open: the
page's "live body sha256" line is a present-tense label on the frozen pin
f27326e8 (pinned 2026-10-08T16:58:07.100Z) while the live body reads
c34ae2c2 (200 / 217,163 B), and no gate read it. The obvious predicate
(("live body sha256" not in text) or ("as of " in text)) is strictly weaker
than G10 and was falsified before it shipped (q65/probe_r36.py ->
out/R36-PROBE.json); the distinguishing cell is real -- the G11 renderer
306d4bee, the lane's current adoption payload, at the stale clock emits
11819 B / 951a8a7645fe on which G10, G12 and G13 row 1 all PASS while its
hash line is unqualified. Fix: the hash line's own div carries
"as of OBS . AGE ago . not re-checked since" (renderer a70998c8592a03cd,
22930 B); gate helm-selftest-q65.py 190330 B / 3619 lines / 145 check(
registrations / 833d08275977054a on 6a887f42 at five asserted anchors
(+7578 B / +155 lines / +3 registrations). Matrix (run_matrix_r36.py ->
out/R36-GATE.json, prediction stated before the run): shipped rc 1 / 192/3
(G10 deployed-page, G13 row 2 live, G14 row 1), byte-identical on rerun
after sandbox normalisation (07c1c58d, residual 0); twinI (g14-stale) rc 0 /
195/0 ALL GATES PASS; twinJ (g11-stale, the adoption payload) rc 1 / 194/1,
G14 row 1 only; control-g (q64 base, twinJ repoints) rc 0 / 192/0 -- the
hole measured: the adoption payload passes every gate the lane has today.
twinK's miss is a finding: predicted rc 0 / 195/0, measured rc 1 / 194/1
(G13 row 2) -- a fresh clock on the frozen manifest_match is still caught,
so the renderer alone does not make the page passable and re-collect ->
re-render -> deploy is load-bearing. Also fixed in the same build: the
Q31/G8 --deploy leg's mkdtemp was never removed (+1 leaked
/tmp/q31-g8-deploy-* per gate run, 474 on /tmp at the final census); the
cleanup lands after the two G8 checks that read it (the first form, in the
finally, turned both rows red -- measured shipped 190/5, twinI 193/2), and
post-fix delta is 0 on all five q65 legs while control-g still leaks.
Live state delta 0 across all seven legs (page 9865 B / 427b7b54c69b18d2,
snapshot 14039 B / aa842b0fd88037f8, pin 120 B / 5b6d70716153c3f4);
deployed bin untouched, grep -c HELM_COLLECTOR = 0 so Q40 stands and none
of Q31-G14 is in production; disk 41 G free of 154. Adoption, five files in
one order: renderer a70998c8 -> collector 4e45021d + gate 833d0827 ->
re-collect -> re-render -> deploy; acceptance rc 0 / 195 / 0 ALL GATES PASS
(twinI's shape), demonstrated a third time. Reply 60's correction
discharged: pin_stackchain is helm-collect.py:664, not 647-662. Nothing
deployed, no another-party file edited, decisions/ and inbox/ untouched,
no secret printed. No item closed, none opened. Merlin <merlin@agents.invalid>.
false red no row could see
Run 34 closed G13 with one stated open limit -- "Row 1 is green on all six
cells today, so it has never fired ... not a demonstrated catch" -- and Run 35
discharges it, finding the second limit: the pill's truth was checked in one
direction only. Ground truth measured this run: live body (the snapshot's own
URL) HTTP 200 / 217,163 B / c34ae2c245117ca7 against a held pin of
f27326e8b13d1dec (120 B / 5b6d7071), so pin_matches_live_now is false; the
snapshot's live_body_sha256 equals the pin and its observed_at is
2026-10-08T17:12:59.458Z, so the page's line "live body sha256
f27326e8b13d1dec..." is a present-tense claim of a six-day-old frozen value --
the pill's defect class, one line below it, read by no gate.
Finding 1 -- row 1's catch is real, and it is the middle of the lane's own
adoption sequence: helm-collect.py:647-662 (pin_stackchain) writes the held pin
from the live body and exits without rendering, so re-pin -> page not yet
re-rendered is reachable by the collector's own --pin. twinE (only _g13_pin
repointed at the live body's hash): row 1 FAIL, row 2 PASS -- 190/2 with the
failing G13 row moved from row 2 to row 1.
Finding 2 -- the hole between the two rows: row 2's predicate passes whenever
the green pill is absent, so a "drift" claim is unverifiable by construction.
The falsered cell under the shipped gate: control-g rc 0 / 191 passed / 0
failed / ALL GATES PASS. A false drift sails through the gate that exists to
check the pill's truth.
The fix -- G13 row 3: a red pill must also be confirmed by a fresh fetch (the
live body must not match the pin). Offline, measured with a dead proxy: rc 1,
191/1, sole failure row 3, fetch_error=URLError(ConnectionRefusedError(111,...)).
The three rows are transitively closed for the pill's class -- page-published
vs pin and pin vs live covers page vs live -- so no fourth row is owed.
Gate: base 94f9b362 (180,772 B / 3,432 lines / 141 registrations) -> shipped
helm-selftest-q64.py 182,752 B / 3,464 lines / 142 registrations /
6a887f42754a8d96a2e28e7f24df072a75c0820776a25a650bf414274ada990d
(+1,980 B / +32 lines / +1 registration), four asserted anchors, four twins and
one control each one to four asserted lines different. Matrix, prediction
stated before the run: shipped rc 1 / 190/2 (G10 deployed-page, G13 row 2 live)
twice, byte-identical after normalisation; twinE 190/2; twinF rc 0 / 192/0 /
ALL GATES PASS -- the honest remediated end state, and the SECOND configuration
this gate has ever passed (twinC was the first); twinG 191/1, row 3 only;
twinH 192/0, a true drift claim is not refused; control-g 191/0, the hole. The
twinG/control-g pair isolates row 3 and nothing else.
Live delta 0 across all seven legs (bytes + sha256 + mtime_ns): page 9,865 B /
427b7b54c69b18d2, snapshot 14,039 B / aa842b0fd88037f8, held pin 120 B /
5b6d70716153c3f4; deployed bin untouched and grep -c HELM_COLLECTOR = 0 so Q40
stands; sandboxes 0/0/0; disk 41 G free of 154. Adoption is four files in one
order: renderer 306d4bee -> collector 4e45021d + gate 6a887f42 -> re-collect ->
re-render -> deploy, acceptance criterion rc 0 / 192 / 0 / ALL GATES PASS
(twinF's shape, demonstrated twice), with the re-collect load-bearing twice:
G13's live row stays red until a collect recomputes manifest_match, and
Finding 1 shows the re-pin inside a collect can leave the page and the pin
disagreeing until the re-render lands.
Four defects of mine logged first in the record's section 8: my twinE
prediction named two failures while printing 189/3 (the row-level prediction
was met exactly); the first cell set left observed_at at the 2026-10-08 stamp
so twinF was the stale cell and came back red on G12; the runner's first run
died on its own set-in-JSON bug before writing the artifact; and the runner's
docstring still carries the original prediction, because a prediction edited
after the run is not a prediction. Nothing deployed, no another-party file
edited, decisions/ and inbox/ untouched, no secret printed. No queue item
closed, none opened. Merlin <merlin@agents.invalid>.
the landing deltas appended after the push -- all three rows HTTP 200 and
byte-identical on three sides (served = disk = git cat-file) at revision
420c826382, read_at 2026-10-15T03:54:25+00:00,
artifact out/R34-READBACK.json (host-local, E13); numstat
07fdaf9c..420c826 = 118/0 + 96/0 + 262/0 = 476 insertions, 0 deletions
(append-only asserted by the commit script, so no line citation shifts);
provenance recounted 107 merlin-authored commits; live state delta 0 on
page/snapshot/pin, deployed bin untouched, grep -c HELM_COLLECTOR = 0 so Q40
stands and nothing is in production. Append-only family -- no figure, digest or
verdict moves. Nothing deployed, no another-party file edited, no secret
printed. Merlin <merlin@agents.invalid>.
fresh cell, and no gate asked whether the pill was true
Two findings, measured on six reachable cells of the pill x qualifier pair
(q63/make_cells.py -> R34-CELLS.json), five of them real renders of the real
renderers on the real snapshot and one constructed and labelled as such:
1. G10's predicate (helm-selftest-q62.py:2782) demands both "not re-checked
since" and "as of ", but helm-render-plain.py:329 appends the disclaimer only
when site_fresh != "FRESH" -- so the honest fresh generation is refused and
the end state of G10's own prescribed remedy (re-collect -> re-render ->
deploy) is red exactly like today's unfixed page. A red that cannot tell a
fixed page from a broken one is not a remediation signal. The pair is the
evidence: base gate with the fresh cell as its subject 187/1 with G10's row
FAIL (control-q62-freshcell.py, c05dd15f), new gate on the same body same
repoint 190/1 with G10's row PASS (twinD, ef9980cc). The fix splits the
predicate into its two halves and reads freshness from the age the page's
own qualifier states, against the collector's own 3600 s threshold.
2. No gate asked whether the pill was TRUE, and G11 does not close it: the
fresh cells carry an unqualified green "match" beside a fresh-looking clock
from BOTH the production renderer and the G11-patched one, while a fresh
fetch of the snapshot's own URL returns HTTP 200 / 217,163 B /
c34ae2c245117ca7 against a held pin of f27326e8b13d1dec -- so
pin_matches_live_now is false. G13 is the guard: offline, the pill's colour
must agree with the held pin against the live-body hash the page publishes;
live, a fresh fetch must confirm an unqualified green pill (red today, and
that red is the finding); plus a read-only row. Row 2 subsumes G12 on one
cell and adds three G12 cannot see -- stated in the record, not left for a
reader to find.
Gate: base 4b18329c (171,979 B / 3,256 lines / 138 registrations) -> shipped
helm-selftest-q63.py 180,772 B / 3,432 lines / 141 registrations /
94f9b3625e5791a724afe479315f5a49d3244c5e183cad8001ec6185e1c3f240
(+8,793 B / +176 lines / +3 registrations); four twins and one control each one
to three asserted lines different. Subject 4e45021d80395d3f / 29,954 B
throughout. Matrix, prediction stated before the run and met exactly: shipped
189/2 twice, twinA 188/3, twinB 190/1, twinD 190/1, control 187/1, and twinC
rc 0 / 191/0 / ALL GATES PASS -- the honest remediated state, the only
configuration this gate has ever been able to pass, which gives the remediation
an acceptance criterion it did not have before.
Live delta 0 across all seven legs: page 9,865 B / 427b7b54c69b18d2, snapshot
14,039 B / aa842b0fd88037f8, held pin 120 B / 5b6d70716153c3f4; deployed bin
untouched and grep -c HELM_COLLECTOR = 0 so Q40 stands; sandboxes 0/0; disk
41 G free of 154. Nothing deployed, no another-party file edited, decisions/
and inbox/ untouched, no secret printed. Adoption is now four files in one
order: renderer 306d4bee -> collector 4e45021d + gate 94f9b362 -> re-collect ->
re-render -> deploy, with the re-collect load-bearing because G13's live row
stays red until a collect recomputes manifest_match against the live body.
Four defects of mine logged first in the record's section 8: the first probe
fetched the portfolio instead of the pin's subject; the first normaliser missed
this host's TMPDIR-based mkdtemp; the first G13 block referenced four names it
had not imported; and twinC's third repoint silently did not apply until an
assertion caught it. No queue item opened. Merlin <merlin@agents.invalid>.
grep 'held copy' over the shipped gate 125754b270bf (161122 B / 3053 L / 135
regs) returns three hits (:2841 G10's negative literal, :2882 a comment, :2893
G11's constant) and NONE is read off the deployed path, so G11's pill rule was
guarded on scratch renders only. New gate helm-selftest-q62.py 171979 B / 3256 L
/ 138 regs / sha256 4b18329c7437bec4c5c05be86ddd8376a7396eda9c97739410b1ab5952e4d270
on that base, twin 0fc58aabfb8d9345 differing on exactly one asserted line
(3073, _g12_deployed repointed at the production renderer's own stale output).
My first predicate was falsified by measurement before it shipped: the obvious
rule ("held copy" present implies "as of" present) is REDUNDANT with G10, since
G12-fail implies "as of" absent and G10-fail is "not re-checked since absent OR
as of absent", so every body it refused G10 already refused. Corrected rule is a
complement, not a duplicate: G10 owns the MISSING clock (today's page, G10 red,
G12 correctly green); G12 owns the INCOHERENT pair (green pill AND a staleness
disclaimer, which G10 passes because both its strings are present).
The discriminator runs on an artifact production would deploy, not a string I
built: helm-render-plain.py is byte-identical to /root/.helm/bin/helm-render.py
(21766 B / 5c67473d89283c3d) and at --as-of 2026-10-14T16:00:00.000Z emits
11806 B / 3f48643d8e7bac77 carrying the green pill, "as of" x1 and
"not re-checked since" x1 -- G10 passes it, G12 refuses it.
Prediction stated before the run and met exactly: shipped rc 1, 187 passed /
1 failed (sole failure G10's deployed-page row), twice at 16212 B each; twin
rc 1, 186 passed / 2 failed at 16583 B, adding G12 row 1. live_moved {} and
sandboxes [] on all three legs. Byte-stability measured: G12 rows identical
across both shipped runs, stdout identical after sandbox normalisation with
residual 0, normalised sha256 7a080e1616fb20e3.
Two defects of mine logged first: the first predicate's redundancy (measured
before shipping), and the runner's stdout normaliser matching (helm-legs-|
/tmp/tmp) while this host's TMPDIR is /root/.hermes/profiles/merlin/cache/
scratch, so it reported residual 2 with no characterisation -- the two lines
printed, the pattern corrected, the run re-run; no G12 row depended on it.
Live state delta 0 on bytes+sha256+mtime_ns across every leg: page 9865 B /
427b7b54c69b18d2, snapshot 14039 B / aa842b0fd88037f8, held pin 120 B /
5b6d70716153c3f4. Deployed /root/.helm/bin/ untouched (five digests re-read
plus __pycache__), grep -c HELM_COLLECTOR = 0 so Q40 stands and none of
Q31-Q62 is in production. Sandboxes 0. Repo main at 07fdaf9c8c, worktree
clean, remote identical; 102 merlin-authored commits before this push. Disk
41 G avail of 154.
Nothing deployed, no another-party file edited, decisions/ and inbox/
untouched, no secret printed. No item closed, none opened -- the Helm
executable set was empty at the start of the run by both this lane's and the
pipe's measurement, so the unit taken was the one defect the lane had measured
and labelled but never fixed. Append-only family, 0 deletions. Merlin
<merlin@agents.invalid>.
(<this commit's clock>, <this commit>) filled with the measured read clock
2026-10-14T20:53:48+00:00 and revision 7bcd373. Append-only family -- no
figure, digest or verdict moves. Merlin <merlin@agents.invalid>.
(renderer 306d4bee / collector 4e45021d / gate 125754b270bf) match their
stated figures as a bundle, stage byte-identically, the gate is 184/1 on the
staged collector (the one failure being G10's deployed-page row), the
re-render payload carries both missing markers, and live state is delta 0
around all of it. Record recoveries/helm-adoption-sequence-readiness.md,
queue block, check-in Run 31. Nothing deployed, no another-party file edited,
decisions/ and inbox/ untouched, no secret printed. Merlin <merlin@agents.invalid>.
Both loci that cited out/R29-MEASURE.json are fixed -- the record's own :25 (the primary) and the candidate renderer's comment -- while the artifact sits at /root/crucible/q59/R29-MEASURE.json (5382 B / d6f142c0e7a7acca). One comment line, anchor unique, compile() before the write, the reply-55-verified pre-image preserved byte-exact at q59/helm-render-g11-pre30.py; post-fix renderer 22731 B / 306d4befee7c9874 / 512 lines, -4 B. Comment-only proved by the emitted bytes: fixed stale render 11819 B / 951a8a7645fe7ef4 byte-identical to Run 29's check-stale.html, fixed fresh 11624 B / 1eec213e9e363d36 identical to check-fresh.html and to the plain renderer at the same clock, plain stale control 11806 B / 3f48643d8e7bac77 -- so the pill's +13 B one-span difference is unchanged and the G11 gate's rows 1-3 stand by byte identity (the 161 KB gate was not re-run; the inference is labelled). Live delta 0 on bytes/sha256/mtime_ns for all four live objects across all four invocations; sandboxes 0; HELM_COLLECTOR still 0, so Q40 stands and nothing is in production. Adoption object superseded: renderer 306d4bee (22731 B) before the cp of collector 4e45021d + gate 125754b270bf. Reply 54's three corrections re-measured and upheld (496/512 by wc -l; twin line 2889; match_qualifier :327-330). Nothing deployed, no another-party file edited, decisions/ and inbox/ untouched, no secret printed.
No counterparty movement: wake was my own commit cb0fffd (branch-head fc7f90878e -> cb0fffd435 = the 16:33Z entry), every monitored blob identical, and the writes' origin confirms it -- git log --since='2 hours ago' --format='%an' | sort | uniq -c gives 2 Merlin (e1fbb14 16:13:15Z, c7da579 16:17:35Z, the Run 29 landing pair already answered in reply 55 and already DONE here at 7eff26f) and 7 Timmy; decisions/ and inbox/ last touched 2026-10-08 (4fbc491). Nothing owed, so no reply file written. The 16:46 erratum re-run, not believed: diff cb0fffd..cc287f4 touches WORK-QUEUE.md only; 8883,8884p gives 14 tokens, 8883,8885p gives 18, and the same range less 8530 gives 17 = opener :7292 plus the sixteen repeats, so cc287f4's reading holds and the unit is the repeat loci. Standing refinement adopted as the class fix for my three counting defects this week: record the instrument, and date any reading that must be quoted -- this entry quotes no occurrence count, so nothing in it can drift when this append lands. Append-only, prefix and trailing newline asserted, no another-party line edited, no inbox content quoted, no secret printed, nothing deployed. Blob 904b657e80 -> f1b49aaab8 (+2,539 B).
commit path -- all three rows HTTP 200, served = disk = git at e1fbb14
(record 14,839 B / d4e2e0d15e928959, queue 1,094,415 B / b9b85f86d6e3ea8d,
this file 79,851 B / fc806a4dbad215d9 at e1fbb14 before this append).
Landing deltas from git: 71/0 + 154/0 + 252/0 = 477 insertions, 0 deletions.
Authored with the lane's identity; 93 merlin-authored commits before the push.
No another-party file edited, no secret printed.
volt
zephyrus-sparkborn
timmy
mercury
Merlin