session 2026-07-19: coordinate-contract arc closed — REVIEWED-64 built + placement-gated, spec v2.2.0 landed, REVIEWED-65 placed; PENDING-64 closed

claude/memory/MEMORY-reference.md

@@ -21,6 +21,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-18/19 S5 night — coordinate contract RULED, REVIEWED-64 placed; demoted on promote at the 2026-07-19 wrap)
+
+- [Session 2026-07-18/19 (S5, night) — COORDINATE CONTRACT RULED; REVIEWED-64 PLACED](session-2026-07-18-s5-night-coordinate-contract-ruled-reviewed64.md) — **Package → design-gate → ruling → authorization in ONE sitting; nothing built past it.** Composed `docs/coordinate-contract-FOR-JURIST-2026-07-18.md` grounded/hook-passed (PENDING-64, `46404ef`); **fresh Ion measurement on the LANDED file became the ruling's "best evidence"**: raw `line:161` fails under BOTH read-frames (1-based mid-Greek · 0-based empty; the S3 RECORD and this probe DISAGREED by silent base-choice), coherent only in the +11…+16 head-delta window. **Design-gate PASSED** (filed verbatim `docs/coordinate-contract-design-gate-JURIST-RULING-2026-07-18.md`, `fb728be`): Option B substance **REFRAMED — ONE constitutional contract** (1-based line in `source_file` valid against `source_sha256`; hash-locality extended to *where in the file*); producer index = **declared transitional state** (consumers refuse untranslated, never handle both). **EXTENDED twice past the package:** (1) binds **ALL FIVE families** — §III shared-substrate forbids mixed-frame at any committed point (the jurist caught my plan violating a clause I QUOTED — harvest: `grounding-quoted-but-not-traced`); (2) `notes[]` credit = **linkage-only**, geometry uncredited (trust-by-adjacency inside one field). D3 name-the-frames (ONE per-sidecar declaration, **schema-optional/GATE-REQUIRED**, FIX lane, Naming note = the collision-class register — 4th instance); D4 **declare-now on the 11**; Q4 one docket PROPOSAL+FIX; Q6 **multi-point probe per work, honest-refuse** where no single constant holds. C-1 datum-not-ledger 3rd unbidden instance recorded (candidate STANDS; trigger sharpened: domain-external). **REVIEWED-64 PLACED (`~/REVIEWED.md:599`).** Chamber CLAUDE.md 2b line HELD-OPEN→RULED. **⚠ PULLING THREAD: the REVIEWED-64 BUILD — next session, BEFORE the engine pull** ("declare now" = an honesty debt): amendment edit-set doc first (FIX-A pattern, the docket's spine) → frame naming + per-sidecar declaration (FIX lane) → graduation refusal (declared data + thin consumer, test-first witnessed red) → the 11 declarations (bounded-diff ×11) → `notes[]` statement → stale SURFACED/`write_sidecar` comments updated in-pass. NOT that session: the translation (#2's work, Region 4). Then the engine pull (ingest_gate known-vs-new + after-the-reply re-anchor). **LITERAL Q: where does the contract's constitutional text land — a spec supersession (v2.2.0 subsection under §III/§VII), or ruled doctrine in the schema doc + graduation-spec with the ruling as its constitutional record — and does PROPOSAL weight itself entail the spec vehicle, or is placement a separate lighter call the amendment doc puts to the jurist as its first gate question?** Read the session file at wake.
+
 ## Archived (2026-07-18 S4 second wake — PREP→FLEET + batch 2; `unrecognized` proven on real structure; demoted on promote at the S5 wrap)
 
 - [Session 2026-07-18 (S4, second wake) — PREP→FLEET + BATCH 2; `unrecognized` PROVEN on real structure](session-2026-07-18-s4-prep-fleet-batch2-unrecognized-proven.md) — **The door proven routine.** `prep_loeb_candidate` built test-first (red WITNESSED 157/158→177/177; **S3's literal Q ANSWERED**: mechanical derivation + the curated table as tool-level DECLARED DATA `_curation/loeb-prep-curation.yaml`, overrides EMPTY — covered all 11 landed works); **batch 2 GRADUATED observed** (`2f5a029`): fab 0 · lost 0 ×5, **Timaeus fired app[table]:1 — the credit's first real book**, Theogony list 35, attach-at-11 on the one artifact hash, staging cleared at last reference, catalogue 1305, Encheiridion → stoic_voices (2nd tradition dest). Steward review → closures in-hour (`f997595`): **`unrecognized` POSITIVE-TESTED** (DSL census 465 works w/ structure / 448 list-only / **17 novel = the far-country watch-list**, `_curation/loeb-dsl-structure-census-2026-07-18.json`; Menander 6×div papyrus columns · Pausanias 94/94 figcaption 1:1 · NE 1×figure; INVERTED expectation: a Pausanias batch reporting `unrecognized: 0` = broken net, not clean book) · refcount lifecycle RECORDED deliberate (3 homes; structural: every slug's no-op re-proves content from STAGED bytes → move-at-first would strand 2..N) · lang/symlink branches fixtured (fleet **180/180**) · **ARC→engine re-anchor = PENDING-53's scope gap** (runbook `reanchor:` scope_note; the 5 `after-the-reply` FAILED rows standing since 07-10; steward: known-failing vs newly-failing must be structurally distinguishable or the gate trains readers to skip it → engine-session design item, NOT built cross-repo). Chamber @ `3aae628` both remotes; no new PENDING. **⚠ PULLING THREAD: Session 2 — the line-ref coordinate-contract FOR-JURIST package** (hook-gated; substrate inputs banked: the SURFACED note in `graduate_to_canonical.py` ~l.238 · the Ion offset in RECORD §(c) + work-map R4 · sidecar-schema line examples · item (f) as amended · `write_sidecar`'s stamp-binds-the-file note). Then S3 = the engine pull (+ ingest_gate known-vs-new + after-the-reply re-anchor). **LITERAL Q: does ONE coordinate contract serve both the producer's body-array indices (tool-internal convention) and the landed file's citation coordinates (#2's re-stamp output) — or are these two DIFFERENT contracts that meet only at the re-stamp, so ruling them as one would bind a tool's internals into the constitution where only the landed-file contract belongs?** Read the session file at wake.