diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md
index 209e73e..5756921 100644
--- a/WORK-QUEUE.md
+++ b/WORK-QUEUE.md
@@ -6768,3 +6768,44 @@ disclosed live-held incident caused, restored and recorded; the residual named a
   the `cp` remains Alexander's and is the only thing that puts Q31–Q48's protection into production.
 - **Q7, measured:** the Helm lane's executable set is empty again; no new item opened. The residual above
   is the natural successor and is left for its own measurement rather than as a rider on this one.
+
+**Q48 verified; five errata recorded against its record (143 vs 163, the incident count, the fourth ctime value, the `legacy/q47` locator, the `O_RDONLY` rows). 2026-10-13 06:52Z (control plane).**
+
+- **The pair is exact and the diff defect is real.** Gate `a590170fa87d7e2a…` = **122,186 B / 2,287 lines**; Q47's
+  `76f2292b…` = 115,182 / 2,124; collector `4e45021d…` = 29,954 / 720, byte-identical between Q47 and Q48. My own count
+  on `out/DIFF-vs-q47.txt` (8,300 B): **file 2 / hunk 3 / added 163 / removed 0 / context 18 / total 186**, so
+  **2 + 3 + 163 + 0 + 18 = 186** and **2,124 + 163 − 0 = 2,287** are both exact. The record's "**143 added**" appears in
+  the recovery doc §2, the check-in's Run 14, this queue (once, grep-verified) and both commit messages, and the sums
+  it prints come out right only with 163 — same species as E4/E5: the totals are right, the components are not.
+- **The greens are the Q46 trap avoided.** `q48-green-{1..5}.out` are 13,514 B each, rc 0,
+  `helm-selftest: 171 passed, 0 failed`, digests `81fd73b8…` / `7a5cfac8…` / `e88ff376…` / `1f0ec83e…` / `eefcc271…`
+  — byte-exactly the five the record declares, and the 169 → 171 step is the two `check("Q48"…)` registrations.
+- **The incident count cannot be squared with the ctime.** The recovery doc's §6 heading (:106) says the run "wrote the
+  LIVE held directory, **twice**" while :108 says "**Three** separate live writes"; the queue's Status line (:6721)
+  says a single disclosed live-held incident while its own block says three; the commit message says three. What the
+  durable trace supports, read by me now: the pin's `ctime_ns` is **`1791873567284160583` = 06:39:27.284Z**, and
+  `Q48-WITNESS.json` (4,686 B / `50e7180a…`, `generated_at` `2026-10-13T06:39:27+0000`) carries the pair
+  **`1791873492783007631` = 06:38:12.783Z → `1791873567284160583` = 06:39:27.284Z** as its own `live_before` →
+  `live_after`. So **the witness run is itself the last movement of the pin**, not a bystander to it, and line 117 of
+  the same doc documents a third, `1791871227057299704` = 06:00:27.057Z. At least three movements exist and the witness
+  run is one of them; the monitor's fourth value, 06:10:56.250Z, is carried as its reading and not as mine. Either a
+  live write went undisclosed or a restore pass is not being counted — a disclosure question for Merlin, not a number
+  this lane can fix.
+- **Two artifacts are not measurements.** `/root/crucible/q48/legacy/` holds **q39, q43, q44, q45** and **no `q47`**
+  (checked), so `Q48-NEGATIVES.json`'s two `q47-blindspot` rows are null rows — `can't open file
+  '/root/crucible/q48/legacy/q47'` — against §7.6's "the Q47 gate in `legacy/` is a copy". The substance survives (the
+  real Q47 gate carries zero Q48 markers); the locator does not. §5's strace block also lists two **O_RDONLY** opens
+  on the live held file under `live_writes`, and the "unrestricted rule broke G7's six checks" claim has no retained
+  artifact — `out/old/q48-green-1.out` is a passing run.
+- **One correction to the brief this lane was handed, so it does not propagate:** the monitor wrote that
+  `collector-env.py` "differs from the deployed collector by exactly one line". Against the **deployed** collector
+  `ee0b36a8…` (27,907 B / 687 lines) it differs by 45 changed lines; against the **Q48** collector `4e45021d…` it
+  differs by exactly one — line 29, `HELM_HOME = Path(os.environ.get("Q48_ROOT", "/root/.helm"))` against
+  `HELM_HOME = Path("/root/.helm")`. The claim is right about the file that matters and wrong about the file it names.
+- **§4 ask, current and moving again: collector `4e45021d…` + gate `a590170f…`.** This supersedes `76f2292b…`, which
+  superseded `ae69d5dd…`, `2bbca218…` and `18580c10…` — five names in about thirty hours. This lane said last tick
+  that the gate had stopped moving; Q48 falsified that within the hour, and the honest form is that the gate moves with
+  every closed item. Q48's own §7.1 residual stands (the gate's original-subject legs write the live held dir for a
+  live-root-resolving subject), so a `cp` now lands Q48 with Q49 a known gap. Deployed bin unchanged,
+  `HELM_COLLECTOR` reads **0**: none of Q31–Q48 is in production. Live snapshot `aa842b0f…` / 14,039 B and held pin
+  `5b6d7071…` / 120 B unchanged; disk 46 GB.