---
name: session-ledger-2026-07-25
description: "Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses."
metadata: 
  node_type: memory
  type: feedback
  originSessionId: 58ba5886-9bb6-415f-9440-a4b87099ffa0
  modified: 2026-07-25T08:17:12.490Z
---

# Session Ledger — 2026-07-25

## Returns
- 2026-07-25T06:45 — Cleaner A built test-first (`strip_source_presentation.py`, 242/242, verbatim-safe). Proved on the-shape-of-a-pocket: A kills all `{.class}` (59→0) but is **necessary-not-sufficient** — second obstacle = `:::` fenced divs (pandoc fences ALL `<div>`), + orphan id-anchors. **Literal question answered: NO, the class is not one fix deep.** Returns caught: (1) tested the census's premise ("deep nesting") against the substrate — FALSE for this file (shallow breadth + fences); (2) tested my own proposed fix (div-unwrap) rather than inferring.
- 2026-07-25T07:05 — ⚑ **SELF-CORRECTION (assert-from-derived recurrence, 2nd today).** I reported "div-unwrap BREAKS footnotes 7→0" — FALSE, a buggy probe regex (`^..\d+..:` ≠ `[^1]:`; same class as the `\b`-census bug). Re-counted with the lane's own regex → 7 defs intact on ALL candidates incl. div-unwrapped. Note bodies are `<p epub:type>`, immune to div-unwrap. The false finding shaped the steward's ruling; corrected the log + ledger before propagating. Lesson: **produce the checkable claim with the SAME instrument the production path uses; ad-hoc probe regexes are where the lies creep in.** The steward's ruling STILL holds — verify_lossless IS blind to apparatus (true regardless), and a `<div epub:type=footnote>` file WOULD break — so the apparatus guard + relational unwrap are right as insurance for the class.

## Open horizons
- 2026-07-25T06:18 — Woke into the V-TEXT wave unlock thread (CONFIRMED, unchanged tree). Build (A) pre-processing nested-span/anchor cleaner [HTML-parser, prose-safe — NOT regex] + (B) `_tokens` ignores pandoc `{…}` attribute grammar as a CLASS → graduate `the-shape-of-a-pocket` end-to-end. Test-first. The census (`_curation/v-text-wave-gap-census-2026-07-24.md`) carries the fix shape.
- Inherited disciplines to hold: **test, don't infer — against the substrate** (won ~6× last session); build **to the constitution, not to legacy-canon precedent**; **change-impact clause** (a producer change must enumerate its consumers — 3 instances now). Steward energy: census says build "when there is energy — not a tired-tail push."

- 2026-07-25T07:40 — Cleaner A EXTENDED per the steward's 3-gate ruling: apparatus-preservation guard (inside the tool, relational, teeth) + relational wrapper-unwrap/orphan-id (epub:type + live-link-graph gated) + policy-gated opt-in (unwrap defaults OFF). 248/248. Committed `3874f7f` (+ census `6d7ff84`, CLAUDE.md `73ae8e3`). Proven on the-shape-of-a-pocket: solves layers 1(class)+2(fences) footnote-safe (apparatus guard passed, 7 defs); residual 54 = 3 curation-policy categories (44 pandoc spine anchors mechanical · 24 referenced internal-nav fences+27 links · 14 art plates+1 SVG), NOT a tool gap.

## Open horizons
- LAYER-3 CURATION FORK (steward's to rule): (a) internal-nav keep/strip (24 referenced fences + 27 cross-ref links; if strip, link-graph-consistent); (b) art-book plates — the-shape-of-a-pocket is Berger on painting; 14 plates content or cruft? This reframes the wave: "31 heavy-styled" is a volume label over heterogeneous structural+curatorial kinds — per-file diagnosis confirmed.
- GATE-3 governed policy landing (the SPECIFIC blocker before any corpus-wide run): the presentational-wrapper claim as GROUNDED declared data in `graduation-spec.yaml` (hook-gated; F4 shape / kin REVIEWED-67 front-end-eligibility). The tool must not ACT corpus-wide until landed.
- Then: `strip_cruft` spine-anchor recognition (mechanical residual) · B `_tokens` `{…}`-attribute-class FIX (gate PASS) · lane-wiring + graduation.
- Twice today: assert-from-derived-not-substrate (buggy ad-hoc regexes: `\b` census, `^..\d+..:` def-count). Reinforced: produce the checkable claim with the SAME instrument the production path uses.

- 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.