session 2026-09-03: the index had become the record — breach fixed, Active Session rotated

Session record + MEMORY.md rotation (prior Active Session demoted verbatim to
MEMORY-reference.md, 9 of 9 non-blank lines conserved) + 4 KG rows.

MEMORY.md 23,714 -> 20,567 bytes; headroom now 4,419. The trim itself landed in
2171d91; this is the wrap half.

Recorded for the next wake: the wake digest's --selftest now fails on every run.
Its end-to-end control samples the 13 most recent transcripts and all 13 are
Tarbuckle mumbles (~66 KB, one human turn each) — PENDING-178's mumble pollution
displacing real sessions out of a second instrument. Not filed; the moratorium is
undecided and this belongs with -178 when that is ruled.

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

claude/memory/MEMORY.md

@@ -73,17 +73,13 @@ 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
-> 🔑 **THE GATE THAT SHOULD HAVE EXISTED — built in an hour, 42 days late, and it found what no gate can see.** The FIX-lane check-in (30 days overdue) unblocked REVIEWED-67's unconditioned per-conversion typography gate. `scripts/verify_typography.py`: converter-agnostic **by construction**, censuses classes in an **independently-formed witness**, 9 controls both directions written before first execution. Ran the corpus's **first typography byte-census**: **`curly_single` 4,608 → 4** — `‘tradition’` → **`' tradition ' .`**, docling *inserts spaces around the flattened quote*. **Tier-3 word-boundary damage at 4,608 sites** (pilot: 16). ⚠ **`body_word_conservation` is structurally blind** — punctuation-stripped tokenization reduces both to `tradition`; the gate's unit is the word, the damage lives below it. **`ligatures` 2,013 → 0**, unpredicted and benign on reading — *the instrument reported the vanishing; the human judged it harmless.* **Poppler recovers all of it ⇒ the defect is the FRONT-END's, not the class's** (⚠ pdftotext+pdftohtml are BOTH poppler — one engine read twice, not corroboration). Lane **HELD**; gate wired to all three terminal lanes.
-> ⚠ **TWELVE INSTRUMENT ERRORS OF MINE, AND NONE CAUGHT BY MY OWN FIRST PASS.** 🔑 **Every catch crossed party lines; nobody caught their own.** Constraint 6 working — the day's only evidence *for* the apparatus, on a day that mostly produced evidence about its cost. **Three catch-modes now distinguishable: a CONTROL verifies an encoder · RECONCILIATION catches a correctly-encoded measure of the WRONG THING (2 of 12, and nothing schedules it) · READING THE SUBSTRATE catches a handle with no referent.**
-> 📌 **THE QUAGMIRE IS A QUEUE.** Filing is cheap for the executor, ruling is expensive for the steward ⇒ unbounded arrivals, one server, steady state 62 items. **Moratorium proposed to 2026-09-15** (detection continues, filing stops) + a hard cap + one class pass over the 62. **Jurist accepted and bound itself**, and corrected the criterion: *a flat register with ZERO graduated texts is a FAILED moratorium, not a passed one.* **Steward's decision owed.**
-> ⚠ **`RE_ID` CANNOT PARSE THE REGISTER'S OWN HOUSE FORM.** `## REVIEWED-133 (PENDING-137) — …` backtracks to the bare token `REVIEWED`; entries **130–133** are invisible to the integrity control and any future amendment to them reports a **FALSE ORPHAN**. **Fix the REGEX, not the entries — REVIEWED-132's own disposition says "Do not touch placed headers."** Bounded `[FIX]`, ~20 min. *Steward raised it; agreed at the wrap.*
-> 📌 **STEWARD OWES:** the **moratorium decision** · rule **PENDING-171** (unblocks the 322 unread of 362) · **-177** (now with measured evidence; Tier-3 not Tier-2) · **-178** · -160 · -168 · the §5 regrade ruling.
+> 🔑 **THE INDEX HAD BECOME THE RECORD.** `MEMORY.md` breached its load budget and was being **silently truncated at wake** — but the cause was not bulk. Five tracker entries had grown into paragraphs, and for **three the index was the SOLE custodian of live state**: the studium tracker stopped at **2026-08-13** while the index carried engine news to 09-01 · the Fool's only link was a **sealed seed**, with nowhere legitimate to append · L1's replay **mechanism** (`minCursor` is a minimum over 11 modules, two never participate ⇒ pinned at 0 **by construction**) and **completion criterion** (uninterrupted run length, not rate) existed nowhere else. All relocated verbatim; **Tarbuckle got a tracker**. 26,803 → 23,714 (`2171d91`, both remotes verified).
+> ⚠ **PRUNING WOULD HAVE BEEN HARMFUL.** The cut took its rule from the file's own Index discipline — trackers are pointers — and so **left "Rules that fire silently" untouched**: those keep their text inline because they fire when I would not know to look. Cutting the loudest lines would have removed the catches and still left three workstreams undocumented, now deleted rather than truncated.
+> ⚠ **THE CANARY WAS CLEAN AND ITS SELFTEST WAS FAILING** (86/87). The failing control samples the 13 most recent transcripts; **all 13 are Tarbuckle mumbles** (~66 KB, one human turn each). **PENDING-178's defect at a SECOND site** — it will now fail on every run, and a control that always fails is one everyone learns to ignore. The **pointer** controls, which the trim rests on, all pass. Not filed (moratorium undecided).
+> 📌 **HEADROOM IS THIN AND THE MECHANISM IS UNFIXED.** Rotation handles the Active Session block; **nothing handles slow growth in the tracker list** — which is how this breach formed.
+> 📌 **STEWARD OWES:** `~/.claude/agents` under version control (**directed; before anything else edits it**) · the **moratorium decision** · `RE_ID` regex `[FIX]` · PENDING-171 · -177 · -178 · -160 · -168 · the §5 regrade.
 
-> ✅ **AFTER THE WRAP — `/doctor` ran; the chamber-library trim is COMMITTED (`c7c30ac`, 54,129→22,530 chars, both remotes current).** Also fixed: **8 sub-agent name collisions** across 21 files — 15 renamed, 0 remain, and the harness surfaced 15 previously-invisible agents on the spot · 4 invalid `SKILL.md` frontmatters (latent, not live) · `plane` MCP disabled (0 calls / 41 sessions) · `permissions.defaultMode: auto`. **PENDING-169 §5a** (`440d18e`): `tarbuckle-wrap.py` = the `Stop` hook at **median 6.7 s / max 13.6 s**, an order of magnitude above every other hook, on the blocking path at every session end — filed against the **existing** 2026-09-08 trigger, no duplicate block. **Steward: 8 September, with the rest of Tarbuckle.**
-> 📌 **NEXT SESSION, STEWARD-DIRECTED — `~/.claude/agents` IS NOT UNDER VERSION CONTROL.** 51 hand-edited files, **0 tracked**, not a symlink into `dotfiles`. **Every other governed surface is tracked**; this one holds *executable configuration* — an agent definition determines what a delegated sub-agent is told to do — so an untracked, unattributable edit there is a governance surface, not a convenience. ⚠ **Found by accident** (`/doctor` was looking for name collisions), and **no instrument was positioned to notice it**. NOT filed — the moratorium is undecided and the instruction was *attend to it*, not *file it*. ⚠ **The 15 renames still have no history — ADDENDUM 1's mapping table is the only undo.** Track the directory BEFORE anything else edits it. Open: dotfiles or its own repo · are all 51 the steward's or some vendored · does `~/.claude/skills` (already symlinked into dotfiles) set the precedent.
-> ⚠ **14th instrument error, and it broke a discipline the repo documents:** I reported *"chamber-library pushed ✓"* having pushed only `origin` — **`github` was 9 behind** and stayed behind through the whole wrap while the record said clean. The repo's `CLAUDE.md` says *"push to **both**"*. Both current now.
-
-- [Session 2026-09-01 — the gate that should have existed](session-2026-09-01-the-gate-that-should-have-existed.md) — a day that *became* the thing it diagnosed. Wake found control (c)'s false positive (a Tarbuckle mumble is unattended **by design**) → PENDING-178, the counter's **unit**. FIX-lane check-in held: **EXTENDED PROVISIONAL, n=1**, trigger re-based to use, ⚠ half not machine-checkable and **no proxy invented**. REVIEWED-133 (PENDING-137) ruled + executed — **two of its conditions corrected by executor substrate reads**, and ⚠ `governance-mcp.py --selftest` was **FAILING while the jurist ruled from it** (fixed, 62 controls). **NEXT: the fr cell's last two steps.**
+- [Session 2026-09-03 — the index had become the record](session-2026-09-03-the-index-had-become-the-record.md) — the load-integrity breach diagnosed rather than pruned; three sole-custodian workstreams relocated; Tarbuckle tracker established; the digest selftest found permanently failing on a mumble-only sample. **NEXT: the fr cell's last two steps** — unchanged.
 
 ## 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).