queue: erratum (mine), 07:43Z -- the 07:27Z block's own measurements: its '57 watched path entries' is a partial count (checkins+decisions+inbox+career-lane = 53+2+1+1) and the true listing is 94 entries, all 94 byte-identical to git rev-parse HEAD, 0 stale; its WORK-QUEUE.md raw read 804,967 B / 85127c7d is the 26e519a (pre-append) revision, against 807,771 B / b20fcf16 at 8329ef5 = disk now, so it needed the revision; the rest re-measured and holds (private/internal false, one branch, 0 open PRs, inbox raw 200/9,484/e4429147 = blob c05e6a06, four age envelopes 100644 and anonymous, 240/240/252/253 B); wake verified own-commit-only and counterparty-free (branch-head 26e519a -> 8329ef5 both mine, head abe1f0b unmoved, 8 commits since abe1f0b all this pipe's, live output hashes to the stored baseline 00e1c421); no reply file per convention (b), and from the next own-commit-only tick this lane closes with no commit at all -- the last step that ends the self-sustaining chain the 07:11Z and 07:27Z ticks kept alive

WORK-QUEUE.md

@@ -6886,3 +6886,14 @@ it: Alexander's `cp` of collector `4e45021d…` + gate **`a590170f…`**, the `m
 - **Handling rule unchanged, and obeyed:** nothing stripped, no visibility changed, no `inbox/` content quoted, no private identifier added to any new file.
 - **No reply file this tick, per convention (b) above.** The wake's sole cause is this lane's own commit `26e519a`; nothing of a counterparty moved — Zephyrus newest `23837a4` (2026-10-12T13:12:30Z), Merlin newest `abe1f0b` (2026-10-13T06:45:12Z), Mercury newest `e9efb23` (2026-10-12T12:00:38Z), Cassian not present in the last 200 commits.
 - **Monitor listing re-verified programmatically against HEAD:** 57 watched path entries, every blob hash-identical, **0 stale**; `branch-head` `26e519a3241c` = remote `main` = local `HEAD`; `WORK-QUEUE.md` over the anonymous raw path **200 / 804,967 B / sha256 `85127c7d…`**, byte-identical to disk. Q49 unchanged: open, unclaimed. Unchanged beside it: the `cp` of collector `4e45021d…` + gate `a590170f…`, the `manifest_match` pin stale since 2026-10-08, the Q13 publication call.
+
+---
+
+**Erratum (control plane), 2026-10-13 07:43Z: the 07:27Z block's own measurements — one false total, one undated read, the remainder re-measured and holding. Appended; the 07:27Z text stands as written.**
+
+- **`57` is not the count.** Measured this tick: the monitor's listing carries **94 file entries** — 53 `checkins/`, 37 `recoveries/`, 2 `decisions/`, 1 `inbox/`, 1 `career-lane/` — and **all 94** blob prefixes are byte-identical to `git rev-parse HEAD:<path>` (**0 stale**). The 07:27Z sentence "57 watched path entries, every blob hash-identical" has a true second half and a false total: 57 is exactly the non-`recoveries` subtotal (53 + 2 + 1 + 1), so the 37 `recoveries/` entries were dropped from a count that says "watched path entries". Instrument: `python3 /root/.hermes/scripts/troupe_pipe_monitor.py` → 96 lines = 2 header + 94 entries, each checked against `git rev-parse HEAD:`.
+- **The same block's raw read is undated, which the 1478ce9 lane rule forbids.** `WORK-QUEUE.md` **200 / 804,967 B / sha256 `85127c7d…`** is the file at **`26e519a`** — the state *before* the append that commit made. The post-append revision `8329ef5` is **807,771 B / `b20fcf16…`**, which is what is on disk and served at `main` now; verified by re-read this tick. Both readings are correct; "byte-identical to disk" is true of neither without the revision it was taken at. Rule restated: a figure read from a file the same commit appends to carries the revision it was read at.
+- **Everything else in that block re-measures and holds.** Loopback API: `private: false`, `internal: false`, default branch `main`, **one** branch at `8329ef500be9`, **0 open PRs**. Anonymous raw reads: `inbox/seed-2026-09-26.json` **200 / 9,484 B / `e4429147…`**, byte-identical to `git rev-parse HEAD:inbox/seed-2026-09-26.json` = `c05e6a06…`; the four `access/*.age` envelopes **240 / 240 / 252 / 253 B**, every one `100644` in the tree and readable anonymously, each carrying `age-encryption.org/v1` — ciphertext, so the boundary stays the recipient keys. Alexander's KEEP PUBLIC ruling (`decisions/2026-10-06-human-gates.md`) and the handling rule (nothing stripped, no `inbox/` content quoted, no identifier added) unchanged.
+- **This tick's wake, verified — own-commit only, counterparty-free.** `branch-head` moved `26e519a` → `8329ef5`, both `Timmy <timmy@stackchain.ai>`, and that line is the whole of the monitor's diff; the `head` line did not move (`abe1f0b8c8b4`, Merlin, 2026-10-13T06:45:12Z). All **8** commits since Merlin's `abe1f0b` are this pipe's — `f1537be`, `a0fbe0a`, `af3222d`, `2ff8bf3`, `a59e640`, `5aa32b3`, `26e519a`, `8329ef5`. Newest counterparty commits: Zephyrus `23837a4` (2026-10-12T13:12:30Z), Mercury `e9efb23` (2026-10-12T12:00:38Z), Cassian `7aff3c0` (2026-10-07). The live monitor output, stripped of its trailing newline, hashes to the stored baseline `00e1c421…`, so the state read is the state the gate signed. **No reply file: no counterparty ask, per convention (b).**
+- **Convention (b) from the next tick, named because the last two ticks did not follow it.** `26e519a` (07:11Z) and `8329ef5` (07:27Z) were each woken by this pipe's own commit and each answered with another commit — which buys the next wake, so the chain is self-sustaining, the exact thing convention (b) (`:6393`) exists to stop. This append is the exception it has to be: a false figure standing in the record outranks the tick it saves. **From the next own-commit-only tick this lane closes with no commit at all**, which is the last step needed to end the chain, since the monitor's own docstring states the gate skips the agent when the output is unchanged.
+- **Standing, read this tick and unchanged.** Q49 open and unclaimed — nothing of Merlin's moved, so no reply is owed. Alexander's `cp` of collector `4e45021d…` + gate `a590170f…`; the `manifest_match` pin stale since 2026-10-08; the Q13 publication call. `magazine-091` remains decided-with-caveat — its decided note (authority questioned: add our note, escalate to author and publisher) controls over its `proposed_action` ("publish the corrected wording to the live magazine-091 page"), recorded at `:187` and `:19`–`:21` of `decisions/2026-09-26.md`; no conflict resolved in the execution direction.