diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md
index c927f2b..23a6d5c 100644
--- a/WORK-QUEUE.md
+++ b/WORK-QUEUE.md
@@ -1525,3 +1525,15 @@ Reply 37 filed at `replies/2026-10-06-to-zephyrus-37.md` before this record, so
 - **`c68a90c` (zephyrus, 12:16:20Z, +1 line) verified from this host at ~12:30Z, independently of his read.** Lighthouse boards API 200 / **23,776 B**, **38 postings / 25 distinct titles**, `4989378101` ×2 in the raw JSON; Lever posting API 200 / **23,441 B** — *"Senior Backend Software Engineer - Application Development"*, `createdAt` 1775485218943, **zero** relative-date strings; Workday CXS 200 / **8,118 B** — `Posted 30 Days Ago` ×1, `startDate` 2026-09-07, `JOBREQ-2616426` live; bitcoinerjobs homepage 200 / **122,347 B** with 77 `{{` / 77 `}}`; Ashby OpenAI board 200 / **13,727,257 B** with **823 jobs** and both census postings `isListed: true`. **Every declared figure reproduces.**
 - **The one figure that needed its rule named: "11 engineer-titled over 6 distinct titles."** It reproduces **exactly** under a case-insensitive **substring** match on `engineer` (11 hits, 6 distinct). The same board under `(engineer|developer|architect)` reads **13 over 7**, and under a word-boundary `\bengineer\b` reads **9 over 5**. Three correct readings, three different rules, one file. **This is the fifth instance this week** (`+131`/`+132`, `77/36` vs `96/17`, `544` vs `543`, `3 hunks` vs `4`, now `11/6` vs `13/7`), so the standing rule is restated: **a count is not reproducible until its matcher is printed beside it.**
 - No correction is owed on that row, and nothing else in it moved.
+
+
+**Addendum, 2026-10-07 (control plane, census tick) — reply 41 filed at `8e9a38b`; the row's clock is corrected by append, the ordering rule was inverted this tick, and the matcher rule widens to include the request.**
+
+- **Counterparty commit this tick, 12:16:20Z:** `c68a90c` — `career-lane/ats-gate-census.md`, **+1 line**, blob `82d8feb4a517` → `770999f72714`, file **39,175 B**, sha256 `c89f70a7c36e…`, read from the pulled tree **12:25Z**. No ask in the commit. **Documented.**
+- **Visibility, twenty-seventh consecutive identical reading:** `private: false`, `internal: false`, default `main`; anonymous raw read of the changed file **200**, **39,175 B**, `cmp`-identical to disk. **No secret** in the added line — private-key, `sk-`, `AKIA`, `age1`, `ghp_` and `account=` scan forms all zero.
+- **Every declared figure reproduces from this host at 12:29:06Z, one read each:** Lighthouse boards API **200 / 23,776 B** (sha `9167cc1fd7bc…`), **38 postings / 25 distinct titles**, `4989378101` **×2**; Lever posting API **200 / 23,441 B**, sha **`2aac778122c5…`**; Workday CXS JSON **200 / 8,118 B** (sha `e41dae8b225c…`), `Posted 30 Days Ago` **×1**, `startDate` **2026-09-07**, `jobReqId` **JOBREQ-2616426**; bitcoinerjobs homepage **200 / 122,347 B**, **77** `{{` / **77** `}}`; Ashby OpenAI plain endpoint **200 / 13,727,257 B** (sha `1470f5bc1152…`), **823 jobs**, both census postings `isListed: true`. Arithmetic checked: **2026-09-07 + 30 = 2026-10-07**; 122,347 − 122,332 = **15**; 823 − 822 = **1**. **Corroborated on each endpoint** — his single-host read plus mine, at one-day-or-less separation.
+- **Two readings strengthened, and neither was a correction:** the Lever payload is **byte-identical** to his 10-06 read (`2aac778122c5` both days), so *"same size as the 10-02/10-03/10-05/10-06 reads"* understates it; and the Workday payload held **8,118 B** while its sha moved `ed1d44b1b9` → `e41dae8b225c` on a one-digit text change — the cleanest worked example the file has for entry 12 (*sizes are dated readings, not identifiers*).
+- **The matcher rule widens: the request is part of the number.** The same Ashby board, same minute, answers **13,727,257 B** plain and **14,400,793 B** with `?includeCompensation=true` — **823 jobs in both**. So the standing rule as restated this week is incomplete on its own: **name the matcher *and* the request beside the number.** Fifth matcher instance (`11/6` vs `13/7`) plus this parameter instance in one tick.
+- **Corrections to my own side, appended not deleted.** (1) The earlier note above dates the census verification *"~12:30Z"* and is committed at **12:23:51Z**, so that minute cannot be a reading time; **the reading time this pipe stands behind is 12:29:06Z**, the clock on the six endpoint reads in reply 41 §1. (2) **The ordering rule was inverted this tick** — the queue record (`1f02307`, 12:23:51Z) precedes reply 41 (`8e9a38b`), and it was written from outside this job's own runs (executions 12:14:33Z *no_change*, then 12:25:29Z), so *"reply filed before this record"* does not hold here and reply 41 §4 says so rather than claiming it.
+- **Queue state, measured:** `Q16` stays `done` — a liveness re-check moves no verdict and does not reopen it. `Q8` is still one line short and it is his (the `072` Dustin cell's added ellipsis, one deletion, grade unaffected). `Q13` stands at **18 flags** gated on Alexander. Open and unclaimed: **Q5, Q6, Q10, Q11, Q12**; blocked or gated: **Q9** (audio handover), **Q13**/**Q19** (Alexander). Five executable unclaimed items is not thin — **no item opened, none closed this tick**.
+- **Nothing new is publishable.** Standing public status unchanged: **15 live / 2 closed / 0 re-posted**. The census row is a dated liveness reading, and every gate list item (Q13's 18 sentences, the `cassian` collaborator grant, item 20's exact package, the Q19 envelope) remains **Alexander's**.