session 2026-09-20: PENDING-187 authorized, PENDING-139 AMD 1 (third blind spot), index rotation

The cold-run framing retracted: /model-handoff §5 specifies report-and-stop and
a next phase from the artifacts, so the missing wrap was the protocol, not a
seam. Session memory, ledger, daily-note finalisation, and 8 KG lines (3 drift
patterns, 3 preventions, 1 blind-spot, 1 status).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

claude/memory/MEMORY.md

@@ -79,23 +79,35 @@ permalink: claude-memory/memory
 > near-limit guard is **PATH-KEYED**: 5/5 warnings via that path, **0/2 via the real
 > `~/dotfiles/claude/memory/` path at a LARGER size.** Same realpath. Editing the real path
 > **silences the only instrument that reports overflow** — and overflow is silent at load.
-> Limit = **25,000 B OR 200 lines, whichever first** (docs). Now **~24.1 KB; margin ≲900 B.**
+> Limit = **25,000 B OR 200 lines, whichever first**. ⚠ **A size written here is stale the moment the
+> wrap that wrote it finishes — MEASURE, never read this number as current** (`wc -c`). At the close
+> of the 2026-09-20 wrap: **24,1xx B / 117 lines ≈ 96%**, margin under 1 KB. The bytes bind, not the lines.
 > ⚖ **THE 59 ARE ANSWERED: ZERO name their parent; ALL position-only.** 0 claim · 12 merely
 > consistent · **37 cite ONLY FOREIGN ids — an id-keyed repair MIS-FILES EVERY ONE** · 10 cite none.
 > **The obvious automated repair is worse than none. Per-block, steward's hand.** ⇒ **PENDING-146's
 > convention question must settle BEFORE more amendments are appended**, or each one joins the 59.
-> **File amendments as `## PENDING-N — AMENDMENT 1:` (id+marker)** — proven this session to stay out.
-> 📌 **AWAITING RULING: PENDING-186** (index budget; (c) withdrawn, (e) favoured, five conditions) ·
-> **PENDING-175** (`governance_item` returns only the FIRST block — **reproduced**, `governance-mcp.py:199–202`).
-> ⚠ **READ BOTH BY `governance_read`, NOT `governance_item`** — the fetch tool hides their amendments.
-> ⚠ **If the 10 k hook-output cap is real, `wake-digest.py` sits at 8,136 chars = 81% with NO
-> write-time guard of any kind.** Unresolved: jurist cites primary source, my reader retracted to
-> could-not-assess. **One test settles it; it writes hook config — steward's call.**
+> **File amendments as `## PENDING-N — AMENDMENT 1:` (id+marker)** — proven 09-14, re-proven 09-20
+> (43/102/59 → **44/103/59**, predicted before the write).
+> 📌 **AWAITING RULING: PENDING-186** (index budget) · **PENDING-175** (`governance_item` returns only
+> the FIRST block) · **PENDING-139 + AMD 1** — now **THREE** drift-check blind spots, and the third is
+> a **UNIT mismatch, not a marker defect**: an in-place rewrite of a placed ruling leaves **no block
+> to see**, so the check reports `all resolve` and could not have said otherwise.
+> ⚠ **READ -186/-175/-139 BY `governance_read`, NOT `governance_item`** — the fetch tool hides amendments.
+> ⏰ **THE 84 CROSSING IS SIX AWAY.** N-now 09-20: **78 raw · 46 at ≥1 · 24 at ≥2**; **all +15 since
+> 09-14 are Tarbuckle** and a real session aged out. **RECORD the crossing with date+split; do NOT
+> grade** (REVIEWED-134 cond 2). **Nothing watches for it.** ⏰ **ladder-freeze 30-day review COME DUE
+> 2026-09-16, still open.**
+> ⚠ **Register commits are NOT atomic per entry** (12-commit measure, 09-20): 5 carried two entries,
+> 1 carried none, several bundled 2–9 unrelated files. Answers REVIEWED-140 row 4 — **the weight-delta
+> toy's ledger is STRONGER than the register it models, and the design does not say so.**
+> ⚠ **PENDING-187 AUTHORIZED** (REVIEWED-140, ruled 09-20) — build at slice 1, §2.4 fix in slice 2.
+> ⚠ **The open-item count is itself contested: 58 (digest predicate) vs 71 (heading-only) —
+> PENDING-142 owns why.** ⚠ 10 k hook-output cap still unresolved (jurist vs my reader); `wake-digest.py`
+> at 8,136 chars has **no write-time guard either way**.
 > ⚠ **Seb's 08-04 reply still unread** — L1 'blocked' UNSETTLED. 🎻 **D821 due 10-01.**
-> **2026-09-16:** joint -178/-179 + ladder-freeze review. OWED-6 unchanged. N-now 09-14: **63 raw ·
-> 31 at ≥1 · 25 at ≥2.**
 
-- [Session 2026-09-14 — the guard was path-keyed](session-2026-09-14-the-guard-was-path-keyed.md) — the 59 answered (zero name their parent; 37 booby-trapped); a jurist falsifier turned my own false claim into the day's finding, that our write convention had routed around a guard that already existed. **Eight false claims of mine corrected, almost none by re-reading.** **PULLING: the repair cannot be derived — PENDING-146's convention is the gate.**
+
+- [Session 2026-09-20 — the cold run was the protocol](session-2026-09-20-the-cold-run-was-the-protocol.md) — the register caught up with a cold Fable design session; **PENDING-187 AUTHORIZED**. **Three corrections of mine, the central one overturned by the steward in one sentence:** I called the cold run's missing wrap a seam, and `/model-handoff` §5 says the opposite — report-and-stop, next phase **from the artifacts**. **PULLING: the week needs a plan across 58 open items, and PENDING-146 is still the gate.**
 
 ## 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).