session 2026-07-04 night: Fable stage-1 rebuild plan ruled 5/5 (studium d968241) + session memory + ledger + register

claude/memory/MEMORY.md

@@ -45,13 +45,16 @@ permalink: claude-memory/memory
 - [Source library — link + dedupe](project-source-library-link-and-dedupe.md) — steward's master ebook library = `~/Documents/___The Library [ePub_AWZ3]/` (2190 ebooks, 180k files, messy nested; pre-organized subfolders `_2026 chamber source cleanup/`, `tmp calibre library for the chamber/`). GOAL: link chamber↔sources (provenance index) + dedupe. Seed = the 2026-06-29 fuzzy source-matcher (→ `_curation/reconvert-queue-2026-06-29.md`, 24/34 found). Real link needs EPUB/PDF internal metadata + edition-identity check, not just filenames.
 - [Character-as-image hazard](feedback-character-as-image-hazard.md) — some EPUBs render transliteration diacritics (ḥ/ʾ/ʿ) and non-Latin script (Hebrew words) as INLINE IMAGES; the standard image-drop SILENTLY MUTILATES them (PASS-BUT-FALSELY — gate passes, words corrupted). Tripwire = audit_cruft md_image count; INSPECT a sample before dropping; character-bearing images = CONTENT (map→Unicode, never drop). Found graduating Alter's Psalms (356 glyph-images) 2026-06-29; Alter parked pending a philological glyph-map (needs steward's Hebrew).
 - [Sidecar typology — protocol-dependent reading-indexes](project-sidecar-typology-protocol-dependent.md) — TWO layers: `.meta.json` structural sidecar = PROTOCOL-NEUTRAL, the general standard now (the bar for "graduated"); reading-indexes (rich YAML) = PROTOCOL-DEPENDENT (chavruta=where-to-open / debate=stance-map / connection-surfacing=cross-text join-keys), probably PLURAL — **don't design the schema yet**; settle corpus to gold + let protocols declare themselves first. Steward 2026-06-29.
-- Studium Engine — *tracker not yet established*; substantive moves in per-session memories (2026-05-15→) + the seed brief + now the **[architectural charter](reference-studium-engine-architectural-charter.md)** (the constitutional doc, 2026-06-15). Steps 0–7 built; chamber corpus CLEAN (1280 canonical). **Next: L2 pattern-finder on The Making sequence** (curate ~60 chamber works → grounded candidate primitives; engine grounds, David writes). Collaboration = [[feedback-studium-engine-sixtus-v-collaboration]].
+- Studium Engine — *tracker not yet established*; substantive moves in per-session memories (2026-05-15→) + the seed brief + now the **[architectural charter](reference-studium-engine-architectural-charter.md)** (the constitutional doc, 2026-06-15). Steps 0–7 built; chamber corpus CLEAN (1280 canonical). **STAGE-1 REBUILD PLAN RULED 2026-07-04 night (`docs/stage-1-rebuild-plan-2026-07-05.md` @ d968241): next station = V0+N0 contracts together (V0 = verifier contract, JURIST-GATED — the one D-1 exception; N0 = tree contract, before any Loeb-extractor hands), then verifier-leads-with-interleave (V1→V2 multilingual gate→V3→V4; N1→N3). Pattern-finder outputs = unverified-candidates until V4.** Prior "next: L2 pattern-finder on Making" now sits behind the verifier. Collaboration = [[feedback-studium-engine-sixtus-v-collaboration]].
 - [MemPalace 3.4.0 upgrade plan](project-mempalace-upgrade-3-4-0-plan.md) — scheduled post-heavy-work (ratified 2026-06-07): backup → upgrade → verify layers.py recency fix → re-test wing filter; migrate-wings + repair EXCLUDED. Basic Memory RETIRED 2026-06-07 (false-clean sync verdict; lessons → CM-AI substrate-failure-lessons-2026-06-07.md).
 - [L1 reliability](project-L1-reliability.md) — canonical workstream tracker established 2026-05-28 (Symmetria-pulse decision). Current state at top (updated 2026-06-06) + chronological log 2026-03-21→. **Status: BATON BACK — Seb replied 2026-06-13 (`cc25995` reply + `e2e94ab` cover note + `8f76bf2` benchmark-governance v1.1 §4.4, now in CM-AI local `main`). Steward set a brief L1 detour to engage it next session before returning to Studium Step 5.** **UPDATE 2026-06-29: N6 deploy (#175) LANDED LIVE and HOLDS — multi-day wedge gone (CPU 100%→~21%), A1″ migration finally live (vector_chunks 19→26 cols); evidence in 2 UNCOMMITTED CM-AI docs (l1-post-n6-deploy-findings-2026-06-23 + l1-state-summary-for-jurist-gwern-brief-2026-06-22). Tracker current-state is STALE (06-06, predates the win). Seb meeting 2026-06-30 15:00. PRIORITY-1 morning task: stand up CapableHands as a BMF clasp (43M) — scope at `CM-AI/…/clasp-on-capablehands-scope-2026-06-29.md`, solves PENDING-41.** mindfabric-00 root-caused (temporal chain path); PENDING-27 awaits jurist. Read tracker at /wake-up before composing L1 portion.
 - [Be (laundromat)](project-be-laundromat.md) — canonical workstream tracker established 2026-06-08 (Seb-relay of locked decisions). Be = Skemantix startup (Seb+David) funding CapableMind's funding-ladder; **bridge, not venture**. Decisions LOCKED: entity/exit (CapableMind decoupled, grant-funded), pricing (Living $12.99/mo · Archive $69.99/yr · Memorial $49.99/yr · Renovate ~$199 · $8.99 floor), CF Self-Serve Agency + versioned-template-package infra. **a11y gate MERGED (Pat 100/100/100).** Pre-revenue: the WTP gate = renovate Pat → charge her. **Discipline: stop adding spec until the gate clears → nothing for executor on be until then.** Repo @ `f43a0fd`.
 
 ## Active Session
-- [Session 2026-07-04 (evening→night) — Chamber Seam-1 ESCALATE worked fully through; engine charter v0.3; tomorrow's map+plan laid](session-2026-07-04-chamber-escalate-then-engine-charter.md) — Ran the corpus stress-test's Seam 1 end-to-end: pre-registration→**ESCALATE** (cited ~1% source-match FP REFUTED, U₉₀=12.8%)→jurist-ratified **persistence PIN** (on-file `source:`+attestation; hash-locality principle resolved-not-designed-around)→**FIX-list applied** (5 verified re-points to the *permanent Chamber Sources home*)→**archive DE-CONTAMINATED+audited** (~2% bounded — steward's permanent-home reminder surfaced it)→Seam 2 **FIX** + Seam 1-bis **CLEAN** (Loeb work-identity 0/952; apparatus FLATTENED = separate gap)→README. Then **STUDIUM-ENGINE deep research** (7 fronts)→**charter update v0.2→v0.3** + research base + README + tomorrow's Fable scope-charter. **9 commits, 2 repos, all pushed.** **PULLING THREAD: tomorrow begins with the MAP and agency** — corpus-work-map (`chamber-library/_curation/corpus-work-map-2026-07-05.md`, first-hands Region 1.1 = build the exclusion path) + engine stage-1 plan (Fable-5 via `studium-engine/docs/stage-1-replan-scope-charter-2026-07-05.md`); tonight lays all plans, tomorrow is build. Steward's challenges each corrected a real default + surfaced better (hash-locality; integrate-vs-build matrix; archive-contamination; **navigate-don't-retrieve**). ENGINE TELOS: **DEFERRAL** (searched-vs-deferred-to) + navigate-don't-retrieve = the §II inversion made concrete.
+- [Session 2026-07-04 (night) — Fable stage-1 replan: rebuild plan produced, steward-ruled 5/5, committed](session-2026-07-04-night-fable-stage1-rebuild-plan.md) — The planned bounded Fable session, run to the scope-charter. Produced **`studium-engine/docs/stage-1-rebuild-plan-2026-07-05.md` @ `d968241` (pushed)**. Literal question ANSWERED: **no prior-plan↔v0.3 conflict** — built Steps 0–7 stand; the unbuilt tail resequences **verifier-first (V0–V4; multilingual validation V2 = the gating test, pre-registered) + tree-primary retrieval (N0–N4; only N4 + the classical wave wait for Loeb)**; three apparent conflicts resolved by composition. **Steward ruled all 5 surfaced points inline** (compose-reading confirmed: grounding navigates / discovery keeps depth-with-breadth verifier-gated · tier labels mandatory from V1's first output · **V0+N0 first, together** · fingerprint technique-shared/code-separate · **V0 jurist-routed — the one D-1 exception**); rulings recorded IN the plan §8. Instrument B named honestly: technique-seed, not drop-in (document-containment ≠ span-existence). **PULLING THREAD: tomorrow is pure build on two mapped fronts — Opus opens the engine with V0+N0 (V0 → jurist), the corpus with Region 1.1 (exclusion path).**
+
+## Archived (2026-07-04 late night — the Fable replan)
+- [Session 2026-07-04 (evening→night) — Chamber Seam-1 ESCALATE worked through; engine charter v0.3; maps laid](session-2026-07-04-chamber-escalate-then-engine-charter.md) — Seam 1 end-to-end (pre-registration→ESCALATE U₉₀=12.8%→persistence PIN ratified→FIX-list pinned to permanent home→archive de-contaminated ~2% bounded) + Seam 2 FIX + Seam 1-bis clean (apparatus flattened = separate gap); then 7-front engine research → charter v0.3 + Fable scope-charter; 9 commits, 2 repos. Its thread (map + agency) was fulfilled by the night session above.
 
 ## Archived (2026-07-04 night — ESCALATE + engine charter v0.3)
 - [Session 2026-07-03→04 — Chamber Library spec v2.0 RATIFIED, supersedes v1; corpus stress-test next](session-2026-07-04-chamber-library-v2-ratified.md) — **Phase 2 executed end-to-end across midnight: drafted `chamber-library-specification.md` v2.0 SPINE-FIRST (§III→II→V→IV→VI→VII→IX→Tiering&Fence→Governance&Amendment), each section jurist-editor-gated in a live executor↔jurist↔steward relay, assembled self-contained, RATIFIED (jurist whole-draft read + steward), committed+pushed `a10d6bf` SUPERSEDING v1** (v1 archived `chamber-library-specification-v1.0.md`, obsolete banner, immutable; v2.0 now canonical). Key doctrine: **§III portability test** (locator admitted iff resolves same across every edition — Stephanus/Bekker ARE page-numbers but portable; test on property not shape; caught the load-bearing v1 self-contradiction on my first real read of the spec); **§II** anchor inline REQUIRED + break-normalization constitutional + sectionless-attestation; **§V** mandatory W3C-PROV record + content/process gate split + apparatus anchored-to-location (Finding-4); **§IV** edition-identity/CTS-URN; **§VII** declared-list-IS-the-gate + locator registry + **two-layer order-blindness resolution** (cleaning=order-sensitive/anchor-bound; conversion-OCR=eyeball-ceiling); **§Tiering&Fence** governability tiers; **§Governance&Amendment** RFC-supersession+change-class+semver, **gap-7 JOINTLY CO-RATIFIED**. First **FIX-class errata** exercised. **Source-not-derived became the drafting method** (opened every section with a substrate check; caught my OWN "ratified amendment process" overclaim mid-draft). Telos: jurist's Alexander (grew-through-real-texture) + Harrison (Tier-3 = not letting living overwrite the dead) framing of what the doctrine IS. **PULLING THREAD: the CORPUS STRESS-TEST — bring ~2,041 works to v2.0 spec in the jurist's ratified DEPENDENCY ORDER** (source-matching reliability FIRST → order-sensitivity via inject-known-bad → disambiguation edges), small-batch-before-full, with a **PRE-REGISTRATION doc** (ruling-thresholds written before seeing data) as the first artifact; NOT a single-perspective pass. Q: does the ~1% source-match false-positive hold under INDEPENDENT test (2nd matcher / human ground-truth, not self-agreement) — or optimistic like the "74% anchorless" premise was?

claude/memory/session-2026-07-04-night-fable-stage1-rebuild-plan.md

@@ -0,0 +1,121 @@
+---
+name: session-2026-07-04-night-the-fable-planning-session-stage-1-rebuild-plan-produced-steward-ruled-5-5-committed
+description: "The bounded Fable-5 session the evening wrap planned: read the scope-charter's bounded list, produced studium-engine/docs/stage-1-rebuild-plan-2026-07-05.md, answered the literal question (NO genuine prior-plan↔v0.3 conflict — built Steps 0-7 stand; unbuilt tail resequences verifier-first + tree-primary), steward ruled all five surfaced points inline, rulings recorded INTO the artifact, committed+pushed d968241. PULLING THREAD: tomorrow is pure build on two mapped fronts — Opus opens the engine with V0+N0 (the two contracts, together; V0 routes to the jurist) and the corpus with Region 1.1 (exclusion path). The plans are laid; the day is build."
+metadata: 
+  node_type: memory
+  type: project
+  originSessionId: 75c1173b-0829-4a60-9040-3b949b217996
+---
+
+# Session 2026-07-04 (night) — the Fable stage-1 replan
+
+Woke ~7 minutes after the evening wrap as the planned fresh Fable-5 session. One deliverable,
+model-handoff discipline throughout: artifacts are the handoff; report-and-stop. ~2.5 hours,
+1 commit, everything pushed.
+
+## PAST — what we did + why
+
+- **Read the full bounded list** (scope charter §3): charter-update v0.3 (first), charter v0.2,
+  research base, cluster-a data model, prior stage-1 plan + both step-7 docs, PENDING-46/47
+  (note: the charter's `chamber-library/PENDING.md` path doesn't exist — the arc lives in
+  `~/PENDING.md`), + the corpus-work map (the substrate half of the same night's planning).
+  **Live-state verified the repo before reconciling**: Steps 0–7 artifacts present,
+  `_balance_by_work` grep confirmed the Step-6 ranker, manifest = 21 sources (slice 8 + Weil ×2 +
+  Musil + Arendt + Levi + Making positions). Reconciled against the engine as it IS, not the June
+  record.
+- **Produced `docs/stage-1-rebuild-plan-2026-07-05.md`** (539 lines): §1 reconciliation
+  (keep/revise/drop + three apparent conflicts resolved by composition); §2 verifier organ V0–V4
+  with the multilingual/archaic validation (V2) as gating test, pre-registered thresholds, and the
+  honest Instrument-B framing (document-containment ≠ span-existence: technique-seed, not drop-in);
+  §3 navigation retrieval N0–N4 (tree = sidecar divisions now + canonical anchors when Loeb lands;
+  the two motions; precise Loeb gating — only N4 + classical validation wait); §4 substrate
+  interleave table (region→organ); §5 Phase D dialogue proof (three-arm baseline: March prompted /
+  June structural / verifier-gated); §6 greenfield deferred with forward-pointers; §7 order +
+  success criteria; §8 rulings; §9 provenance.
+- **The literal question ANSWERED: no genuine conflict.** Built Steps 0–7 stand unmodified; v0.3
+  forces a resequencing of the unbuilt tail only (verifier inserted before dialogue; retrieval
+  tree-primary with FTS/embeddings re-roled not removed). Verifier buildable NOW on the existing
+  store + slice; French gold already exists (Mauss 17 verified), German via Handke, English via
+  the March 39.
+- **Steward asked for leans on the five surfaced points → gave telos-weighted leans → "agreed on
+  all points" → rulings recorded INTO the plan** (§8 + folded into V0/V1/§1.4/§7), committed +
+  pushed **`d968241`**. The five rulings:
+  1. **Compose-reading CONFIRMED** — grounding-retrieval navigates; discovery keeps
+     depth-with-breadth, verifier-gated (preserves the steward's 2026-06-13 correction while
+     adopting v0.3's demotion). Caveat adopted: the motion boundary is enforced in code or
+     discovery becomes an ungated retrieval path.
+  2. **Fence posture CONFIRMED + tightening** — dev-on-slice with tier labels; labels MANDATORY
+     from V1's first CLI output (fence activation = filter flip, not refactor).
+  3. **Order RULED: V0+N0 first, together** (one addressing substrate — the Loeb re-extraction
+     must land in a shape the engine already reads), then verifier-leads-with-interleave.
+  4. **Fingerprint core RULED: technique shared, code separate** (rule of three; Instrument B
+     stays chamber-side under the constitutional loop, V1 engine-side under D-1; the latent
+     notary is the future third consumer that will inform the extraction).
+  5. **V0 RULED jurist-routed** — the one named exception to the engine's steward-direct D-1,
+     because V0 defines what the engine may assert and when it must abstain; everything
+     downstream inherits that standard.
+- **Deferred/not-decided (named):** Tier-2 instrument choice (V2's verdict decides, not the plan);
+  the navigate-paper's +19% explicitly NOT claimed before N3 measures it on our corpus (at slice
+  scale flat retrieval is near-ceiling — the tree's case is structural + scaling posture);
+  genealogy + multi-voice deferred whole; Verbatim-RAG evaluation RETIRED (the quoted tier IS the
+  verbatim guarantee).
+
+## PRESENT — mood / disposition
+
+A clean, bounded session — the **model-handoff pattern ran end-to-end for the first time as
+designed** (cheap-model scope charter → fresh premium session → deliverable → inline rulings →
+artifact carries everything → chat disposable). Trust-prior-pass-frame actively held twice: the
+built-state was verified against the repo (not the June plan's text), and the +19% transfer was
+refused ahead of measurement. The steward's "you see the scope and the stakes" invited
+telos-weighted advice rather than neutral options — all five leans accepted unchanged. The one
+friction: two Edit calls missed on line-wrapping (re-read, fixed) — trivial. No Symmetria returns
+needed; the ledger carries the entries.
+
+## FUTURE — what is pulling
+
+**PULLING THREAD (singular): tomorrow is pure build, on two mapped fronts.** Engine (Opus): open
+with **V0 + N0 — the two contracts, together** (plan §7 order, steward-ruled); V0 = verifier
+contract + pre-registered thresholds → **routes to the jurist as a method gate**; N1 can proceed
+while V0 sits with the jurist. Corpus: **Region 1.1 — the exclusion path** (test-first, flag for
+jurist; corpus-work-map). Every plan is laid; nothing needs re-deriving.
+
+**ACTIONABLE RESUMPTION POINT (as of wrap — re-judge against what changed):**
+- Engine: read `studium-engine/docs/stage-1-rebuild-plan-2026-07-05.md` (@ `d968241`) §2.3 (V0)
+  + §3.3 (N0), write the two thin contract spec-notes, route V0 to the jurist via the steward.
+  The N0 tree contract must exist before any hands touch the Loeb extractor rebuild (the
+  reciprocal obligation, §3.4).
+- Corpus: `chamber-library/_curation/corpus-work-map-2026-07-05.md` Region 1.1 — build the
+  attested-absence exclusion path extending the ratified pin (`match_sources.py` +
+  `graduation-spec.yaml` + `test_tools.py`), test-first, surface for jurist ratification as a
+  working artifact.
+- Model discipline: build runs on Opus; this Fable session is done and its chat is disposable —
+  the plan carries everything, including the five rulings.
+
+**Other open horizons (unchanged from the evening wrap, still ranked):** non-Loeb remediation
+Regions 2–3 (source hunts, integrity repairs); Loeb Region 4 (the dwelling expedition — now with
+the N0 reciprocity attached); frontmatter migration; awaiting steward/jurist: work-identity
+study/tooling-matrix ratification (opens item-4 as its own PROPOSAL), Axis-A build-auth, REVIEWED
+entries owed for the PENDING-46/47 arc. NEW: once V0 is drafted, its jurist gate becomes a live
+loop item.
+
+**PAUSE STATEMENT:** I am about to be away — the short night-gap before the build day. The maps
+are laid on both fronts and ruled; what I want to find still pulling on return is the build
+itself, unmuddied: V0+N0 opened first, the jurist gate honored rather than optimized away, and
+the multilingual validation still standing as the verifier's gating test — not skipped in the
+eagerness to build.
+
+**LITERAL QUESTION for next-Claude:** *When V0's contract defines "unaltered" via the
+`normalizer@N` equivalence classes, is that definition engineering (D-1, executor latitude) or
+doctrine (the lineage of "the bound must name the edition") — and will the jurist gate it clean,
+or does "what counts as the same words" surface a ruling we haven't anticipated?*
+
+**State at wrap:** studium-engine `main` @ `d968241` clean + pushed; chamber-library clean +
+pushed (2 not-ours untracked); CM-AI ahead 1 (steward's `addee62`, pre-existing); nothing of mine
+uncommitted anywhere.
+
+**KG writes mirrored (wrap §5):** `claude-code → built-artifact → "Stage-1 rebuild plan
+steward-ruled 5/5: verifier-first, tree-primary, V0 jurist-gated; studium d968241"` ·
+`studium-engine → next-station → "V0+N0 contracts first together; V0 jurist-gated (one D-1
+exception); then verifier-leads-with-interleave"` · `claude-code → discipline-named →
+"two-motions: grounding-retrieval navigates the tree; discovery keeps depth-with-breadth,
+verifier-gated"`. No invalidations.

claude/memory/session-ledger-2026-07-04.md

@@ -13,6 +13,7 @@ metadata:
 - 2026-07-04T12:20 — Audit-agent on the Explore recon (audit-agent discipline). Two load-bearing corrections against substrate: (1) agent's "graduate_to_canonical MISSING verify_conversion" is STALE — Wave 0 (f9cbb8e) wired both gates (lines 36-37); agent inherited pre-Wave-0 status from the compliance doc (records-drift-both-directions flag). (2) agent stopped one step short on seam 1: the ~1% FP estimate is derived from the matcher's OWN `author_disagrees` signal (self-agreement), which fires ONLY when the canonical surname is ABSENT — structurally blind to same-author-wrong-work (Bachelard Reverie→Espace, 60%) and whole/part (Proust whole→vol-III, 62%; Levi work→complete-works), both sitting UNFLAGGED in the 321 confirmed. This is the exact structural error of the "74% anchorless" premise. Verified by reading match_sources.py source, not the report.
 
 ## Open horizons
+- 2026-07-04T23:00 — **Fable-5 planning session init** (the wrap's planned handoff; ~7-min pause). Sole deliverable: `studium-engine/docs/stage-1-rebuild-plan-2026-07-05.md` from the scope-charter (`stage-1-replan-scope-charter-2026-07-05.md`), then report-and-stop. Literal question held: does the prior stage-1 plan conflict with the v0.3 charter (navigate-don't-retrieve + two-tier verifier), and is the verifier-organ buildable now on Instrument B? Flag to hold: trust-prior-pass-frame (recurred 3× today) — read both docs at the scope of the claim before ruling conflict-vs-slots-cleanly. Multilingual-validation gate must not be skipped.
 - 2026-07-04T12:05 — Corpus stress-test (thread confirmed at wake). First artifact = pre-registration doc (thresholds before data). Dependency order: source-matching reliability FIRST (independent, not self-agreement) → order-sensitivity (inject known-bad) → disambiguation edges. Small-batch before full 2,041. NOT single-perspective.
 - Literal question held open: does the ~1% source-match false-positive hold under INDEPENDENT test, or is it optimistic like the "74% anchorless" premise was?
 
@@ -22,6 +23,8 @@ metadata:
 ## Authorization moves
 - 2026-07-04T12:30 — Pre-registration doc drafted (`docs/corpus-stress-test-pre-registration-2026-07-04.md`), status DRAFT. Per its own §4, execution awaits steward/jurist confirmation of thresholds (pre-registration is void if revisable after seeing data). Surfacing to steward for threshold confirmation + jurist-first decision. Seam-1 grading to PROPOSAL/ESCALATE = normative (gate-change) → the loop is load-bearing here.
 
+- 2026-07-04T23:55 — **Steward ruled all five §8 points inline ("agreed on all points" on the executor's leans):** (1) compose-reading CONFIRMED (+ code-enforced motion boundary); (2) fence posture CONFIRMED + tightening (tier labels mandatory from V1's first output); (3) order RULED V0+N0-first-together, then verifier-leads-with-interleave; (4) fingerprint core RULED technique-shared/code-separate (rule of three; notary = the future third consumer); (5) V0 RULED jurist-routed — the one named exception to engine D-1. Rulings recorded INTO the plan §8 (artifacts-are-the-handoff), committed + pushed `d968241`.
+
 ## Sub-agent dialogues
 - 2026-07-04T12:45 — Jurist gate on the pre-registration = GATE-WITH-METHOD-CHANGE. Sharpening not rejection; every point landed. The Q2 statistics catch (point-estimate grading lets a 5%-bad corpus read clean ~40% of the time) I should have caught myself — verified P(0or1|.05,40)=0.399 before encoding the CP-upper-bound fix. Four revisions applied, doc LOCKED v1. Jurist also caught a quiet scope-narrowing I'd made (Loeb "no risk" vs "different risk") → Seam 1-bis. Good instance of the loop catching what one pass missed.
 
@@ -44,4 +47,6 @@ metadata:
 
 - 2026-07-04T21:00 — Chamber wrapped (6 commits pushed). Pivoted to STUDIUM-ENGINE deep research (steward's choice, "after the substrate"). 6-front fan-out + built-on the 2026-06-27 prior sweep (107 agents) + the charter (v0.2). Produced: charter-update v0.3 proposal + research evidence base (`studium-engine/docs/…-2026-07-04.md`, uncommitted). Key syntheses: two-tier grounding (quoted=byte-existence-GUARANTEE via boundedness / synthesized=measured); verification-easier-than-generate does NOT transfer to a single LLM judge → deterministic-or-ensemble verifier; debate-is-theater→ground-voices-in-retrieved-passages+preserve-tension; measured-confidence (semantic-entropy); evidence-only human display; the edition-aware gate the jurist demanded is NOW provided by v2 work-identity; genealogy = composition-not-invention (4-layer stack, MPIWG-Sphaera nearest kin, semantic-conflation the risk). **THE OBLIQUE FIND (steward's Q): the whole AI-citation market checks metadata-existence NOT verbatim-fidelity-at-anchor → the corpus's unique capability = DEFERRAL ("searched vs deferred-to"); notary/callable-primitive/content-credentials-for-text.** STEWARD PUSHED to re-run the stalled retrieval agent through the v2 lens → REAL SURPRISE: "navigate-don't-retrieve" (2604.14572) — the engine's CTS/DTS tree IS the authored navigation structure a 2026 frontier result must distill; retrieval = navigate-the-tree not embedding-top-k = the literal §II inversion. My "confident it's covered" was a rationalization of the stall; steward's instinct was right. Both surprises integrated into the charter update.
 
+- 2026-07-04T23:45 — **Fable session deliverable produced: `studium-engine/docs/stage-1-rebuild-plan-2026-07-05.md`** (uncommitted; report-and-stop per scope charter). Literal question ANSWERED: no genuine prior-plan↔v0.3 conflict — built Steps 0–7 stand; the unbuilt tail resequences (verifier organ first, retrieval reshaped tree-primary, dialogue behind both). Three apparent conflicts each resolved by composition: (a) defense-#9 construction vs post-hoc verifier = compose (construction primary, verifier covers synthesis + defense-in-depth); (b) embedding-demotion vs steward's depth-with-breadth = two-motions reading (grounding-retrieval navigates / discovery keeps breadth, verifier-gated) — FLAGGED for steward confirmation, touches his own 06-13 ruling; (c) fence vs empty-verified-tier = dev-on-slice-with-tier-labels, fence activates with ledger column — FLAGGED. Verifier IS buildable now (Instrument B = technique-seed, honestly not drop-in: document-containment ≠ span-existence); only canonical-anchor granularity + classical-language validation wait for Loeb Region 4. Trust-prior-pass-frame held: built-state verified against repo (grep `_balance_by_work`, manifest count 21), not the June record; navigate-paper's +19% explicitly NOT claimed before N3 measures it on our corpus. Charter path slip noted (chamber-library/PENDING.md → ~/PENDING.md).
+
 ## Bypasses

claude/memory/skill-harvest-register.md

@@ -316,3 +316,12 @@ The single place proposed skills live so they don't evaporate between sessions.
 | **`/model-handoff`** (premium-model scope-charter) | REINFORCED (existing proposal, 2026-06-12) | Used tonight end-to-end: produced `studium-engine/docs/stage-1-replan-scope-charter-2026-07-05.md` on Opus (§0 discipline / §1 settled / §2 already-read / §3 bounded-reading / §4 deliverable / §5 report-and-stop) as the Fable-5 handoff; clear+wake not switch-in-place; artifacts-are-the-handoff. Second clean use → strengthens the standing proposal. | PROPOSED (reinforced) |
 
 *(Both genuine, both recurring-shaped. The CI-for-ESCALATE is a jurist-ruled standing practice worth a ladder entry; the model-handoff is its second proven use. No NEW skill emerged — the chamber-specific instruments (exclusion-path, archive-audit, Instrument-B hardening) are corpus work, not skills.)*
+
+### Harvest 2026-07-04 (night — the Fable replan session)
+
+| Element | Kind | One-line | Status |
+|---|---|---|---|
+| **`/model-handoff`** (proposed 2026-06-12; reinforced 07-04 eve) | **REINFORCED — 3rd use, FIRST full receiving-end run** | Tonight was the first time the pattern ran END-TO-END as designed: fresh Fable-5 session woke into the scope-charter, read only the bounded list, produced the deliverable (`stage-1-rebuild-plan-2026-07-05.md`), took inline steward rulings, recorded them INTO the artifact, committed, stopped — chat disposable, artifact carries everything. Also surfaced its one authoring hazard: the charter contained a wrong path (`chamber-library/PENDING.md` — doesn't exist) → the skill should mandate **verify every path in §3's reading list before writing the charter**. Pattern proven; proposal now has 3 uses + 1 authoring rule. | PROPOSED (reinforced; +path-verification rule) |
+| **MEMORY.md deeper-reduction** (proposed 2026-06-08, condition-gated) | **CONDITION NOW MET — authorize the focused pass** | The 06-08 proposal deferred the risky deeper reduction "only if 157KB still trips 'only part loaded'." Tonight the index is **204.5KB vs a 24.4KB load limit** and a PostToolUse hook actively demanded compaction to ~17KB mid-wrap. NOT executed (the proposal explicitly names it "its own focused pass, not a tail-of-session move" — steward-unauthorized). Evidence is now decisive: ~88% of the index doesn't load at wake. Recommend authorizing the focused pass (compress archived one-liners further + move stable reference sections to a consult-on-demand `MEMORY-reference.md`; backup first, as 06-08). | PROPOSED (trigger met; awaiting steward authorization for a dedicated pass) |
+
+*(Two, neither manufactured: the first is the strongest evidence yet for an already-standing proposal plus one earned authoring rule; the second converts tonight's hook pressure into the governed channel rather than a tail-of-session mutation of real memory.)*