governance: REVIEWED-75 placed; PENDING-72/75 built-and-landed; session ledger

REVIEWED-75 (kind-scoping the verification criterion) placed by the steward.

PENDING-75 -> spec v2.7.0 landed with both required corrections (V-SCAN's
distinct criterion preserved; the anti-bypass guard rebound to the property).

PENDING-72 -> spec v2.8.0 landed (voice-purity as the engine-consumable bar),
mechanism built test-first, backfill executed 18/1, gate wired, single-reading-
pass designed. Plus the source_lines FIX: producer + 11 consumers in one
change-set, then corrected again when the base-rate sweep found splitlines()
also wrong (308 lines' disagreement on one canonical).

Ledger records the session's sharpest return: the sweep caught a fix one commit
old, because ratifying a convention by comparing two implementations is
SELECTION, not derivation — I verified the two disagreed, never that either was
right.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Xefg5EXwcpd9RMAr63dWrD

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

@@ -5,7 +5,7 @@ metadata:
   node_type: memory
   type: feedback
   originSessionId: 58ba5886-9bb6-415f-9440-a4b87099ffa0
-  modified: 2026-07-25T07:18:12.687Z
+  modified: 2026-07-25T08:17:12.490Z
 ---
 
 # Session Ledger — 2026-07-25
@@ -29,10 +29,26 @@ metadata:
 - 2026-07-25T08:30 — Mechanism-census RAN over 48 wave files (`_curation/mechanism-census-2026-07-25.tsv`, committed `a527e0a`; volume-census superseded `06331fb`). Distribution: 8 clean/near-clean · 21 internal-nav (one ruling) · 2 MIXED 2nd-mechanism · 8 pandoc-class-leak (French/translation) · 8 glyph-needed · 1 azw3. Dominant lever = ONE internal-nav CURATION RULING, not one cleaner.
 - 2026-07-25T08:30 — RETURN (banked lesson's first live test, steward-flagged): "ONE ruling clears 23" was an inference from residual COMPOSITION, not from what removal DOES — same gap that falsified the volume census. Checked it cheaply from the TSV → clears 21/23; 2 (histoire-de-la-folie resid 246 non-nav, planning-XP 88 non-nav) hide a 2nd mechanism. the-shape-of-a-pocket reconciled (A-unwrap removed the fence layer; residual nav-only). Caught before it got planned around. [[feedback-census-by-mechanism-not-proxy]] working as intended.
 
+- 2026-07-25T10:15 — **NEW CONTEXT (same day, ~6min pause).** Thread RE-POINTED by the steward's post-wrap reframe → [[project-chamber-versioned-releases]]: top thread is now *"which purpose anchors Chamber V1?"*; the nav ruling + the wave + PENDING-75 are INPUTS to that scoping, not open obligations. Lean surfaced at wake: pose the V1-purpose question BEFORE the nav validation, since nav may be V2-deferrable depending on which voices V1 needs.
+- 2026-07-25T10:15 — Wake canary caught two small governance defects, both cheap: (1) **REVIEWED-74's header is indented two spaces** in `~/dotfiles/REVIEWED.md:704` → not a markdown heading, invisible to `^## REVIEWED-` greps ([[feedback-governance-drafting-copy-paste-clean]] recurring — 2nd instance, kin to the REVIEWED-59 header); (2) MEMORY.md's maturation-dialogue pointer is a **relative path that breaks under physical symlink resolution** (memory dir → `~/dotfiles/claude/memory`, so `../../../../_Dev/…` resolves to `/Users/_Dev/…`) — file exists, pointer is fragile; wants an absolute path. Named at wake rather than banked for "a good moment."
+- 2026-07-25T10:15 — ~~Standing authorized-but-unbuilt backlog: REVIEWED-72, -73, -74. All AUTHORIZED, none built.~~ **⚑ STRUCK 10:35 — FALSE, see the return below.**
+- 2026-07-25T10:35 — ⚑ **SELF-CORRECTION (assert-from-derived-not-substrate, 3rd instance in 24h — and the worst-placed).** I told the steward at wake that REVIEWED-72/73/74 were all AUTHORIZED-but-unbuilt and that "the wave stays blocked until REVIEWED-72's demonstration." **Two of the three were FALSE.** Substrate check: REVIEWED-72 **BUILT+LANDED** (`graduation-spec.yaml:424` `reference_writer: markdown-smart`, `:439` `reader_audit`); REVIEWED-74 **BUILT+LANDED** (`verify_body_conservation.py:333` `resolve_added`; `apply_char_glyphs.py:100` two-sided count-scoped manifest); spec v2.6.0 carries both; the four-case unblock demonstration passed 07-24 → **the wave is UNBLOCKED**. Only **REVIEWED-73 (voice-purity sidecar)** is genuinely unbuilt (zero `voice_purity` hits in `scripts/` or `graduation-spec.yaml`; `sidecar_gate` is the unwidened PENDING-56 one). **Mechanism of the error:** 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**. The derived record (REVIEWED.md) and the substrate (code + spec header + CLAUDE.md) disagreed and I never asked the substrate. **Placed in a WAKE BRIEFING**, so it shaped the steward's picture of their own project's state before any work began — the highest-leverage place for a false claim to land. Reusable: *the wake briefing is a claim surface like any other; the backlog section needs the same substrate check as a finding.*
+
 ## Confidence to recalibrate
+- 2026-07-25T10:15 — Confidence that "pose the V1 purpose first" is the right next bite: **0.7** (verified: the re-point doc says purpose-first re-bounds the library work and names nav as V1-conditional; inferred: that the steward wants the decision now rather than more executor groundwork — that is the steward's call, not mine). Uncertain: whether the 3-step nav validation is cheap enough to run *regardless* of V1 scoping, since it also second-hand-checks the census instrument.
 
 ## Authorization moves
 
 ## Sub-agent dialogues
 
 ## Bypasses
+
+## Returns — 2026-07-27 (same session, continued across a power failure)
+
+- 2026-07-27 — ⚑ **THE SESSION'S SHARPEST RETURN: the sweep caught my own fix, one commit old.** Steward ruled FIX + re-stamp-now on the `source_lines` divergence, and added *"confirm the rule rather than the sample — the two formulas disagree only when the file ends in a trailing newline."* That caught a **live corruption risk**: 36/1,297 canonicals have no trailing newline, so a blanket `-= 1` migration would have corrupted exactly those; my 11-file sample (ONE producer, all newline-terminated) could not have shown it. Then the steward-directed base-rate sweep landed on the fix I had **just committed**: I had ratified `len(splitlines())` **without checking what `splitlines()` splits on** (`\v \f \x1c \x1d \x1e \x85 U+2028 U+2029` — breaks no consumer of a line coordinate honours). 4 canonicals carry them; **lintott disagrees by 308 lines**. So BOTH prior formulas were wrong on **complementary subsets** — no single sample distinguishes all three. **Reusable:** *when two implementations of one field disagree, do not pick the survivor — derive the rule from what a CONSUMER of the value must do, then test the shapes where each candidate happens to be right.* Picking the survivor is comparison-as-substitute-for-derivation, a new face of assert-from-derived-not-substrate.
+- 2026-07-27 — Root cause fixed, not the value: ONE implementation (`verify_voice_purity.count_lines`), producers import it. Two formulas for one field is how the divergence arose; a third would have arrived identically. Kin: the change-impact clause (producer-then-consumers in one change-set — fixing the producer while 11 consumers hold the old value is the orphan pattern, steward-named).
+- 2026-07-27 — **The exhaustive-partition rule validated itself on first contact** (REVIEWED-73): applied to the existing engine corpus it surfaced 3 files with unassigned tails **and** `musil-mwq-tome-1`'s drifted binding — *the engine had been serving Musil with boundaries shifted by 6 lines*, unknown to anyone. Also **corrected the ruling's own cited instance**: all five ARC bindings verify clean; the real drift was a chamber canonical.
+- 2026-07-27 — Q2/Q4 reconciliation (steward-confirmed): wiring the voice-purity gate to EVERY candidate would have **silently blocked the Loeb wave with a bar that has no jurisdiction over it**. Found by asking where the two clauses MEET rather than implementing whichever was read last. Reusable: when two ruled clauses appear to conflict on scope, look for the single point where both are true before choosing one.
+
+## Confidence to recalibrate — 2026-07-27
+- Ratifying a convention by comparing two existing implementations felt like *derivation* and was **selection**. Confidence in "the engine-side convention is the correct one": was ~0.9, should have been ≲0.5 — I had verified that the two disagreed, never that either was right. The check that would have caught it cost one line (`\f` in a test string) and was not run until the steward asked for a sweep.