session 2026-09-14: the 59 answered (zero name their parent); PENDING-186 + PENDING-175 amendments; the memory write-guard is path-keyed

- The 59 unattributable register blocks: ZERO name their parent in their own
  text; all position-only. 37 cite only FOREIGN ids, so an id-keyed repair
  would mis-file every one. The obvious automated repair is worse than none.
- PENDING-186 [PROPOSAL] filed + AMENDMENT 1: the 'silent failure' ordering
  constraint is falsified (the harness warns at write time), and the real
  defect is that our write convention routed around that guard.
- Claude Code's near-limit MEMORY.md guard is PATH-KEYED: 5/5 warnings via the
  ~/.claude symlink path, 0/2 via the real dotfiles path at a LARGER size.
  Pre-registered and confirmed. MEMORY.md must be edited by the symlink path.
- PENDING-175 AMENDMENT 1: governance_item returning only the first block is
  no longer predicted but REPRODUCED, located at governance-mcp.py:199-202;
  the second defect is narrower than reported - it is a colon.
- Both amendments filed id+marker so they do not join the 59 they describe.

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

claude/memory/MEMORY-reference.md

@@ -287,6 +287,39 @@ Split out of [MEMORY.md](MEMORY.md) on 2026-07-06 to keep the wake-loaded index
 
 ## Archived (2026-08-20 — the fence, the vault spec and Trial 09 held; demoted on promote at the 2026-08-20 wrap)
 
+
+<!-- demoted from MEMORY.md at the 2026-09-14 wrap -->
+## Active Session
+> 🔑 **TWO OF THE THREE PARTIES READ THE SAME STORE AND COUNTED AS TWO.** The `governance` MCP
+> server's enum and `governance_search` cover `PENDING.md`/`PENDING-archive.md`/`REVIEWED.md` —
+> **exactly the executor's corpus.** Jurist+executor agreeing on a register question is **one check
+> counted twice.** Jurist-ratified. ⚠ **Recorded AGAINST Constraint 6.** → PENDING-89/-140, **banked
+> not filed**, venue 2026-09-16. ⚠ Establishing it needed the executor's transcript AND the MCP file
+> list — **reachable only from one of the two positions.**
+> ⚖ **THREAD ANSWERED 2026-09-14 — of the 59, ZERO name their parent; ALL are position-only.**
+> 0 claim a parent · 12 merely consistent with position · **37 cite ONLY FOREIGN ids, so an
+> id-keyed repair mis-files every one** · 10 cite none. **No automated repair is safe: per-block,
+> steward's hand.** Widening declared; instrument's own recognizer set the population.
+> ✅ **2026-09-12:** **PENDING-185** (`52d75fc`) — a state-claim falsifier whose unit cannot express
+> its claim; rec **(b) retire, as a LOSS**; both ends cross-referenced. · **REFUSED the jurist's
+> `~/CLAUDE.md` annotation** (Constraint 1); steward placed it, verified. **First live use of the
+> inbound-contamination clause, one day old.** · `gitea` **closed 57 commits**, `ls-remote`-verified.
+> ⚠ **'Ruling (B)': a referent-less term entered from the JURIST** (`08:44:58`, measured), which then
+> asserted a false provenance **three times** — the third, *'it came from the executor'*, inverted.
+> *A missing referent acquires one when a party guesses which store holds it.* **Act on none of it.**
+> ⚠ **Seb's 08-04 reply still unread** — L1 'blocked' UNSETTLED. 🎻 **D821 due 10-01.**
+> ⛔ **LIMIT MEASURED 2026-09-14 (docs, not inference): 25,000 B OR 200 lines, whichever first —
+> past it is NOT loaded at wake.** Now **24,292 B = 93–97% (unit unresolved); margin 708–1,710.**
+> ⚠⚠ **WRITE-GUARD IS PATH-KEYED: 5/5 warnings came via the `~/.claude/…/memory/` SYMLINK path;
+> real-path edits warn NOTHING at a LARGER size. ALWAYS EDIT MEMORY.md BY THE SYMLINK PATH.** ⚠ **"17.1 KB ceiling" was a MIS-TRANSCRIPTION** of the harness's
+> *compaction target*, and it ran ledger→index→briefing unchallenged. **The remedy is
+> [PROPOSAL]-grade, not a trim: 59% of this file is standing prefs that must fire WITHOUT a
+> lookup, so shaving them is loss-of-function wearing housekeeping's clothes.**
+> **2026-09-16:** joint -178/-179 + ladder-freeze review.
+> ⚠ **OWED-6** unchanged. N-now banked in `session-ledger-2026-09-13.md` (09-12: 62 raw, 31/25 ·
+> 09-14: 63 raw, 31/25) — it lived ONLY here, checked across 539 files.
+
+- [Session 2026-09-12 — the phantom referent, and the shared substrate](session-2026-09-12-the-phantom-referent-and-the-shared-substrate.md) — a falsifier fired truly on a change it cannot scope (PENDING-185); then a referent-less term from the jurist exposed that jurist and executor read the **same three register files**. **PULLING: the 59 unattributable blocks, still — today went somewhere real and somewhere else.** **FIRST MOVE: enumerate the 59; ask which name their parent in their own text. The split is the finding, not the count.**
 <!-- demoted from MEMORY.md at the 2026-08-26 wrap -->
 ## Active Session
 > 🔑 **TARBUCKLE IS WIRED — five surfaces, 125 controls** (`6f0ccde` `3df5e4f` `7a9dbf2` `acdbc09` `8a0e5c4` `cfbaded`). body · mumble · wake seam · wrap seam · `! tarbuckle`. §13.1 spec written LAST, per §12 — and four filed claims did not survive the substrate, which is why.