diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md
index b50b33d..82cfeff 100644
--- a/WORK-QUEUE.md
+++ b/WORK-QUEUE.md
@@ -8500,3 +8500,14 @@ check), the census **0/0**, `HELM_COLLECTOR` 0 so Q40 stands, disk 45 G of 154,
 - **Live/deploy untouched:** snapshot 14,039 B / `aa842b0f…` / mtime_ns `1791479579475780303`; pin 120 B / `5b6d7071…` / `1791478687099553071`; five files in `/root/.helm/bin/`, `HELM_COLLECTOR` **0** → Q40 stands, none of Q31–Q45 §9 or the `Q45S10` unit in production; disk 45 G of 154 G (72 %). Queue served anonymously 200 / 1,014,835 B, identical to disk.
 - **PR #76 named once, unchanged:** open, mergeable, +398/−5 across 15 files, CI green, 0 reviews, `Closes #34` while **#34 carries three unchecked acceptance boxes** — a criteria decision for Alexander, not a code one.
 - **Standing, not re-argued:** the §4 `cp` (collector `4e45021d…` + gate `c56230e5…`), the `manifest_match` pin stale since 2026-10-08, Q13, Q9, Q19, and Q53 — the career lane, held for Alexander, item 7 expiring.
+
+**Erratum, mine, appended — the Run-27 acceptance block's "correction to the brief" does not hold: the two tokens are blob oids, and the brief prints blob oids by design. 2026-10-14 11:24Z (control plane; clock read immediately before this edit, queue 1,018,366 B).**
+
+- **What the block above claims.** "ONE CORRECTION TO THE BRIEF: its seed digests `4e3cca9cffd2` / `4f53c93a708d` are unsupported — measured at the exact revisions they are `decd3350585dd169` (18527 at `2b834d4`) and `83acffe0222d46e7` (13218 at `2b834d4^`)."
+- **Measured, and both classes are real.** `git rev-parse 2b834d4:recoveries/helm-discovery-channel-seed.md` → **`4e3cca9cffd2ace531030c9a1dd5bed25412ffab`** (18,527 B); `git rev-parse 2b834d4^:recoveries/helm-discovery-channel-seed.md` → **`4f53c93a708d95200e61f50d93a23c8b2119975b`** (13,218 B). Those two tokens are the file's **git blob oids** at exactly the revisions named, so "unsupported" is the wrong verdict for them. `git cat-file -p <rev>:<path> | sha256sum` gives **`decd3350585dd169…`** and **`83acffe0222d46e7…`** — the same two blobs' **sha256 content digests**, also correct, and the class the record's own `:432`/`:611` rows use. Two hash families, both measured; the sentence's verdict holds for neither.
+- **And the brief is not wrong to carry them.** The hand-off is `troupe_pipe_monitor.py`'s output, which prints the Gitea contents API's `sha` for each path — a blob oid. This tick's own listing line is `recoveries/helm-discovery-channel-seed.md efcc8351fba1`, and `git rev-parse HEAD:recoveries/helm-discovery-channel-seed.md` = **`efcc8351fba1a7383b22aa9dd568fa3794e5d9ae`**: identical, by construction, and the script's own docstring says "the file listing with blob shas". The tokens the block corrects appear in the recovered record only as listing lines — `2026-10-14_06-17-55.md:142` (`+recoveries/helm-discovery-channel-seed.md 4f53c93a708d`), `2026-10-14_08-33-20.md:143` (`+… 4e3cca9cffd2`), `2026-10-14_08-49-46.md:142` (`-… 4e3cca9cffd2`) — and the quoted pairing "18,527 B / `4e3cca9cffd2`" appears in no recovered brief: it is this pipe's own composition. *Tier: Documented for the blob oids, the sizes, the API field and the listing lines; Unrecovered for any brief text that called them digests, which the listing format does not carry.*
+- **Withdrawn with the sentence: the tally.** "The second misquote of lane artifacts in two ticks" does not survive either — the first instance it names describes prose ("it reported reply 50 listing 'the four cited artifacts'") that the monitor listing does not contain and that is not recoverable, and the claim sits in reply 51's §"Two readings" as well as in the block at `:8468`. The lane's own defect stands without a count.
+- **What survives, and it is why this family keeps recurring:** a token quoted without its class. The mirror defect is already logged above — reply 51's `git cat-file -s` rows at `:8467` printing content digests where the blobs belong (errata'd by appending to reply 51, and in reply 53 §0). Both are one error: a hash family swapped for its sibling, with no byte figure moving in either direction.
+- **Nothing else moves.** No item closed, none opened; no reply written this tick (Merlin's tip is still `3606d5f`, already answered by reply 53, and nothing of his is unanswered). Live state re-measured here, unchanged: snapshot 14,039 B / `aa842b0fd88037f8…` / mtime_ns `1791479579475780303` / ctime_ns `1791957230760646867`; held pin 120 B / `5b6d70716153c3f4…` / mtime_ns `1791478687099553071` / ctime_ns `1791957230761646950`; the five deployed files in `/root/.helm/bin/` with `HELM_COLLECTOR` **0** → Q40 stands, and none of Q31–Q45S10 is in production; disk 45 G of 154 (72 %). The §4 `cp` ask is unchanged in substance and is not re-raised. Nothing deployed, no another-party file edited, `decisions/` and `inbox/` untouched, nothing from `inbox/` quoted, no secret printed.
+
+— Timmy (control plane), Run-27 acceptance erratum