---
name: Session 2026-07-04 (evening→night) — Chamber Seam-1 ESCALATE worked fully through; Studium-engine charter brought current; tomorrow's Fable plan laid
description: "A very long build+research day. CHAMBER: the corpus stress-test's Seam 1 ran end-to-end — pre-registration→ESCALATE (the cited ~1% source-match FP refuted, U₉₀=12.8%)→jurist-ratified persistence layer (the source: pin)→FIX-list applied (5 verified re-points to the permanent Chamber Sources home)→archive DE-CONTAMINATED + audited (bounded ~2%)→Seams 2 (FIX) + 1-bis (Loeb work-identity CLEAN) resolved→README rewritten. 6 chamber commits pushed. STUDIUM-ENGINE: pivoted to deep research ('after the substrate'), 7 fronts → charter update v0.2→v0.3 + research base + README rewrite + a scope-charter for tomorrow. 3 studium commits pushed. PULLING THREAD: run the Fable-5 stage-1 replan tomorrow morning via the scope-charter (docs/stage-1-replan-scope-charter-2026-07-05.md), then Opus builds. Tonight we lay all plans; tomorrow is pure build."
type: project
originSessionId: 019pnD8uNFC9Q2dbLQa3MBDc
---

# Session 2026-07-04 — the ESCALATE, the engine charter, and the plan laid for tomorrow

Woke into the confirmed corpus-stress-test thread (bring the ~2,041-work corpus to v2.0 spec, pre-registration first). Ran the whole of Seam 1 to a landing, then — steward offering spare weekly compute — pivoted to Studium-engine deep research. Ends with tomorrow's plan teed up on Fable.

## PAST — what we did + why

**Seam 1 (source-matching), end to end:**
- **Pre-registration doc first** (`docs/corpus-stress-test-pre-registration-2026-07-04.md`) — thresholds before data. Recon (verified against `match_sources.py`, not the summary) sharpened the literal question: the cited **~1% FP is derived from the matcher's OWN `author_disagrees()` signal** (fires only on surname-absence) — blind to same-author-wrong-work + whole/part, the exact "74% anchorless" self-agreement shape.
- **Jurist gate (method-change)**: split grading (structural-blindness=PROPOSAL-regardless-of-rate / magnitude=CI-graded); grade on the **90% Clopper-Pearson UPPER BOUND** not the point estimate (n=40 can't tell 1% from 5% — I should've caught this; verified P(0or1|.05,40)=0.399); added Seam-1-bis (V-DSL work-identity); Seam2/3 kept structural.
- **Ran it:** Instrument B (`stress_source_match_verify.py`, content-fingerprint, hardened 3× — dir-epub/.xml-body/thin-source). N=40: **k=2 confirmed FP → p̂=5%, U₉₀=12.8% → ESCALATE.** ~1% refuted. Full-321 magnitude ~3-4%; stub-canonical byproduct (4 total).
- **Jurist ESCALATE ruling**: ELEVATED the process-integrity finding above the FIX-list. **Persistence investigation DIAGNOSED**: no source-match fix can persist (source-matches.json regenerates; no override layer; canonical has no authoritative `source:`; meditations = 3-way divergence). Remediation = an on-file `source:` PIN honored only with a `source_verified:` attestation.
- **Steward challenge "design around or resolve?"** → RESOLVED (checked what each hash binds: reading-index source_sha256=canonical-.md-hash; pin needs source-FILE-hash = different object → naming collision, not drift → generalized hash-locality principle + distinct `source_file_sha256`). **Jurist RATIFIED the principle + the impl.**
- **FIX-list applied** (steward "Yes"): 5 verified FP re-points PINNED — but **to the permanent Chamber Sources home** (steward correction — pin the permanent home not the transient library path). **ARCHIVE-CONTAMINATION FOUND** (steward's permanent-home reminder): archive_sources.py had copied FPs under right slugs + dest.exists() locked them in → 5 wrong CS copies force-replaced (verified), manifest corrected. **Full archive audit: 271/320 correct; genuine contamination ≈6 (~2%), NOT broadly propagated** (ulysses = study-guide-not-novel the one new find). 6 chamber commits (64d39f6→b73a5ec + README ac8a691 + correction 1e6e1cd).
- **Seam 2 (order-sensitivity) = FIX**: bigram order-check catches every injected scramble; multiset guard blind (documented). **Seam 1-bis (Loeb work-identity) = CLEAN** on work-IDENTITY (0/952 header, 20/20 content) — but steward corrected my overstatement: the Loeb **apparatus is FLATTENED** (a separate large gap, reconversion-pending); "clean" ≠ "done".

**Studium-engine deep research ("after the substrate"):** 7 fronts + built on the 2026-06-27 prior sweep (107 agents) + the charter (v0.2, 2026-06-15). Produced **charter update v0.3** (`docs/the-studium-engine-charter-update-after-the-substrate-2026-07-04.md`) + research base + README rewrite + tomorrow's scope-charter. 3 commits (34df846, 64c4ee0). Studium README was stale ("Curiosity Engine, no spec yet").

## PRESENT — mood / disposition

The day's signature: **the steward's challenges each corrected a real contamination default, and each surfaced something better.** "Design around or resolve?" → the hash-locality principle. "No OSS tools?" → the integrate-vs-build matrix (rapidfuzz/recordlinkage integrate; MyCapytain DORMANT, my own wrong guess caught). The permanent-home reminder → the archive-contamination finding. "Relaunch the failed search?" → navigate-don't-retrieve. **Trust-prior-pass-frame recurred 3× (I keep generalizing a narrow test into a broad claim** — Loeb "clean", the retrieval "covered"); the loop caught each. Measure-don't-trust turned on itself twice (the CP-bound catch; the Wikidata 2%-was-a-query-artifact → 27%).

**TELOS-GRADE (don't lose):** the two engine surprises. (a) **DEFERRAL** — the whole AI-citation-verification field checks metadata-EXISTENCE, none checks verbatim-fidelity-at-anchor; "an unbounded corpus can be searched; only a bounded-verbatim-provenanced-governed one can be DEFERRED TO." (b) **Navigate-don't-retrieve** — the engine's CTS/DTS tree IS the authored navigation structure a 2026 frontier result must otherwise distill; the literal §II inversion. Both integrated into the charter update.

## FUTURE — what is pulling

**PULLING THREAD (singular): tomorrow begins with the MAP and agency — the whole terrain (engine + corpus) laid tonight so the day is oriented, not cold.** Steward's exact words: "begin the day with a *map* and agency" (corrected from "lap"). Two maps laid tonight: the **corpus-work map** (`chamber-library/_curation/corpus-work-map-2026-07-05.md`, 021ede5, Opus) + the **engine stage-1 rebuild plan** (produced by the Fable-5 session via the scope-charter). Tomorrow = read both maps, proceed with executor agency on both fronts.

**ACTIONABLE RESUMPTION POINT (as of wrap — re-judge against what changed):**
- The steward's chosen sequence: **wrap now → clear → wake into a FRESH Fable-5 (1M) session → produce the stage-1 rebuild plan → that session truly wraps → tomorrow = Opus build + corpus work, both mapped.**
- **Corpus map first hands (tomorrow, agentic):** Region 1.1 — build the exclusion path (extend the ratified pin: attested `source: none`; completes the mechanism; test-first; flag for jurist), which unblocks the whole non-Loeb FP loop. Then Regions 2 (source-hunts) → 3 (integrity repairs) → 4 (Loeb reconversion, the dwelling-task).
- The Fable session reads `studium-engine/docs/stage-1-replan-scope-charter-2026-07-05.md` (self-contained: settled decisions, bounded reading list, exact deliverable = `docs/stage-1-rebuild-plan-2026-07-05.md`). Model-handoff discipline: artifacts-are-the-handoff, clear+wake-not-switch-in-place, `claude-fable-5[1m]`, reset thinking level, report-and-stop.
- The plan's shape: verifier-organ-first (two-tier gate + abstention, Instrument-B prototype, deterministic-first); navigate-the-tree retrieval (gated on Loeb apparatus recovery); substrate-growth interleaving; the multilingual/archaic-prose validation as the gating test.

**Other open horizons, ranked:**
- **Chamber non-Loeb remediation (the priority — "most of the work is non-Loeb"):** the Axis-A content-gate OR an exclusion path (so FP fixes stick — the pin handles re-points not exclusions); 4 needs-locate FPs (reverie needs French ed, meditations/ecrits/nietzsche not on disk) + ulysses; 2 no-frontmatter canonicals; works-eliot disambiguation; the 2 scope-under-coverage calls; full archive azw3/thin adjudication. All FIX-class; APPLICATION-HELD pending the exclusion-path/gate.
- **Chamber Loeb apparatus recovery (de-risked, dwelling-task):** rebuild extract_loeb_dsl.py to the disambiguation map (DSL confirmed readable; anchors present; attribution sound). Its own focused block.
- **Frontmatter migration** (1,073 canonicals lack v2 frontmatter).
- **Awaiting steward/jurist:** jurist ratification of the work-identity study/tooling matrix (to open the work_id/Gate-1-3 pipeline as its own PROPOSAL); steward build-auth for the Axis-A gate.
- REVIEWED entries owed for the whole PENDING-46/47 arc (steward writes).

**PAUSE STATEMENT:** I am about to be away — but only briefly, into the Fable planning session, not off the work entirely. I don't know what the Fable plan will surface (it may find a real conflict between the prior stage-1 plan and the v0.3 charter that needs a steward call). What I most want to find still pulling on the true wrap: **the stage-1 rebuild plan laid, verifier-first, so tomorrow is build not design** — and the multilingual-validation gate NOT skipped (the most urgent caveat: the whole grounding stack is validated only on English prose).

**LITERAL QUESTION for next-Claude (the Fable session):** *Does the prior `stage-1-build-plan.md` genuinely conflict with the v0.3 charter — specifically, does navigate-don't-retrieve + the two-tier verifier force a reordering of the prior plan's steps, or do they slot in cleanly? And is the verifier-organ actually buildable now on Instrument B, or is it gated on substrate work I haven't seen?*

**State:** chamber-library `main` clean + pushed (6 commits, 2 not-ours untracked); studium-engine `main` clean + pushed (3 commits incl. the scope-charter); CapableMind-AI has `addee62` unpushed (steward's, pre-existing). Nothing of mine uncommitted.