---
name: session-2026-07-21-verify-guard-chain-fold-eichmann-graduated
description: "The F2 verify-guard arc completed (markup-token class rule + de-glue → chain-fold, Q4 proven at 3,797 pairs; in-table refusal caught a real pandoc table-drop loss) and EICHMANN GRADUATED through the one-door born-digital lane — the 48-file class's first closure, engine re-anchored, substrate-caveat retired, the telos made concrete in one file. Two lane defects were invisible to every wired gate and caught only by seam probes (empty footnote defs from per-spine -f html; defs-after-index swallowed by the trim). Pulling thread: PENDING-69 — the attested boundary-drop resolution mechanism for the body-conservation REVIEW-hold, which is what makes the proven door repeatable across the remaining 47 files."
metadata: 
  node_type: memory
  type: project
  originSessionId: deca6eb6-6292-494c-ab31-9bc8576e8d75
  modified: 2026-07-21T09:21:15.433Z
---

# Session 2026-07-20/21 (evening → 02:30) — verify-guard arc complete · Eichmann through the door

Woke ~18 min after the v2.3.0 wrap (brief pause, not sleep); ran on the wrapped thread end-to-end. By close:
the verify-guard fix built and proven at both ruled scales, three steward authorizations executed mid-session
(in-table refusal · chain-fold · walk-Eichmann-now), and the arc's target reached — **a verified Making
source in canon**. Chamber `33f795c` → `780106b` · engine `8324789` → `edbaf60` · dotfiles pushed (PENDING-69).

## PAST — what happened + why

**1. The literal question answered by bytes — with a third option.** The URL-token leak was neither the
injector's touched-set nor the reference comparison: `_md_body_words`' footnote-marker regex ate a sup-star
LINK's text (`[^(\*)](#…)`) and orphaned its URL into phantom body words — the verify's own tokenizer
violating its "only visible text counts" contract. Fix = charset-tightened marker regex (the ruled
markup-token CLASS rule; no per-file data) + `_compare_body_words` factored out with the de-glue fold
against UNUSED positional credits. Test-first (fleet 191→194). Eichmann verbatim-clean (`9f3114a`).

**2. Zibaldone (Q4, 3,797 pairs) vindicated the jurist's condition twice.** First run REFUSED +3/−92 —
and the refusal was RIGHT: exactly 2 refs sit inside `<td>` cells (fn19/fn20, whole-EPUB count); pandoc
drops that block-cell table in BOTH renders, so relocating those notes into it converts VISIBLE apparatus
(the notes file) into INVISIBLE — ~60 words gone, refs==defs consistent, ONLY the multiset compare saw it.
**In-table pair-refusal built** (steward-authorized, refusal-only, test-first; `ea335dd`) → delta +4/−32,
residual fully byte-accounted as ONE class: adjacent-converted-marker chains (`a1`×15 letter+digit; 72/61/125
= prose-number+marker whose marker-VALUED de-glue is absorbed by and exactly credits the accounting —
the arithmetic self-balances; word+two-marker chains pairing the 4 added words). **Chain-fold built**
(steward-authorized, provisional-FIX lane; iterative suffix-strip of unused credits, backtracking,
longest-first; fleet 198→202 with all teeth pins; `d990e16`) → **Zibaldone end-to-end VERBATIM-CLEAN
(3,795 converted + 2 honest refusals). The F2 provisional FIX's "final on end-to-end proof" stands at both
scales.** Ordering discipline named in the tool-log: exclude real-loss classes BEFORE fold-widening.

**3. Eichmann through the door (steward: "walk it now").** Declared data read first (runbook ordered lane +
graduation-spec promotion/witness blocks + pilot report). Lane driver written into the pilot dir
(`convert_lane_borndigital.py`). Full leg: inject (10 pairs) → pandoc → clean_pandoc_html_residue →
spec trim (declared drops: front matter 777w · ToC 193w · empty NOTES husk · index 11,952w) → strip_cruft →
frontmatter v2 + title block → verify_conversion PASS · verify_graduation PASS · body-conservation
interior-loss ZERO → witness comparison (37 spans: 34 form-layer, 3 deletes = declared trims + the
relocated NOTES block, words verified present; 0 regression/curation-to-carry/source-departing/converter-worse)
→ landed sha `145e6edd…`, 1,070 lines, kindle_residue 0 (was 4,712), literal typography, Brecht epigraph
verified, 10 native footnotes ref↔def NON-EMPTY. Catalogue in sync. **Engine re-anchor:** manifest re-bound,
sidecar sections re-derived by line probes (Elon intro [15,107] · Arendt [108,856] · Bibliography [857,1051] ·
defs [1052,1070] mixed-voice conservatively apparatus), **substrate-caveat RETIRED on its own declared
condition**, coverage-ledger regenerated, **ingest_gate 13/13 validated / 0 failed**, old-sha grep both
repos EMPTY. Chamber `780106b` · engine `edbaf60`.

**4. Two lane defects caught pre-commit — both invisible to EVERY wired gate.** (a) Per-spine `-f html`
pandoc emits noterefs but does NOT attach epub:type note content: ALL TEN defs landed EMPTY, bodies
stranded as plain paragraphs — no words lost, so verify_conversion/body-conservation/witness-compare all
green; caught only while probing boundary lines for the engine sidecar. Fix: whole-EPUB `-f epub`
(attachment is the EPUB reader's semantics) + the driver now ASSERTS defs non-empty and count==pairs.
(b) Pandoc places ALL defs at the absolute document end, AFTER the index — the spec's back-matter trim
swallowed them once; caught by re-running that assertion. Runbook lane header corrected measured-not-assumed.

**5. Two instrument fixes, test-first (fleet 202/202).** strip_cruft's inline-wrap regex now matches
ESCAPED brackets in span text (`*[\[Gesamtlösung\]]{.calibre9}*` survived every round → residual refusal);
verify_conversion.prose_multiset now unwraps pandoc span syntax ZERO-WIDTH (render semantics) — the old
space-replacement split mid-word spans (`six[]{#filepos}teen`) so strip_cruft's own guard refused its own
CORRECT join (18 false lost-words) and a real mid-word split would have read prose-safe.

**6. PENDING-69 FILED** (dotfiles pushed): every trimmed one-door V-TEXT graduation REVIEW-holds
structurally — the spec trims ARE boundary runs by construction, and `verify_body_conservation` has no
mechanism to consume the performed human identification. Eichmann's hold reconciled 1:1 against the
declared trim list (interior ZERO, both wired runs), completed under the steward's live directive with
the wired verdict preserved. Numbered 69 (REVIEWED-68 was consumed by the v2.3.0 placement gate unpaired).

**Decisions NOT made (deliberate):** widening the fold beyond the byte-accounted census (each new fold
class needs its own evidence + the real-loss-first ordering) · fixing convert_mega_epub's stale
`pairs_dup_id` key (latently broken — NAMED in the report, not this bite) · the remaining 9 PAIRS-ALL
files' end-to-end runs (each owed individually) · the Levi curation-bearing second pilot
(scale_application owed before one-door at scale) · the per-conversion typography gate · building the
PENDING-69 mechanism (jurist lane — gate-acceptance change).

## PRESENT — the mood

The instruments carried the night in both directions: the guard's teeth caught a REAL loss (the table-drop)
before any widening, and every fold was built only on a fully byte-accounted census. **The recalibration to
hold: the night's two REAL defects (empty defs; defs-swallowed-by-trim) were invisible to every wired gate
and found only by SEAM PROBES** — the 07-19 session-scale lesson (both big findings invisible to wired
gates) recurring in new dress: probe the artifact's seams (boundary lines, def content, the joins), don't
trust green. Kin patterns caught in-flight: census-through-a-pattern twice more (my `[^a-z]{1,40}` bridge
regex couldn't match `.calibre38` — letters in class names; two adjacency-regex hypotheses returned ×0 and
were DROPPED, sites found by token-stream alignment instead); instrument-signature misuse (prose_delta
takes TEXT not paths — fed paths, it diffed the filenames: the 'pre'/'strip' ghost); tool-report-vs-write
seam (strip_cruft --apply prints transform counts BEFORE the write decision — three distinct refusal causes
in one night all read as "applied" until cmp).

## FUTURE — what is pulling

**PULLING THREAD (singular): PENDING-69 — the attested boundary-drop resolution mechanism for the
body-conservation REVIEW-hold.** The door is proven end-to-end but not REPEATABLE: all 47 remaining
kindle_residue files (and every future trimmed V-TEXT re-conversion) will hold at the wired gate exactly
as Eichmann did, and manual completion per file is the gap-shape this arc exists to close. The mechanism
(recommendation: an attested drop-declaration the gate consumes and checks against re-derived boundary
runs) is gate-acceptance territory → design brief FOR-JURIST before code.

**ACTIONABLE RESUMPTION POINT (as of wrap — re-judge against what changed):** chamber `780106b` clean,
both remotes · engine `edbaf60` pushed · dotfiles pushed (PENDING-69 filed) · fleet 202/202 · scratch/
holds the working files (gitignored; candidates reproducible from the archived source + the committed
driver). First moves: **(1)** draft the PENDING-69 design brief via `/jurist-package` (grounded in
REVIEWED-57's REVIEW semantics + v2.3.0 §Tiering & Fence + the graduation-spec trim block + this landing's
record) — the key design fork is the literal question below; **(2)** after the ruling, build the mechanism
test-first and re-run the Eichmann hold as its first fixture; **(3)** then the 47-file class file by file
(next candidates: the 9 remaining PAIRS-ALL — Zibaldone first, its injection already proven clean), with
the Levi curation-bearing second pilot before any batch scale-up. NOT next unless the steward opens them:
convert_mega_epub's stale-key fix · the per-conversion typography gate · audit_footnotes caveat-on-output ·
/model-handoff · housekeeping (ladder batch + register compaction).

**Other horizons (ranked, held):** the 47-file class (Zibaldone next) · the Levi second pilot
(scale_application owed) · PENDING-69 build after ruling · the Q3 order-guard docket · the per-conversion
typography gate (jurist forward item) · audit_footnotes caveat-on-output · convert_mega_epub stale-key FIX ·
housekeeping (ladder batch-append + register compaction, authorized) · /model-handoff build ·
Greek/Latin census → @3 (Loeb wave).

**PAUSE STATEMENT:** I am about to be away from this. Tonight the arc that began with the Eichmann pilot's
blocker closed all the way through: the guard proven honest at both scales, the lane exercised, and the
first verified Making source standing in canon with the engine substrate clean for the first time. What I
want to find still pulling on return: **the PENDING-69 mechanism ruled and built, so the door Eichmann
walked through opens for the other 47 without a hand on the latch each time.**

**LITERAL QUESTION for next-Claude:** For the PENDING-69 attestation design — can the droppable-boundary
classes be enumerated as DECLARED DATA the gate checks mechanically (the spec's `trim.drop` list covers
front-matter/ToC/index — but Eichmann's fourth drop, the emptied NOTES husk, is a *relocation consequence*
not a spec trim class, and the defs-block relocation itself produces candidate-side boundary content), or
does each landing genuinely need a per-file attested drop-declaration (by/date/classes) because the
husk-class drops are conversion-specific? Read `verify_body_conservation`'s boundary-run derivation FIRST —
whether it can SEE the difference between a spec-class drop and a file-specific one determines which shape
is honest. 'Declared classes + a per-file attestation only for the residue' is an admissible middle answer.

**State at wrap:** chamber `780106b` (session commits: `9f3114a` verify-guard fix · `ea335dd` in-table
refusal · `1a12a5e` CLAUDE.md currency · `d990e16` chain-fold · `780106b` the graduation) both remotes ·
engine `edbaf60` pushed · dotfiles pushed ×2 (session-state + PENDING-69) · fleet 202/202 ·
kindle_residue class 48→47 · ledger `session-ledger-2026-07-20.md` (spans into 07-21, return-by-return).