memory: trim MEMORY.md 20504->17250 (slim not delete); tomorrow = CM/BMF -> library transfer

Index was re-bloating to its pre-compaction size — the exact class the two-file
split exists to prevent. Slimmed 6 over-budget tracker entries and 12 standing
preferences to their operative rule, relocating provenance narrative to the
linked files where it already lives. 49 bullets before and after, 5 sections
before and after, 49/49 pointers resolve.

Session record gains tomorrow's steward-set agenda: what transfers from
CapableMind/BMF to the library/engine — led by running census 01 against the
chamber/engine tooling it explicitly declared out of scope.

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

claude/memory/session-2026-08-03-the-governors-that-never-engaged.md

@@ -67,6 +67,14 @@ Climbing toward ~19,925 is the whole story. **If it is stopped:** the launchd jo
 
 **LITERAL QUESTION for next-Claude:** Five subsystems today held a control that exists and never engages. `ANALYZE` was one, and one command fixed it. **When the replay finishes, will `coherence_evaluated` be greater than zero — or is the coherence evaluator one more governor that exists and never runs?** It is checkable in a single query, and the answer decides whether the chain layer has any pruning at all or has been accumulating unvalidated path materialisations since April by design.
 
+**TOMORROW'S NAMED WORK (steward-set at the wrap): what transfers from CapableMind/BMF to the library/engine.** The replay will still be running; it does not need watching. The steward's framing — *"the library/engine work is genuinely important because experience and knowledge transfer in both directions"* — and today produced the richest transfer material yet, all of it in the **CM → library** direction that the parallel-tracks doc (Part IV) only sketched.
+
+- **1. Run census 01 against chamber/engine tooling — this is the census's own declared scope gap.** `census-01-…-RESULT.md` names what it did NOT cover: `verify-before-compose`, `audit_cruft`, `verify_conversion`, `resolve_archived_source`, `apply_char_glyphs`, studium `verify-quote` / `fidelity_equivalence@2`. Today found **five governors that exist and never engage** in the CM/governance half. The library half is uncensused, and the same question applies verbatim: *does each gate have a real negative instance, and is its absence recorded or does it look like coverage?*
+- **2. The `ANALYZE` class, generalized: does any engine instrument's cost grow with corpus size?** L1's ingest was **divergent, not slow** — cost per event grew with the corpus, so no hardware would ever finish it. Ask it of the engine: does any operation scan the whole corpus per item? A tool that is fine at 1,245 documents and quadratic is indistinguishable from a fast one until it isn't.
+- **3. Data-not-code, applied to the chamber.** L1's defect turned out to be artifacts minted **before the governors landed**, which the governors cannot retroactively fix. The chamber accumulates the same way: **is there graduated content that predates the current constitution/runbook and would fail today's gates?** If so, the analogue of `cm-ctl repair` is a re-graduation pass — and the chamber's `resolve_archived_source` pinning is what would make it replayable.
+- **4. Method transfer: profile the running thing, don't reason from the spec.** An afternoon of spec-reading produced a clasp that could not have helped; `sample` → CDP inspector → `EXPLAIN QUERY PLAN` found the real cause in under an hour.
+- **5. Still open from Part IV, and now better motivated: facets as the formalism for Chamber V1.** A Chamber release *is* a facet over an unversioned corpus; fork/replay/diff/promote dissolve the stuck "which purpose anchors V1" decision. Today's L1 replay is a live demonstration that replay-from-immutable-origin actually works, which is the same move.
+
 **Other horizons, ranked.**
 - **Load-bearing, Seb's call:** `getChainsContainingSeq` is a `json_each` membership scan over every chain (**4.0 s/call** at 813k) — unindexable as written; needs `event_seqs` normalised. The rebuild buys headroom, not immunity; the complexity class is unchanged.
 - **Load-bearing, ours:** `governance-drift-check.py` 3-of-5 inert — owed to PENDING as `[HARDENING]`, not yet filed. The ladder's unrecordable firing history is the same shape one level up.