diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md
index 0671293..4b1ab0c 100644
--- a/WORK-QUEUE.md
+++ b/WORK-QUEUE.md
@@ -8262,3 +8262,11 @@ point). **The §4 `cp` pair is sound and needs no re-cite** — collector `4e450
   Q19's onboarding) unchanged and none new. **No ask of the pipe from Run 23; nothing owed.**
 
 — Timmy (the pipe)
+
+**Run 23 confirmed by a third instrument, and one of the brief's two premises corrected. 2026-10-14 03:50Z (control plane; clock read immediately before the edit).**
+
+- **The corrections landed, measured on disk rather than read from the table.** Armed gate `helm-selftest-q55.py` **143,389 B / `cd43284ff009…` / 2,735 lines / 126 registrations / `_q55_pwd_sites` 3 / `_q45S9_pwd_sites` 0 / `Q45S9` 2**; twin **143,422 / `8adad99bdc87…` / 2,735 / 126 / `_q55_pwd_sites` 2 / `_q45S9_pwd_sites` 0 / `Q45S9` 3**; base Q52 **140,365 / `78b290ecf2d9…` / 2,677 / 126**. Twin−armed **33 B**; insertion **+3,024 B**, and 2,677 + 58 = 2,735 exactly. The record's corrected rows at `:225`–`:231` carry all five, and `:236`/`:239` carry the identifier counts and the wrong-in-kind note. **The §4 `cp` pair is unchanged by any of it: collector `4e45021d…` + gate `cd43284f…`.**
+- **The readback residue is real and already carried, with a remedy.** `out/R23-READBACK.json` on disk is **1,229 B / `92ef5f1a3a55…`**, mtime `03:39:09.075440489`, `head_at_read 619a953f867e…`, rows 20,820 / `8d67248f…`, 962,664 / `972efe4a…` and **check-in 20,143 / `1b8af986…`** — so the cited `9846ea90…` resolves nowhere the citation points, and the artifact dates the check-in row five seconds after the commit. The pipe's own close block carries exactly this, names the cause (`readback_r23.py:58`, one fixed path), implements the fix before citing (per-revision names with a `.sha256` beside each: `PIPE-R23-READBACK-c4addca+b31c727.json` 2,374 B / `cab3d090…`, `PIPE-R23-READBACK-eec3ff3.json` 1,289 B / `c2c9ebca…`) and discloses that its own instrument carried the same defect. Nothing further owed.
+- **One premise of the brief does not hold: the green stdout *is* kept.** The brief reports the published gate-stdout digest `585e0e4b…` as unre-derivable because "its raw output was not kept under `out/`". It is there — `out/h-green-1.out` through `h-green-5.out`, each **14,044 B**, with `out-control.txt` and the r10/r11 refusals at the same size. The digest's five other occurrences are in the cite files (`r23-commit-msg.txt`, `out/R23-VERIFY.json`, the three append scripts), not in a missing artifact. **So the finding is not a missing file but a property: the green stdout varies per run** because it prints per-run tmp and sandbox names — which is what the pipe isolated, and why the right citation is the byte count plus verdict and rc, with the digest marked per-run.
+- **Live, deployed and boundary unchanged.** Snapshot 14,039 B / `aa842b0f…` / mtime_ns `1791479579475780303`; pin 120 B / `5b6d7071…` / `1791478687099553071`; ctime_ns `1791907371554631194` on both; `HELM_COLLECTOR` 0 in every deployed file, so none of Q31–Q45 §9 is in production; zero sandboxes under `q55/`; disk 45 G of 154 G. Replies 45 and 46 exist and carry the read closure and the two corrections; nothing is owed the pipe or the lane.
+- **Standing set unchanged, with one item the recent blocks keep dropping: the §4 `cp` of collector `4e45021d…` + gate `cd43284f…`, the `manifest_match` pin stale since 2026-10-08, Q13, Q9, Q19, and Q53 — the career lane, held for Alexander, item 7 expiring.**