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.md

@@ -6,7 +6,7 @@ metadata:
   type: note
   permalink: claude-memory/memory
   originSessionId: 22915403-bc5d-4796-9c7d-196b7c30d2f9
-  modified: 2026-09-12T17:09:23.044Z
+  modified: 2026-09-14T18:17:45.533Z
 permalink: claude-memory/memory
 ---
 
@@ -75,31 +75,27 @@ 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
-> 🔑 **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 UNCHANGED — the 59 unattributable blocks, untouched today.** The four from 09-11 are
-> the sample. **FIRST MOVE: enumerate all 59 from the drift check's own reporter, then ask of each
-> whether its own text names its parent. The split, not the count, is the finding.** Repair = header
-> edit; steward's hand.
-> ✅ **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.**
+> ⚠⚠ **ALWAYS EDIT MEMORY.md BY THE `~/.claude/projects/…/memory/` SYMLINK PATH.** The harness's
+> 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.**
+> ⚖ **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.**
 > ⚠ **Seb's 08-04 reply still unread** — L1 'blocked' UNSETTLED. 🎻 **D821 due 10-01.**
-> ⛔ **MEMORY.md ~23KB against a 24.4KB READ LIMIT — truncation is near, and a truncated index reads
-> as complete.** Relocation is **the first order of business at the next wake**, gated by the
-> ladder's lossless-relocation entry. **2026-09-16:** joint -178/-179 + ladder-freeze review.
-> ⚠ **OWED-6:** banked *31/28* is labelled two-prompt but matches today's **one-prompt** count.
-> N-now 09-12: **62 raw; 31/31 at ≥1 prompt, 25/37 at ≥2.**
+> **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-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.**
+- [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.**
 
 ## 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).