queue: Run 24 (Q45S10) recorded DONE at 32ad55b (landing fill 50bf350) and the Q45 section 9 follow-on thread CLOSED -- the pipe's verification block appended, with its own instrument's figures (five cells, live delta {} in all five, no restore), the three corrections (the landing correction's mispaired character count, the sandbox-path dependence of every stdout byte figure, the 406212 B that is Testimony only), the provenance defect on the two commits' author identity, and no new item opened with the reason stated: the lane's executable set is empty and the one channel the record names as next -- a destination handed over by a third party at runtime -- is a hypothesis with no fixture, which is the ruling this pipe already filed for the equivalent case. Standing and unchanged: the section 4 adoption cp (collector 4e45021d + gate c56230e5a075), the manifest_match pin stale since 2026-10-08, Q13, Q9, Q19, Q42, Q52, Q53. Repo visibility re-read (private false, one branch main) -- public is Alexander's decided KEEP PUBLIC state, not a mismatch; decisions/ and inbox/ unchanged; nothing from inbox/ quoted; no secret printed. Queue 978022 -> 983165 B, append-only, trailing newline and the single anchor asserted on bytes before the write.

WORK-QUEUE.md

@@ -8354,3 +8354,55 @@ queue's Q52 is Mercury's and Q53 the career lane's, so neither number is reused.
 - **Q7, measured:** the Helm lane's executable set is empty again — the adoption, Q9, Q13/Q19 and Q42 are
   human- or counterparty-gated, and Q52 is Mercury's and Q53 the career lane's. **No new item opened** — the
   next Helm unit after this is a decision, not a task.
+
+
+---
+
+**Pipe verification — Run 24 (Q45S10): VERIFIED and DONE at `32ad55b` (landing fill `50bf350`, correction `50bf350`).
+Timmy / control plane, 2026-10-14.** Re-run on the pipe's own instrument, not read from the lane's `out/`:
+`/root/crucible/q56-pipe-verify/` (report `out/PIPE-VERIFY-R24.json`, host-local per E13), byte-identical gate
+copies with the digests asserted (`c56230e5…` / `820b7afd…` / `cd43284f…`), the subject passed by
+`HELM_COLLECTOR`, and an independent digest-verified guard on both live objects. Five cells: `v1` shipped ×
+discover **rc 0 / 176-0 / silent**; `v2` disarmed × discover **rc 1 / 176-1** with
+`live_digest_in_artifact=True`; `v3` armed × discover **rc 0 / 177-0** with `PASS Q45S10`; `v4` shipped × real
+**rc 0 / 176-0**; `v5` armed × real **rc 0 / 177-0**. **Live delta `{}` on bytes/sha256/mtime_ns in all five; no
+restore needed.** Every figure the record carries re-derived here: the pair (147,151 / 2,798 / 127 on
+143,389 / 2,735 / 126, twin 147,074 / 2,796 / 127), `143,389 + 3,762 = 147,151`, the twin's 4 changed lines and
+−77 B, the decoy digest recomputed, the fixture = the real collector with 3 hunks and nothing else, the `+210 B`
+armed delta, **the check set identical between shipped and armed on the same subject** (176 → 177 is the one new
+check), the census **0/0**, `HELM_COLLECTOR` 0 so Q40 stands, disk 45 G of 154, and the raw-path read
+(`32ad55b` → 200 / 13,218 B / `83acffe0…` = disk = git). Landing arithmetic confirmed: `--numstat` 84/0, 192/0,
+184/0 → 460 insertions, 0 deletions; the check-in's 29,217 → 31,735 → 33,771 B = **+2,518 + 2,036 = +4,554**.
+
+- **Three corrections filed in `replies/2026-10-14-to-merlin-47.md`, none of them by re-argument.**
+  **(C1) Documented — one figure in the landing correction is mispaired.** It reads *"the queue 978,022 bytes =
+  959,834 characters (the 10,304 difference…)"*; measured at both revisions, `8ba7c8e` is **970,138 B / 959,834
+  characters** and `32ad55b` is **978,022 B / 967,603 characters**. `978,022` is 967,603 characters (difference
+  10,419) and the printed `10,304` is `970,138 − 959,834` — the *previous* revision's pair. The correction has the
+  cause right (the scripts print `len()` of a decoded string; the queue's `+7,769` is the character delta where the
+  byte delta is `+7,884`) and the check-in's other pair right (29,217 B = 28,840 characters); what is wrong is one
+  number, in the class the correction itself names. **(C2) Documented — byte counts are a property of the sandbox
+  path length**, not of the gate: the sandbox is `mkdtemp(dir=<the gate's directory>)`, so the pipe's runs in a
+  12-character-longer tree produced every figure **+12 per occurrence of that path in stdout** (occurrence counts
+  identical on both sides, 4/5/4/6/6; +48/+60/+48/+72/+72 predicted and observed). "Byte-stable" and "to the byte"
+  hold inside `q56/`; the portable citations are the verdict, the rc, the `+210 B` delta and the digest pair —
+  reply 46 §C2's finding, now decomposed on a second run set. **(C3) Testimony only — the 406,212 B reclaimed is
+  not re-derivable:** `out/Q56-CENSUS.json`'s `cleanup` records one path (`q56/__pycache__`) with **no byte count**,
+  so the sum of recorded per-path bytes is 0; the figure is the script's own pre-`rmtree` computation and is not
+  disputed, only tiered and given a one-line fix.
+- **One provenance defect, no content at issue.** Both Run 24 commits are authored `Timmy <timmy@stackchain.ai>`
+  (the clone's configured identity) where the lane's 82 earlier commits are `Merlin <merlin@agents.invalid>`, so
+  `git log --author=merlin` misses the run; fix at commit time with `git -c user.name=Merlin -c user.email=merlin@agents.invalid`.
+- **The Q45 §9 follow-on thread is CLOSED at `32ad55b`.** Its named residual — *resolve every path the subject
+  declares at runtime* — is discharged across four runs: Q48 (env, argv), Q52 (the home database), Q45S9
+  (`pwd.getpwuid`) and Q45S10 (the filesystem search). The lane's own §7 limits stand as the honest scope.
+- **No new item opened.** The Helm lane's executable set is empty, and the one channel the record names as next — a
+  destination handed over by a *third party* at runtime (a config file, a sibling process) — is a hypothesis with no
+  fixture, which is the ruling this pipe already filed for the equivalent case. Named, unclaimed, deliberately not
+  opened. Standing and unchanged: the §4 adoption `cp` (collector `4e45021d…` + gate `c56230e5a075…`), the
+  `manifest_match` pin stale since 2026-10-08, Q13's wording call, Q9, Q19, Q42 (zephyrus's), Q52 (Mercury's), Q53
+  (career lane, held for Alexander). Repository visibility re-read (`private: false`, one branch `main`) — public is
+  Alexander's **decided** state (`decisions/2026-10-06-human-gates.md`, *KEEP PUBLIC*), corrected at `e8002c8`, so
+  it is not a mismatch, not an open gate and not a fresh ask; `decisions/` (`eb34b4b4d781…`, `f126eba75613…`) and
+  `inbox/seed-2026-09-26.json` (`c05e6a0666d8…`, 9,484 B) unchanged, nothing from `inbox/` quoted, no secret
+  printed.