---
name: Session 2026-07-24 (evening, cont.) — REVIEWED-72/74 built + landed atomically (spec v2.6.0); the 47-file V-TEXT wave is unblocked
description: "Continuation of the same day (steward /clear'd to build with room). Built REVIEWED-72's ruled reference (markdown-smart) + REVIEWED-74's added-side MULTISET fabrication check (resolve_added), demonstrated the unblock (four cases: clean PASS · prose-deletion FLAG · fabrication-outside-manifest FLAG · Eichmann regression clean), wired it into the graduation gate, and LANDED it as spec v2.6.0 (bounded-diff proven) committed eaa38bf (github; origin/Gitea unreachable). Grounding measurement REFUTED the jurist's own stated premise (the 287-token Levi added delta = 279 displacement + 8 glyph, NOT injected content — the injector enumerates markers on the LOST side); the jurist owned it (PENDING-73→REVIEWED-74). PULLING THREAD next session = BEGIN THE WAVE: run ONE real non-imaged kindle_residue file end-to-end through the newly-wired gate, proving a real graduation (not just the gate logic), with the added_fabrication_threshold floor-watch live."
metadata:
  node_type: memory
  type: project
  originSessionId: c8dd62d7-df44-4d38-8e66-12bd2afe9a33
  modified: 2026-07-24T14:37:08.351Z
---

# Session 2026-07-24 (evening, continued) — the V-TEXT source-fidelity gate: built, demonstrated, wired, LANDED (spec v2.6.0)

Woke into the Flag-1 pulling thread (build REVIEWED-72 → unblock the wave), pressed one design-gate confirmation (PENDING-73→REVIEWED-74) through the jurist, then built + demonstrated + wired + landed the whole gate atomically. The 47-file wave is now unblocked on a reference that refuses real loss, not merely passes clean files.

## PAST — what happened + why

**Substrate re-read caught the wrap's framing.** The wrap said "the build is bounded." Re-reading the ruling + measuring (`scratchpad/ground_manifest.py`, read-only) showed the naive repoint FLAGs: run (3) carries 287 added tokens → `classify`'s `added_total > 50` → FLAG. So "declare/excuse the injection delta" is a **new added-side gate organ** (the follow-on `resolve_review`'s docstring deferred), not a constant swap. Surfaced this before writing code.

**The measurement REFUTED the jurist's own stated premise (the day's drift-family, good direction).** The ruling (REVIEWED-72) said the 287 was "injected footnote content the injector enumerates exactly." The measurement DECOMPOSED it: **multiset-added = 8 tokens, ALL glyph** (`wstawać×6, oświęcim, braşov`); the other **279 are present-elsewhere in the reference — DISPLACEMENT, multiset-neutral** (classify's position-based run counter mislabels moved apparatus as "added"). The injector's `converted_markers` (646 digit markers) land on the LOST side, explaining 0 of the added. Prior sub-Q settled empirically: `_tokens` uses `\w+`/`re.UNICODE` → PRESERVES diacritics (`wstawać`≠`wstawa`) → glyph is visible + TWO-SIDED. Steward chose routing (b) — "be sure of no surprises" → filed **PENDING-73 + jurist package** (`docs/borndigital-added-side-fabrication-check-JURIST-PACKAGE-2026-07-24.md`; verify-before-compose hook passed). **The jurist RULED (REVIEWED-74) and OWNED the refuted premise** — *"the producer must know X is not evidence the producer records X"* — with four corrections: Q1 in-scope + atomic on a recorded THREE-PART test; Q2 MULTISET over presence (dominates: catches duplication); Q3 two-sided COUNT-SCOPED (Counter subtraction; whole-run-or-nothing loss excuse); Q4 authorizes the glyph CLASS not future normalizations. Plus the 646-marker latent dependency + a FOURTH demo case (Eichmann regression).

**Built to the four corrections + demonstrated + wired.** `verify_body_conservation.resolve_added` (10 invariant fixtures, incl. duplication-catch + count-scoped negatives); `apply_char_glyphs` two-sided manifest (added=joined words / removed=`<img>`-split fragments — the honest asymmetry that tracks the reference's pandoc inline-image tokenization); repointed `reference_tokens_epub`→markdown-smart; **four-case demonstration PASSED on real candidates** (`docs/borndigital-added-side-four-case-demonstration-RECORD-2026-07-24.md`): Case 1 clean Levi PASS (fab=0) · Case 2 prose-deletion FLAG · Case 3 fabrication-outside-manifest FLAG (fab=80) · Case 4 Eichmann added+interior clean (fab=3<23, boundary→resolve_review). Wired into `verify_candidate` + `graduate_to_canonical.body_conservation_gate` (loads `<stem>.glyph-manifest.json` + declared threshold); lane writes the sidecar. Fleet 222→**234**.

**LANDED atomically (steward: "push into the landing").** Spec **v2.5.0→v2.6.0** — froze v2.5.0 byte-identical, **BOUNDED-DIFF PROVEN** (exactly 4 regions: title · v2.6.0 block · source-fidelity clause revision · §Governance 2 disciplines; 4 deleted lines = only the old title + old bullet). 969/1046 reconciled (cross-converter → periodic reader audit, declared data, specified-not-yet-built with cadence/trigger/pass-criterion VISIBLE per steward). graduation-spec `body_conservation:` declared data. §Governance += reassigned-component check (REVIEWED-72) + in-scope-refinement three-part test (REVIEWED-74). Doc currency: chamber CLAUDE.md v2.6.0 + tool-evolution-log. **Committed `eaa38bf`, pushed github ✓; origin/Gitea unreachable (port 443, known-flaky) — retry owed.**

## PRESENT — the mood

**The substrate-first discipline HELD, and its payoff was the sharpest of the day: measurement refuted the jurist's own compressed framing, and the jurist owned it precisely.** This is the assert-from-derived-not-substrate drift-family run in its GOOD direction — read the data before theorizing, and even a ruling's premise yields. Load-bearing: securing the judgment BEFORE building (routing b), then building test-first with the bounded-diff proof as the backstop against a tail-of-session constitutional slip. The Prime Directive's dwelling-warning was live during the spec supersession (constitutional surgery at the end of a marathon) — answered by leaning on the bounded-diff proof (exactly 4 regions, verified) rather than trusting the edit. Nothing felt rushed into; every gate stayed green (234/234) and every hook passed.

## FUTURE — what is pulling

**PULLING THREAD: BEGIN THE 47-FILE V-TEXT WAVE.** The gate is built for exactly this. The clean first bite is narrow: run **ONE real non-imaged kindle_residue file** end-to-end through the newly-wired flow — the demonstration proved the gate *logic*, not a full *graduation* through the wired path.

**ACTIONABLE RESUMPTION POINT (as of wrap — re-judge against what changed):** chamber-library @ `eaa38bf` (github; origin/Gitea retry owed), working tree clean, fleet 234/234. First move: pick a NON-imaged file from `_curation/kindle-residue-census-2026-07-19.tsv` (47 files; EXCLUDE the 12 imaged census-flagged ones — Jung/Derrida/Zibaldone/Lichtenberg/… which need per-source glyph-maps first). Run `_curation/eichmann-pilot-2026-07-19/convert_lane_borndigital.py SOURCE.epub OUT.md MAP.json [SOURCE_ID]` → cleaners → then `graduate_to_canonical` (now runs `resolve_added` on the added side + loads the glyph manifest + boundary-drops). Read the human boundary runs, attest via `<stem>.boundary-drops.json`, graduate. **WATCH the `added_fabrication_threshold` (40) floor** — a real book may surface a benign floor higher than the 2-book calibration.

**Other horizons (ranked):**
- **REVIEWED-73 — the voice-purity sidecar build** (authorized, not started): the larger parallel build (orthogonality · exhaustive-partition · chamber-side · closed-vocab role · line_frame → widen sidecar_gate → migrate ~20 engine sidecars → single reading-pass). Steward chose the wave over this for next session; it can run in parallel with the wave's glyph-map curation.
- **Warde chamber graduation** (WIP): frontmatter rebuild to the schema + its voice-purity sidecar (essays=`text`, CUP-Bible facsimile=`apparatus`) per REVIEWED-73.
- **The reader-audit RUNNER** — specified-not-yet-built named dependency (`body_conservation.reader_audit`); not blocking the wave (periodic).
- **Per-source glyph-maps for the 12 census-flagged imaged files** — each VIEWED + verified before entering the lane (the parallel curation track feeding the imaged half of the wave).
- **origin/Gitea push retry** (chamber-library ahead on origin; github has eaa38bf).

**PAUSE STATEMENT:** I am about to be away. The gate is built, tested, wired, and constitutionally landed (v2.6.0, `eaa38bf` on github) — durable, off my working tree. What I want to find still pulling: **the wave itself — the first REAL graduation through the gate we just built, proving the mechanism holds not on the demonstration but on a live book, with the threshold-floor watch active.**

**LITERAL QUESTION for next-Claude:** When the first real non-imaged V-TEXT file runs end-to-end through the newly-wired gate, does the whole flow produce a clean graduation (resolve_added multiset PASS on the added side + boundary-drop attestation resolving the front/back-matter trims) — or does a live book surface an `added_fabrication_threshold` floor HIGHER than the 2-book calibration (40) predicted, forcing a recalibration of the declared threshold before the wave proceeds? (The gate's correctness is proven on the demonstration; the open question is whether the *calibration* survives contact with a real book.)

**State at wrap:** chamber-library @ `eaa38bf` (github pushed; origin/Gitea unreachable, retry owed); working tree clean; fleet 234/234. REVIEWED-72/74 placed + landed (spec v2.6.0). PENDING-71/72/73 all RULED. Ledger: `session-ledger-2026-07-24.md` (the whole day, rich). Related in-flight: none (the landing is complete).