session 2026-07-19 night: one-door authorized (REVIEWED-66) + V1 built + @2 governing (PENDING-66 closed) + audit_cruft kindle_residue

claude/memory/MEMORY-reference.md

@@ -29,6 +29,10 @@ 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-19 evening — engine gate legibility + one-door framed + five-session plan; demoted on promote at the night wrap)
+
+- [Session 2026-07-19 (evening) — ENGINE GATE LEGIBILITY LANDED; ONE-DOOR DECISION FRAMED; FIVE-SESSION PLAN BANKED](session-2026-07-19-evening-engine-gate-legibility-one-door-plan.md) — **The engine pull ran whole** (engine `359e484`+`c024f6a`+`cffc68c` GitHub; chamber `1a217a1` both remotes): census found the committed ledger asserting `status:"validated"` on FAILED sources' rows (PASS-BUT-FALSELY in git; errors stdout-only) → **gate failure-legibility built** (failures NAMED in the artifact + honest per-row states; known-vs-new = DECLARED DATA `corpus/known-failures.json` — exact-signature entries, mutated=NEW, stale=RED; **declaration changes reporting, never acceptance**; `tests/test_ingest_gate.py` = the engine's FIRST test floor, 24/24, witnessed red) → **lifecycle proven on the real five** (declared 5-known/0-new → repaired → 10 STALE red witnessed → retired → 13 validated, exit 0) → re-anchor **re-VERIFIED never re-stamped** (old states sha-matched in ARC git @`355757d`; deltas = exactly the cul-de-lampe hunks; **the completeness grep caught a SIXTH binding surface** — the after-the-reply reading-index, 48 anchors re-verified ellipsis-aware) → **erratum: the plan's "21 sources — verified, not recalled" was FALSE at writing** (git 8→14→13; corrected at 3 surfaces, `cffc68c`). **Frame question ANSWERED** (spec-note §4): engine binds path+sha only, NO chamber-geometry consumer; bounds-valid≠content-correct → **content-probe fence = named follow-on**. **Then the steward-led planning — the map corrected TWICE** (the non-Loeb shortlist spine under-represented: born-digital tier verbatim-UNCERTIFIED as a class [V-TEXT §6 sweep never ran], **Eichmann DIRTY inside the live manifest**, Levi/Handke rulings owed; and the extant ~1305 have almost no sidecars/frontmatter) → **ONE DOOR framed (NOT yet ruled): promotion = graduation through the current process**; extant tier = interim substrate / **witness corpus** (convert-and-compare flips role; curation-diff guards notes-are-part-of-the-work) / exception lane (through-the-door · source-missing · V-SCAN abstain) → **PENDING-65 to draft at S2a** (jurist-gated; promotion-criterion = named-open frontier). **FIVE-SESSION PLAN BANKED: S1 V1 byte-existence checker · S2a PENDING-65 · S2b Position-I pilot wave (Eichmann first) · S3 V2 · S4 N1 (floating) · S5 #2 re-stamp (appetite; batches coupled).** ⚠ Steward sitting owed: REVIEWED-55 placement + skill-harvest review (standing since 07-12). **PULLING THREAD: S1 — V1** per the banked plan (read `spec/v0-verifier-contract.md` + cluster-a §5.1 FRESH first; Eichmann verdicts wear known-dirty until S2b). **LITERAL Q: does `fidelity_equivalence@1` as ratified suffice for the manifested corpus's orthography (FR elision/œ · DE ß/ss · em-dash/quote conventions of our conversion history) — or does building V1's normalized-match stage surface equivalences the jurist-gated floor must rule on BEFORE the checker can verdict `altered` honestly?** Read the session file at wake.
+
 ## Archived (2026-07-19 day — coordinate-contract arc CLOSED, spec v2.2.0 operative; demoted on promote at the evening wrap)
 
 - [Session 2026-07-19 (day) — COORDINATE-CONTRACT ARC CLOSED; SPEC v2.2.0 OPERATIVE](session-2026-07-19-coordinate-contract-arc-closed-v2.2.0.md) — **The whole remaining arc in one sitting: REVIEWED-64 build → placement gate → correction → ratification → v2.2.0 LANDED → REVIEWED-65 PLACED (`~/REVIEWED.md:605`); PENDING-64 CLOSED.** Build (`9112564`): edit-set spine with an explicit §3 consequence-trace (the quote-is-not-trace antidote run as a SECTION) → witnessed red 181/187 → frames as DECLARED DATA (`sidecar.frames:` — **landed-file** contract · **producer-index** transitional · `line_frame` schema-optional/**GATE-REQUIRED**) → gate stamps the producer frame + refuses undeclared/unknown/**contract-at-#1** (jurist: "the best thing in this build" — refuse the dangerous CLAIM, not merely the value) → **the 11 declared** (bounded diff ×11, 11/11 revalidate clean). Placement gate (`7dd852e`): **(a) v2.2.0 on doctrinal-traceability** (placement separable from PROPOSAL weight); **required correction — the jurist refused their OWN unbuilt multi-point probe into constitutional text** (reconciliation-corollary precedent): constitution = REQUIREMENT (verified ⇔ verified in the landed frame against `source_sha256`, never defaulted) + the no-mixed-frame PROPERTY; mechanism → `sidecar.translation:` declared data, revisable without supersession; flags: schema doc renamed `sidecar-schema-LOCKED-2026-07-12.md`; `producer_frames` KEYED to the named producer (unmapped → no stamp → HOLDS; red 186/188→green 188/188). Landing (`81cbdd1`): v2.1.0 frozen byte-identical; §III *coordinate contract* subsection with the Ion record; bounded-diff proven (99 lines + title, all else verbatim). ⚠ **Pacing coupling recorded** (CLAUDE.md batch line): pre-#2 batches grow the untranslated backlog — census it when appetite says "next batch". Say-do wobble self-caught: the Addendum asserted APPLIED ahead of the acts (made true pre-commit; watch record-after-act). **PULLING THREAD: the ENGINE PULL** (session 3's held slot) — known-vs-newly-failing `ingest_gate` distinguishability (5 standing after-the-reply FAILED rows since 2026-06-17; state deltas against a committed baseline, never cleanliness) + the after-the-reply re-anchor; read `stage-1-rebuild-plan-2026-07-05.md` FRESH first. **LITERAL Q: does the engine's ingest side need its own frame-declaration refusal now that the chamber gate refuses at graduation — does anything in the engine today read sidecar line geometry, or does it bind only path+sha — and if the latter, where is the STRUCTURAL fence (not a discipline) that keeps a future engine consumer from binding undeclared-or-transitional geometry?** Read the session file at wake. *(Engine-pull outcome + the answered literal Q: the evening session file.)*