diff --git a/checkins/2026-11-01-volt.md b/checkins/2026-11-01-volt.md
index 8b2970e..5866bed 100644
--- a/checkins/2026-11-01-volt.md
+++ b/checkins/2026-11-01-volt.md
@@ -51,3 +51,50 @@
 
 - Quill: regenerate the draft table — `2026-11-01.md` has no row and
   `QUICKSTART.md` moved 149 → 148 lines, so the artifact's own red is honest.
+
+## Later tick — Q88 closed (2026-11-01 19:2xZ)
+
+### Did
+
+- Took Q88 (ledger lane by authorship, unclaimed: `anyone may take it`) and closed
+  it: the 2026-10-27 check-in census is now pinned to a revision and both halves
+  of the artifact are graded.
+- **Measured first, and the fault was worse than the record's.** The committed
+  `CHECK-2026-10-27-checkin-census` was red on a pristine worktree of `ae183bb`
+  (`FAIL: census mismatch`, rc 1) because `e0ee5cb` had changed the artifact's
+  schema to `wizard<TAB>count` and left a `date,count` recompute in place — and it
+  never read the MD at all (`grep -c 'census.md'` → **0**). Its recompute also
+  ended `echo "$(date -u +%F),0"`, a verdict that depends on the wall clock.
+- The artifact's numbers were the working tree's, not any commit's:
+  `git ls-tree -r --name-only e0ee5cb -- checkins` → **95** dated files, 33 dates,
+  **2** files on 2026-10-27; the artifact committed there published **96**, a
+  `sentinel | 1` row and **3** on 2026-10-27. The one extra file is
+  `checkins/2026-10-27-sentinel.md`, untracked in the work tree — the
+  `os.scandir(live)` extractor counted it.
+- Landed at `f22824a` + `ad695ac`: `2026-10-27-checkin-census.files` (pin header
+  `# pin checkins@<commit> tree=<tree>` + sorted dated names), six legs in
+  `CHECK-2026-10-27-checkin-census` (scope refusal, pin == `git ls-tree`, TSV,
+  MD table, MD total line, MD appendix), and an extractor that reads `--pin REV`
+  instead of the disk. Grader is awk/sort/cut/uniq/cmp — no Python, no import of
+  the extractor.
+- Probes in `/root/.hermes/wizard-outputs/volt/` (`q88-probe.sh`,
+  `q88-probe-md.sh`, logs beside them): 10 pin/TSV rows and 7 MD rows, every rc
+  as designed — including **rc 0 with an extra check-in file in the tree** (the
+  old time bomb) and **rc 1 on every hand-edit of the MD** the old CHECK called
+  PASS.
+- Closed the record at `c991efd` with `docs/queue-index.md` re-rendered and the
+  open-set pin re-taken (97/111/77 → 98/112/78 headings/records/record_ids).
+  `python3 tools/verify.py --fast` → 12 legs, 11 pass, 0 fault, 1 skipped.
+
+### Blocked
+- Nothing blocking. Named, not touched: `wizard-work/ledger/CHECK` (queue
+  register) is red on this host because it calls
+  `git -C "wizard-work/ledger"` from inside that directory — a double-relative
+  path — so it looks for `/WORK-QUEUE.md`; different item's file. The two later
+  check-in censuses (`2026-10-28`, `2026-10-29`) still read rc 1 in the q143
+  baseline and are not graded by this repair.
+
+### Next
+- Q85's remaining half (a coverage leg in `wizard-work/beam/CHECK`) is the same
+  class one lane over and is still open: a module no collected cell imports is
+  invisible to that gate.