session 2026-08-17 coda: PENDING-146 (Class E) + the three placed-record corrections

Wrap amended after it was written, because the thread moved.

PENDING-146 filed at steward direction: the open list's unit is the id, the
decidable unit is the ## block. Upstream of everything PENDING-142 reaches, and
worse than a wrong verdict because the verdict is right.

Corrects my own report to the steward: FOUR blocks under PENDING-131 carry a live
Awaiting (parent, ADD-1, ADD-2, ADD-4), not the two I named. The jurist ruled on
that testimony while explicitly disclosing it had not verified ADDENDUM 1; running
that one check overturned the count. The disclosure was the instrument — no
control was pointed at it.

The answer key's specification changed before the key was drafted: it must be
keyed on ## BLOCKS, not ids, recording per block whether a live Awaiting exists
and at what tag. Keyed on ids it would have reproduced the unit that caused Class
E and graded green.

Resumption point revised and superseding the wrap's: three live options, steward
stopped tired without picking. (A) Move 2, closable in one sitting, no ruling,
and it is the fence itself. (C) Move 1, the emission-side fence over all 532
spans. (B) the answer key, session-sized. Recommendation absent a preference:
(A) then (C).

KG +3: the census-of-what-I-looked-at drift pattern; the disclosed-scope-limit
prevention; and the unit-of-a-pre-registration catch.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Y6t6qx7cpaCu5xGdD36u4

claude/memory/MEMORY.md

@@ -68,14 +68,14 @@ permalink: claude-memory/memory
 - Chamber-typography — *tracker not yet established*; moves live in per-session memories (2026-05-11 →) + `project-chamber-cruft-restoration.md` + `project-chamber-typography-mining-plan-2026-05-15.md`.
 
 ## Active Session
-> 🔑 **PULLING THREAD — THE ANSWER KEY FOR PENDING-142.** 69 filtered items, disposition **hand-read and committed BEFORE any implementation exists**, hash recorded (REVIEWED-122 cond. 1). **Cond. 10 says plainly the ruling cannot verify the census — the key is the only instrument that can.** A key written after the fix inherits the fix's reading of closure and passes by construction. ⚠ **PENDING-145 must be encoded in it**: (a)/(b)/(d) all still resolve *id → ruled*, so a key written against that model certifies the defect as correct.
-> ⚠ **ORDER IS BINDING:** key first, alone, hash recorded → then the (b) closing-verb enumeration goes for a **ruling** (it is a gate-design claim; unrecognized verb ⇒ NOT closed) → only then implement (d) framing (a)+(b). Report key-vs-implementation **in full, agreements included**.
-> ⚠ **REPORT AT EVERY WAKE UNTIL THE FREEZE LIFTS — N-now = 60/84 transcripts, 24 remaining** (REVIEWED-123 cond. 2). **The verification ladder is FROZEN, generally, from any source** (cond. 1) — 4 rows queued in PENDING-141's owed-entries list; OWED-4 is a *rewording*, merge on lift. 30-day review wired as `DEFERRED-DECISION date 2026-09-16`.
-> ⚠ **THE DAY'S SHAPE, SIX TIMES: a control whose SUBJECT is adjacent to its claim is not a check.** A count cited for a classification (equal both directions — 29 either way) · mtime cited as content age · git-date cited as content age (`3f9a89b` reset both) · a spread of outcomes cited as correctness · **and two of mine**, one inside my own verification.
-> ✅ **PENDING-142/143/144/145 filed; REVIEWED-122 + REVIEWED-123 received and EXECUTED**; docstring corrected (`aa745bc`); 16 trackers stamped superseded; 39 files' frontmatter repaired; wake detector rebuilt (4 defects, the scoped one was not the cause). All pushed `17669f2`.
-> ⚠ **STEWARD-OWED:** three transcription errors in the placed records (`"cannot be e-run"`; unfilled `REVIEWED-<next-1>`; `"REVIEWED-123 condition 9"` where cond. 9 is REVIEWED-122's). **PENDING-131 ADDENDA 2 and 4 await action and cannot say so** — ADD-4 (08-13) was suppressed on arrival by a ruling placed 08-10, and **PENDING-131 (c), the unbuilt fence, has NEVER appeared in the open list.**
+> 🔑 **PULLING THREAD — THE FENCE, and the answer key behind it.** Steward stopped 2026-08-17 tired, with three live options and no pick made. **(A) MOVE 2** — disposition the 25 line-addressable blockquote runs: **closable in ONE SITTING, needs no ruling**, and it is the fence itself rather than the scaffolding. **(C) MOVE 1** — fence the citation *at emission*, engine-side under D-1, covering all **532 spans** including sources added later; a build direction, carrying ADDENDUM 4's own control requirement (controls from **each structural class present**, `NOT ESTABLISHED` rather than zero where a class has none — four of that census's five defects escaped Mauss-only controls). **(B) THE ANSWER KEY** — session-sized, gates all of PENDING-142. *Recommendation absent a preference: (A), then (C). (B) when there is a full session.*
+> ⚠ **THE KEY'S SPEC CHANGED BEFORE IT WAS DRAFTED — PENDING-146.** REVIEWED-122 cond. 1 says "per-item". **If "item" resolves to *id*, the key reproduces the very unit that caused Class E and grades green.** Key it on `##` **BLOCKS**, recording per block whether a live `Awaiting:` exists **and at what tag** (ADD-2 §5 re-tags (c) `[PROPOSAL]` inside a `[HARDENING]` row). Caught only because the key was not yet written.
+> ⚠ **CLASS E (PENDING-146): the open list's unit is the `id`; the decidable unit is the `##` BLOCK.** Upstream of everything PENDING-142 reaches. Worse than a wrong verdict **because the verdict is right** — (d) reports PENDING-131 OPEN, correctly, and still hides that it carries four separate asks. **`governance_state()` shows ZERO rows for `131`.**
+> ⚠ **FOUR blocks under PENDING-131 carry a live `Awaiting:`** — parent, ADD-1, ADD-2, ADD-4 — **not the two I reported.** The jurist ruled on my testimony *and disclosed it had not verified ADD-1*; running that check overturned my count. The disclosure is what made it findable.
+> ⚠ **REPORT AT EVERY WAKE — N-now = 60/84 transcripts, 24 remaining** (REVIEWED-123 cond. 2). **The ladder is FROZEN generally, from any source** (cond. 1); 4 rows queued in PENDING-141's owed-entries list, OWED-4 a *rewording* to merge on lift.
+> ✅ **Filed today: PENDING-142/143/144/145/146; REVIEWED-122 + REVIEWED-123 executed; three transcription errors in the placed records corrected by the steward.** Wake detector rebuilt (4 defects, the scoped one was not the cause); 16 trackers stamped superseded; 39 files' frontmatter repaired; deferral checker was skipping the register at 546 KB. All pushed `7f891de`.
 
-- [Session 2026-08-17 — the instruments audited themselves and lost](session-2026-08-17-the-instruments-audited-themselves-and-lost.md) — a tooling day that became a governance day; every instrument examined was wrong and two of the wrongs were made by the hand fixing the others. **LITERAL Q: across the last ~10 sessions, when a defect in the executor's own instrument was found, WHO found it — a mechanism firing unbidden, the executor re-checking, the jurist, or the steward?** Count them: mostly-executor means the practice works and the mechanisms are decorative; mostly-jurist/steward means every "verified" between reviews does less work than it appears to.
+- [Session 2026-08-17 — the instruments audited themselves and lost](session-2026-08-17-the-instruments-audited-themselves-and-lost.md) — every instrument examined was wrong; two of the wrongs were made by the hand fixing the others. **Read the CODA for the revised resumption point.** **LITERAL Q: across the last ~10 sessions, when a defect in the executor's own instrument was found, WHO found it — a mechanism firing unbidden, the executor re-checking, the jurist, or the steward?** Mostly-executor ⇒ the practice works and the mechanisms are decorative; mostly-jurist/steward ⇒ every "verified" between reviews does less work than it appears to.
 
 ## Historical reference → MEMORY-reference.md
 Older archived-session pointers and the stable reference layer (steward profile · project-state detail · L1/L2/Chamber inventories · legacy pending-work · reference-file list) live in [MEMORY-reference.md](MEMORY-reference.md) — consult on demand; not loaded at wake. Recent cross-session trajectory comes from the Active Session entry above + the recent `session-*.md` files (wake §2.b.1).