dotfiles/claude/memory/session-2026-07-25-to-27-two-supersessions-and-the-sweep-that-caught-its-own-fix.md

---
name: session-2026-07-25-to-27-two-supersessions-voice-purity-bar-and-the-sweep-that-caught-its-own-fix
description: "Landed TWO ruled supersessions — v2.7.0 (REVIEWED-75, kind-scoping the verification criterion, both jurist corrections applied) and v2.8.0 (REVIEWED-73, voice-purity as the engine-consumable bar: verifier + declared data + backfill 18/1 + gate wired + single-reading-pass designed). The rule validated itself on first contact (3 unassigned tails + musil served with boundaries shifted by 6 lines, unknown to anyone) and corrected the ruling's own cited instance. Then the steward-directed base-rate sweep caught MY OWN source_lines fix one commit old — splitlines() also breaks on \\f/U+2028, 308 lines' disagreement on lintott. PULLING THREAD (unchanged, still untouched): which purpose anchors Chamber V1 — the steward's versioned-releases re-point, to which PENDING-75's kind-scoping is now the constitutional enabler."
metadata: 
  node_type: memory
  type: project
  modified: 2026-07-27T17:33:14.120Z
  originSessionId: 954fee42-68ff-46b5-95e6-238f33e6ca80
---

# Session 2026-07-25 → 07-27 — two supersessions, and the sweep that caught its own fix

Spans a power failure (07-25 morning → 07-27). Woke into the versioned-releases re-point; the steward relayed the PENDING-75 ruling and then said "build out all of the rulings." Ended with two constitutional supersessions landed, a gate wired, and a correction to work I had committed an hour earlier.

## PAST — what happened + why

**⚑ First move was a correction, and it was mine.** The wake briefing told the steward REVIEWED-72/73/74 were all AUTHORIZED-but-unbuilt and "the wave stays blocked until REVIEWED-72's demonstration." **Two of three were FALSE** — 72 and 74 were built and landed in v2.6.0 on 07-24; only 73 was genuinely unbuilt, and the wave was already unblocked. **Mechanism:** I read REVIEWED.md's *"If AUTHORIZED: build …"* lines — a record of what was **authorized**, not of what was **done** — and reported them as outstanding. *A ruling's disposition clause is a forward instruction, not a status.* Worst-placed possible error: a wake briefing, shaping the steward's picture of their own project before any work began.

**Spec v2.7.0 — REVIEWED-75, kind-scoping the verification criterion** (`e3b6aef`; ruling filed `docs/kind-scoping-verification-JURIST-RULING-2026-07-25.md`; REVIEWED-75 placed 07-27). The jurist adopted the package's Part-4 argument over his own: the foreclosure is not that a non-text work *fails* the criterion but that the criterion is **VACUOUS** on it (empty re-extraction is trivially prose-word-identical to its own empty extraction). Both required corrections applied against the LIVE wording as directed: (1) the **deterministic/scan split preserved** — V-SCAN has no ground-truth text and keeps its own more-expensive criterion; the draft would have flattened a distinction the ratified table draws, *inside the sentence meant to stop over-claiming*; (2) the **anti-bypass guard rebound to the property, not enrollment**. ⚑ I also caught a defect in the drafted Edit 2: *"ratified as above"* pointed the wrong way (§V precedes §Tiering & Fence) — landed as a named cross-ref.

**Spec v2.8.0 — REVIEWED-73, voice-purity as the engine-consumable bar** (`e596983` + `85c50a7`). Framed on the **orthogonality** the ruling required: the trim answers *"should this be preserved?"*, voice-purity answers *"whose words are these?"*; the Eichmann leak was **not a trim failure** — the trim *correctly kept* Elon's Introduction and the Bibliography. **Extending the trim is the wrong fix.** Built: `scripts/verify_voice_purity.py` (16 self-test invariants, negatives-first), `graduation-spec.yaml` `voice_purity:`, `scripts/migrate_voice_purity_sidecars.py`, `voice_purity_gate()` + `write_voice_purity()` wired into graduation, `docs/single-reading-pass-DESIGN-2026-07-27.md`. Fleet 248 → 288.

**⚑ The rule validated itself on first contact.** Applying exhaustive-partition to the existing engine corpus surfaced: **3 ARC sidecars with unassigned trailing lines** (ornament divs; assigned + flagged `_migration_assigned` for curator confirmation — the ROLE is a judgment neither gate nor script can make) and **`musil-mwq-tome-1`'s drifted binding** (5032→5038 lines) — *the engine had been serving Musil with boundaries shifted by 6: body truncated early, 6 lines mislabelled apparatus, 6 unassigned at the tail.* HELD for re-derivation, not migrated. Backfill: **18 migrated / 1 held**, verified at the real enforcement path.

**⚑ Corrected the ruling's own cited premise.** REVIEWED-73 cites the "5 standing FAILED ARC rows" as the live drift instance. **All five ARC bindings verify clean.** The one genuinely broken binding was Musil, a chamber canonical, unknown to anyone. The jurist's architectural argument for chamber-side is unaffected; the cited instance was wrong.

**Q2/Q4 reconciliation (steward-confirmed).** The two clauses meet at one point: **the gate fires at the graduation of a source the engine consumes**; everything else NOT-APPLICABLE. Wiring it to every candidate would have **silently blocked the Loeb wave with a bar that has no jurisdiction over it**. Found by asking where the clauses meet rather than implementing whichever was read last.

**The seam dissolved rather than got solved.** I had named "attestation binds the LANDED sha but the gate runs at graduation" as a blocking dependency. Reading the apply leg: graduation is a **pure move** (`git mv`/rename, no content transformation), so the candidate's bytes ARE the landed bytes. `write_voice_purity` re-stamps only `source_file`/`source_path` and **deliberately does not recompute sha/lines** — recomputing would let a content change re-bind quietly, inverting what the binding is for (steward-confirmed).

**`source_lines` — FIX, twice** (`4a1a731` then `b82fc48`). Steward ruled FIX + re-stamp-now + producer-then-consumers in one change-set, on the grounds that `count("\n")+1` names a coordinate the ratified frame says cannot exist (the de-glued-marker shape). ⚑ **Steward's "confirm the rule, not the sample" caught a live corruption risk:** the formulas agree iff the file does NOT end in a newline — **36/1,297 canonicals** — so a blanket `-= 1` would have corrupted exactly those; my 11-file sample (one producer, all newline-terminated) could not have shown it. Then the sweep caught the fix itself: **`len(splitlines())` also breaks on `\v \f \x1c \x1d \x1e \x85 U+2028 U+2029`** — 4 canonicals carry them, **lintott disagrees by 308 lines**, `wc -l` confirms newline-based. **Both prior formulas wrong on complementary subsets** → no single sample distinguishes all three. Root cause fixed: **ONE implementation** (`verify_voice_purity.count_lines`), producers import it.

**Base-rate sweep (steward-directed) — remaining sites checked.** `sha256`: one latent basis divergence (`read_text().encode()` vs `read_bytes()`, CRLF-only); 0/1,297 CRLF; `write_sidecar` still text-based → **named, not silently changed**. **Tokenizers AGREE** (`\w+` + `.lower()` across `verify_body_conservation`, `inject_epub_footnotes` ×3, `build_sidecar` ×2; the missing `re.UNICODE` is a py3 no-op). Empirical: Eichmann gate 122,715 vs raw 122,735 tokens, **identical 9,620 types** — the 20-token delta is exactly the footnote-marker digits `_tokens` strips by design. Consistent-by-design, fully accounted.

## PRESENT — the mood

Productive and repeatedly humbling, in the useful direction. The session's spine was **three corrections of my own claims**, each caught by a different mechanism: the substrate (the wake-briefing backlog error), the steward's instinct (the rule-vs-sample catch that prevented corrupting 36 files), and a sweep the steward directed (which landed on code I'd committed an hour before). The contamination directive ran healthy all session — the steward challenged framings and was right each time.

The sharpest lesson is uncomfortable and worth keeping uncomfortable: **ratifying a convention by comparing two existing implementations felt like derivation and was selection.** I verified that the two disagreed; I never verified that either was right. Confidence in "the engine-side convention is correct" was ~0.9 and should have been ≲0.5. The check that would have caught it cost one line (`\f` in a test string) and did not run until asked.

Also noted with satisfaction: the gate suite caught its own stale assertion on the first run after the correction (287/288 → the label fix). Negatives-first test design paid immediately.

## FUTURE — what is pulling

**PULLING THREAD (unchanged from the 07-25 re-point, and still untouched): *which purpose anchors Chamber V1, and what bounded voice-set + capability envelope does it need?*** ([[project-chamber-versioned-releases]]). Everything built this session is now an **input** to that scoping, not an open obligation. **PENDING-75's kind-scoping is the constitutional enabler under it** — an image-based work (Warburg, Jung) enters a later Chamber version as a new declared kind, additively, rather than forcing a re-founding of the load-bearing clause. That is a real structural unlock for the versioned-releases frame.

**ACTIONABLE RESUMPTION POINT (as of wrap — re-judge against what changed):** all four repos clean and synced; nothing half-finished. The first move is a **decision, not a build**: pose the V1-purpose question (Making Sequence / violin-XXI treatise / ARC) and let the answer bound which library work is V1-blocking vs V2-deferrable. If the steward wants executor work instead, the smallest well-defined bite is **`musil-mwq-tome-1`'s reading pass** (re-derive its boundaries; the engine is currently serving it 6 lines off) — bounded, concrete, and it closes a live defect.

**Other horizons, ranked:**
- **`musil-mwq-tome-1` re-derivation** — a live mis-attribution in the engine's served corpus. Small, bounded, real.
- **3 `_migration_assigned` ARC tails** — curator confirmation of the ROLE (ornament divs assigned `apparatus`).
- **The internal-nav curation ruling** (~31 wave files) — the *previous* pulling thread, now subordinate; matters for V1 only if V1's voices are nav-heavy books.
- **`write_sidecar`'s sha basis** (text vs bytes) — latent, 0 live instances (no CRLF canonicals), named for its own small FIX cycle.
- Sidecar **relocation** chamber-side (14 files) — re-points the engine's loader, a consumer-affecting cross-repo change.
- The 2 MIXED wave files' second mechanism · the 8 PANDOC-CLASS-LEAK · the 8 GLYPH-NEEDED · `unsong` (.azw3).
- **Housekeeping (fresh-session slot):** skill-harvest register compaction + verification-ladder batch-append — still owed, register exceeds read caps.

**PAUSE STATEMENT:** I am about to be away. Two supersessions are landed, everything is pushed, and no work is half-finished — this is a clean seam, which is rarer than it sounds. What I want to find still pulling: **the V1-purpose question, still unanswered and still first** — not quietly displaced by another round of library work, however tractable. The library work is now genuinely optional-until-scoped, and that is the whole point of the versioned frame.

**LITERAL QUESTION for next-Claude:** The steward has re-pointed to Chamber V1 twice now and both times the session went to library work instead — good work, ruled work, but not *that* work. Is that displacement a signal that the V1-purpose question is not actually answerable yet (missing some input we haven't named), or is it just that library work is legible and a purpose-decision is not? Naming which one it is matters more than another supersession.

**State at wrap:** chamber-library, studium-engine, ARC, CapableMind-AI — all **clean, 0 unpushed**. chamber pushed to both `github` and Gitea `origin` (Gitea cooperated). Spec **v2.8.0 operative** (v2.7.0, v2.6.0 frozen). Fleet **288/288**. REVIEWED-75 placed. Ledger: `session-ledger-2026-07-25.md` (carries the 07-27 returns).