session 2026-09-12: PENDING-185, the shared-substrate finding, and a referent no party held

PENDING-185 [HARDENING] — a state-claim falsifier whose unit is the FILE where the claim's
unit is a change made UNDER PENDING-149. It fires at [ESCALATE] on every future ~/CLAUDE.md
edit and cannot be fixed by reading more carefully. Recommendation (b), retire and mark
manual-only, recorded as a LOSS rather than dressed as a fix.

The day's real yield is smaller and worse: the governance MCP server's enumerated FILES and
governance_search cover PENDING.md + PENDING-archive.md + REVIEWED.md — exactly the corpus
the executor sweeps. So jurist and executor agreeing on a register question is ONE CHECK
COUNTED TWICE, not two positions converging. Jurist-ratified. Recorded AGAINST Constraint 6's
falsifiability clause, as that clause requires, and banked for PENDING-89 / PENDING-140
rather than filed. Establishing it needed the executor's transcript AND the MCP file list —
reachable only from one of the two positions it describes.

'Ruling (B)' was a term with no referent. It entered from the jurist at 08:44:58 (measured,
65 records before the executor's first use) and twice acquired a false source — the steward,
then the executor — each asserted rather than read. Act on none of it.

Also: the steward's ~/CLAUDE.md annotation, placed by his hand after the executor declined
the jurist's instruction to place it (Constraint 1; a jurist sign-off does not authorize one).
First live exercise of the inbound-contamination clause, one day after it landed.

Contains: session record, ledger, MEMORY.md promote + trim, MEMORY-reference.md demote
(lossless-relocation gate PASSED, md5 c9146a4f over 1,998 bytes), 6 knowledge-graph rows,
2 skill-harvest proposals.

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-11T18:41:58.797Z
+  modified: 2026-09-12T17:09:23.044Z
 permalink: claude-memory/memory
 ---
 
@@ -75,33 +75,31 @@ 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
-> 🔑 **AN ADDENDUM'S OWNER IS DECIDED BY WHERE IT SITS, NOT BY WHAT IT SAYS.** Four bare
-> `### ADDENDUM` blocks sit after PENDING-183, so every reader keyed on item ids assigns them
-> there. **Two are PENDING-139's**, and one of those records the *first* CLASS E mirror. In the
-> jurist's words, *the item documenting the defect is filed under the defect.* The repair is to
-> put the item id in each heading (a header edit, not a move), and it **awaits the steward.**
-> ⚠ The drift check counts **59** blocks it cannot attribute. That is the population; the four
-> are a sample.
-> ✅ **DONE 2026-09-11, in the jurist's order:**
-> - deferral `pending-168-count-unit-declared` stamped against REVIEWED-138;
-> - **PENDING-184 [FIX] filed (`2af4335`) before it was built (`37a2c86`).** The body selftest
->   was writing to the LIVE draws log. Two controls, D9 (live log untouched) and D10 (redirect
->   received), and a mutation shown to fail each;
-> - PENDING-180 CLOSED: **the second CLASS E mirror in two days**;
-> - PENDING-182 ADDENDA 1–2: `tick_id` sited in `fire_tick`. Its precondition is met and it
->   **awaits a ruling**;
-> - the steward's CLAUDE.md edit committed (`771bec6`).
-> ⚠ **SEB ANSWERED PENDING-94 (note dated 08-04, pushed 08-08, `fd4feb1`), AND NO ONE HERE SAW IT
-> FOR OVER A MONTH.** Whether L1 is still 'blocked on Seb' is **UNSETTLED** until the steward reads it.
-> 🎻 **D821 for the COE, recording due 10-01.** Report in vault
-> `06. Projects/Chamber Orchestra of Europe/2026/`; all 65 quotations exact.
-> ⚠ **The vault's git mirror pushes every file**, so heavy or copyrighted binaries live in
-> `~/Documents/Sources/<project>/`. This is the steward's decision, recorded in the vault CLAUDE.md.
-> ⛔ **MEMORY.md is over the harness's 17.1 KB warning.** Compaction by *relocation* is owed, in a
-> sitting of its own. 30-day ladder review and the joint -178/-179 review are both
-> **2026-09-16**. N-now was last measured at 59 (31 real / 28 mumble) on 09-10; re-measure at wake.
+> 🔑 **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.**
+> ⚠ **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.**
 
-- [Session 2026-09-11 — filed before built, and the D821 reading](session-2026-09-11-filed-before-built-and-the-d821-reading.md) — the jurist's sequence run to the letter, then Schubert for the COE. **PULLING: an addendum's owner is decided by where it sits, not by what it says.** **FIRST MOVE: read the two unowned blocks and establish their owners from the text; then ask the steward about the heading repair. Size the population before repairing the sample.**
+- [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.**
 
 ## 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).