session 2026-07-24: chamber-sources problem CLOSED — Levi omnibus re-sourced + all 13 source gaps filled + invariant landed in chamber CLAUDE.md; 935MB byte-dupes purged; Silva named; Warde OCR on M4; wake into the Levi 14-bracket verify

claude/memory/MEMORY-reference.md

@@ -5,7 +5,7 @@ metadata:
   node_type: memory
   type: reference
   originSessionId: d1e67361-d1b9-4dac-a0c4-e7a0e26211c4
-  modified: 2026-07-22T12:37:10.191Z
+  modified: 2026-07-24T08:49:17.702Z
 ---
 
 # MEMORY — Reference layer (consult on demand)
@@ -29,6 +29,9 @@ Split out of [MEMORY.md](MEMORY.md) on 2026-07-06 to keep the wake-loaded index
 
 # Archived sessions + stable reference layer (relocated verbatim from MEMORY.md, 2026-07-06)
 
+## Archived (2026-07-23 — REVIEWED-69 merged + v2.4.0 · character-as-image finding → PENDING-70 → v2.5.0 · glyph-mapping BUILT; demoted on promote at the 2026-07-24 wrap)
+- [Session 2026-07-23 — REVIEWED-69 merged + v2.4.0 · character-as-image finding → PENDING-70 ruling → v2.5.0 · glyph-mapping BUILT](session-2026-07-23-reviewed69-70-v2.4-v2.5-character-as-image-glyph-mapping.md) — A very long single session that ran the whole PENDING-69/70 arc to ground. **(1)** merged the boundary-drop mechanism to main + cut spec **v2.4.0** (REVIEWED-69; standalone MINOR bump — vehicle resolved by fact, nothing assembling; `f466ed0`). **(2) Prepping the Levi pilot surfaced a corpus-integrity finding:** the witness is silently DAMAGED — a 2026-06-16 image-drop MUTILATED char-bearing glyphs mid-word (Wstawać→Wstawa, Brașov→Braov, Oświęcim→Owicim), verified live, each confirmed by the passage's own gloss. Steward named the structural cause: **the whole canon predates the constitution + the fleet** → the extant witness is a pre-fleet conversion, not editorial gold; census = **13/248-backup files** carry mid-word glyph drops (Jung 18, Levi 18, Derrida, Zibaldone, Lichtenberg…), a confirmed floor. **(3)** drafted the legacy-body reframe as a jurist package (PENDING-70) → **RULED**: Q1/Q3/Q4 confirmed (Q1 corrects a defect in the one-door ruling's OWN wording; `witness_class`=positive attributed attestation), **Q2 accepted-in-principle but SUBSTITUTE CONDITION ruled** (my reframe dropped the JUDGMENT-COST test the condition existed for — enumerate demonstrable classes in advance · report judgment cost · legacy-witness-promotions-only) → **spec v2.5.0 landed** (`e37e076`). **(4) glyph-mapping BUILT + DEMONSTRATED** (`apply_char_glyphs.py`, the Q3 hard precondition; `3852d46`; fleet 216→**222**): letter-adjacent glyph `<img>`→declared SOURCE Unicode, REFUSES unclassified (attest-never-default); VIEWED the 4 source glyphs (ca=ć, as=**ş cedilla** steward-confirmed NOT comma-below ș, s=ś, e=ę); demonstrated on the real 527-doc Levi EPUB (substituted=9, unclassified=0 corpus-wide, survives pandoc end-to-end). **PULLING THREAD: the Levi second pilot ITSELF (step 3) — now unblocked, the gate before the 47-file verbatim-fidelity-restoration wave.** First move = derive + interior-verify the 14 witness brackets (La Chute lesson) → run the full lane (`convert_lane_borndigital.py … the-complete-works-of-primo-levi-primo-levi`) → 14 per-work comparisons + **JUDGMENT-COST reporting** (the substitute Q2 condition). **LITERAL Q: when the Levi pilot runs (14 works, ~18 mutilation sites now repaired), does the judgment cost stay tractable, or explode when the easy mechanical patterns run out (the jurist's actual worry)? + do the 14 brackets interior-verify cleanly at omnibus scale?** ⚠ origin (Gitea) 2 commits behind (`5d61f2d`,`3852d46`) — retry when it recovers. Read the session file at wake.
+
 ## Archived (2026-07-22 — PENDING-69 boundary-drop mechanism drafted→ruled→BUILT + /model-handoff; demoted on promote at the 2026-07-23 wrap)
 - [Session 2026-07-22 — PENDING-69 boundary-drop mechanism drafted→ruled→BUILT (Q7 capstone passed) · /model-handoff](session-2026-07-22-pending69-boundary-drop-mechanism-built-model-handoff.md) — The whole PENDING-69 arc in one remote session (steward in Salzburg, machine at home): package DRAFTED reading the gate's code FIRST (literal-q honored — the gate classifies boundary runs by POSITION+SIZE only, provably CANNOT confirm class identity → REVIEW stops, no channel for the human id) → **RULING PASSED with corrections, Q2 OVERTURNED my lean to (b) vocabulary-only** (a privileged "spec-class" = **trust-by-name**; `trim.drop` is a label vocabulary, every run per-file attested) → **mechanism BUILT test-first** on branch `reviewed-69-boundary-drop-resolution` @ `21e3499` (NOT main): `resolve_review` + additive `boundary_run_sig` (ratified verdict logic UNCHANGED, seed re-confirmed) + `boundary_drops` declared data + `_resolve_boundary_review` thin consumer; fleet 214→216; **Q7 CAPSTONE PASSED on the REAL Eichmann** (verdict=REVIEW, interior_loss=0, **8 boundary runs** = 3 front-matter + 5 index → mechanical PASS; both negatives refuse). Then **`/model-handoff` BUILT** (authorized ⚖ Stroke 3). Honored "nothing lands on main without your confirmation" — branched, did NOT push. Substrate lesson: the k-gram aligner is **MOVE-BLIND** → boundary runs are DROPS, `relocation` the rare reordered case (corrected my own package framing). Q5 added-side exclusion scoped OUT (conservative). **PULLING THREAD: the Levi curation-bearing SECOND PILOT — the last gate before the 47-file wave; BLOCKED on the steward's 3 actions (2026-07-23 pm): place REVIEWED-69 · merge `21e3499`→main+push · vehicle-call the ONE constitutional §Tiering&Fence sentence (drafted). LITERAL Q: when the Levi omnibus (14 works, hand-curated) runs the one-door lane, do its curation-bearing divergences classify tractably (fidelity-restoring vs source-departing — the JUDGMENT cases Eichmann exercised 0×), or does a real case resist? + is the mechanism's SILENCE on inter-work (interior) drops genuinely correct at multi-work scale, or does an inter-work drop hide a real loss? Read the Q6 ruling + `promotion.witness`/`witness_comparison` declared data FIRST.** Read the session file at wake.