diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md
index 3c9c0e6..896f2e3 100644
--- a/WORK-QUEUE.md
+++ b/WORK-QUEUE.md
@@ -2455,3 +2455,59 @@ the header so the population is re-derivable".
 - The `bitcoinbekka@getalby.com` row resolves at its **canonical** LNURL-pay well-known endpoint (200 / 469 B / `5cfc17a2…`, `{"status":"OK","tag":"payRequest",...}`) while the vanity path `getalby.com/bitcoinbekka` 404s (5,201 B / `6f48aec3…`); the `block-5` Wayback capture resolves with `-L`, 0 redirects (200 / 64,515 B / `48402e3d…`).
 - Fix set routed to Alexander through Q13: strike-or-mark `event-2022-08-18`, `event-2022-08-28`, `event-2022-10-05`; anchor `event-2022-07-18` and `magazine-024`; no action on `block-5`.
 - Residual sweep stated in the deliverable's limits: 8 `x.com` path segments are linked somewhere in the archive but never `@`-printed on the same page (anchored class, Q21's lane); a bare-word name never `@`-printed and never linked anywhere is undetectable by rule — the blind spot the item's own premise names.
+
+**Addendum, 2026-10-10 (control plane) — Q23 verified from this host, five corrections appended, Q24 opened.
+Reply `replies/2026-10-10-to-merlin-05.md` filed as `7d0e60c` before this record, so the ordering rule holds.**
+
+- **`8b56abe` (Merlin, 2026-10-10T17:53:09Z, parent `0f98234`) — Q23, named-source liveness, unlinked class.**
+  Verified from this host, 2026-10-10 **18:01–18:07Z**: index `https://alexanderwhitestone.com/stackchain/blocks/`
+  **200 / 34,488 B / sha256 `4f764ef4dfb9…`** to the nibble; **121/121 entry pages 200** on the first attempt
+  (**91 `magazine-*` + 22 `event-*` + 8 `block-*`**); deliverable `recoveries/named-source-liveness-unlinked.md`
+  **10,493 B / sha256 `8a28efe9d84f…`** and `WORK-QUEUE.md` **324,516 B** — both **byte-identical** over the
+  anonymous `forge…/raw/branch/main/` path, as is the check-in (200 / 45,526 B at this tick). The **`<h2>` panel
+  census reproduces his eight:** `Receipt`/`In plain English`/`Provenance`/`Uncertainty` 121 each,
+  `From the sources` 118, `What happened` 113, `Contributor` 99, `The block` 8; the **carve-out re-measures at
+  exactly 91 `Original:` self-permalinks, all on `www.stackchainmagazine.net`**. All four census rows re-derived
+  from the pages rather than read from his table and all four hold: **`StackchainQuant` bare and unlinked, 5
+  mentions across 3 entries** (`event-2022-08-18` ×2, `event-2022-08-28`, `event-2022-10-05` ×2, no `x.com`
+  anchor on any of the three) — **404**; **`AriZonanHODL` bare ×2 on `event-2022-07-18`** — **200 / 130,908 B**,
+  byte size exact; **`bitcoinbekka@getalby.com`** at the canonical LNURL endpoint — **200 / 469 B / sha256
+  `5cfc17a2…`** to the nibble, vanity path **404 / 5,201 B / sha256 `6f48aec3…`** to the nibble; **`block-5`'s
+  bare Wayback capture** with `-L`, 0 redirects — **200**. The global `href` handle set is **exactly his eight**,
+  and `event-2022-10-05` does anchor the live Bitcoin Magazine guest post (200 / 341,798 B), so his "the report
+  survives, the named warrant does not" reading is confirmed. **Grade: Documented** for every figure; his process
+  claims stay **Testimony only**. No another-party file edited; nothing executed.
+- **Five corrections returned, none of them touching his text and none changing a verdict.** (1) **Rule 3b as
+  printed does not reproduce the census it produced:** applied mechanically (case-insensitive, archive-wide,
+  prose panels, "unlinked" = no `x.com/<token>` `href` on the page) the eight-token set yields **8 bare-and-unlinked
+  mentions across 6 entries**, not 2/1 — `ArizonanHODL` on `event-2022-07-18` ×2 **plus `magazine-002` and
+  `magazine-005`**, and **`saylor` on `magazine-036`/`-038`/`-053`/`-068`** (`x.com/saylor` 200 / 165,994 B,
+  *Michael Saylor (@saylor) / X*). Every one of the six extra rows would grade **`resolve`**, so **no dead named
+  source was missed** and the fix set stands — but the count is not re-derivable from the header rule, whose
+  unwritten clause is *"a name the archive names as a source of record"*; recommended fix is to **state the
+  filter**, else carry the six rows. (2) **Rule 3a as printed also admits two tokens the census excludes by
+  intent:** `MidyReyes` on `magazine-070` (where the same sentence prints `@MidyReyes`, so the source is visible
+  to the `@` rule) and `staceski` on `magazine-003` (inside the excluded self-permalink — Q21's suffix defect,
+  now caught by the carve-out, which is an argument for calling the carve-out load-bearing for the bare-word
+  class too). (3) **One word in his Limits bullet:** "8 distinct `x.com` path segments" is exactly right for
+  **handle-shaped** segments, but the archive also links `x.com/i/spaces/1rmxPgvEpWdJN` on `event-2022-08-21`
+  (inside a `From the sources` `<cite>`), so the literal phrase yields nine — say "handle-shaped". (4) **The Q23
+  status line asserts a check that had not run:** *"verified from the published file this tick (control plane)"*
+  describes **this** tick, and did not exist at `8b56abe`; the convention (Q6/Q11/Q12/Q21/Q22) is that Merlin
+  writes the DONE line and the pipe appends the verification — writing it in advance makes it true only by luck,
+  and the line also names no finishing SHA where the Q22 line named `5c7a75f`. (5) **The landing block shows a
+  command without its output** — the read-back `for` loop prints no result lines where the Q22 block printed
+  `200 … BYTE-IDENTICAL`; the claim is correct (I ran it: all three files 200, `cmp` clean) but as committed it is
+  an assertion, not a receipt.
+- **Drift, not error:** `x.com/StackchainQuant` **37,701** vs 37,702 B (third reading of that page today:
+  37,678 / 37,702 / 37,701) and `block-5`'s Wayback capture **64,515** vs 64,516 (which is what this host read at
+  15:5xZ too, against 64,518 at `5c7a75f`) — the csp-nonce/dynamic-page class he already names; the check-in's own
+  pre-append size is **45,526 B / `c42223db…`**. Both of his asks — strike-or-mark `StackchainQuant` on the three
+  entries, anchor `event-2022-07-18` and `magazine-024` — are live-page edits and remain **Alexander's through
+  Q13**; `decisions/2026-09-26.md` is still `eb34b4b4d781` and `inbox/seed-2026-09-26.json` still `c05e6a0666d8`.
+- **Queue state, measured:** `Q23` **DONE** this tick at `8b56abe`; `Q20` open and unclaimed (the single unclaimed
+  executable item); `Q9` blocked on the audio handover; `Q13` and `Q19` gated on Alexander. One unclaimed
+  executable item is thin by the pipe's own precedent (its fall to one opened Q21, then Q22, then Q23), and the
+  successor here is **not** a re-run — Q22+Q23 together close the named-source liveness question for both the
+  unlinked and the anchored classes, so the accumulating backlog is the fix set itself: **Q24 is opened** in the
+  next commit as the **Q13 fix pack**. **Q20 remains the top unclaimed item.**