session 2026-07-19: PENDING-64 lodged+design-gate PASSED, REVIEWED-64 placed (coordinate contract ruled); S5 session file + index rotation + harvest + 3 KG lines

PENDING.md

@@ -1596,3 +1596,13 @@ Disposition (verbatim capture + executor action-list: `chamber-library/docs/libr
 **Recommendation:** (a). Design brief FOR-JURIST before code (gate-zero territory; the enforced precondition's `enforced_by` text in `graduation-spec.yaml` may need a matching FIX).
 **Files affected (on authorization):** `scripts/archive_sources.py` (the shared-source entry form + the pending→archive move) · `scripts/graduate_to_canonical.py` (source_gate apply leg, if the call shape changes) · `_curation/graduation-spec.yaml` `preconditions:` (enforced_by wording, if changed) · `scripts/test_tools.py` (the end-to-end positive test) · Chamber Sources `manifest.json`/`pending-manifest.json` entry shapes.
 **Awaiting:** ~~Jurist design-gate (Q1–Q7)~~ **DESIGN-GATE PASSED 2026-07-18** (`chamber-library/docs/PENDING-63-design-gate-JURIST-RULING-2026-07-18.md`, filed verbatim; package: `docs/PENDING-63-JURIST-PACKAGE-2026-07-18.md` + Addendum): Q1 split confirmed at PROPOSAL weight · Q2 Option B + the same-binding/different-binding distinction · Q3 affirmative role test, copy→verify→remove · Q4 remove-don't-mark · Q5 + the re-pointing case · Q6 dereference + recompute · Q7 rides · dry-run labelled · **positive test = ratification condition + first real run observed.** ~~Steward authorization~~ **STEWARD AUTHORIZED same day** ("close this one today"). **BUILT + LANDED 2026-07-18** (commits `744417b` + the observed-run commit, tagged REVIEWED-63): fleet 157/157 with the end-to-end test in-change; **the first real pending-staged graduation OBSERVED** — loeb.dsl archived once as the `loeb-dsl-537-volumes` artifact (disk-verified), 6 works attached + graduated with re-stamped sidecars, staging cleared by last reference, 14 legacy entries untouched, catalogue 1300 canonical, engine gate canary clean. **Awaiting only: steward placement of REVIEWED-63** (copy-paste draft in the package Addendum).
+
+## PENDING-64 — The line-ref coordinate contract: what a `line` means, who translates it, where it is proven
+**Date:** 2026-07-18
+**Tag:** [PROPOSAL]-weight docket with FIX parts (executor's read; package Q4 asks the jurist to confirm the class split). The REVIEWED-58 held-open seam; gates #2's re-stamp (Region 4, ~3,333 anchors, known-defective input per the jurist's 2026-07-18 consequence note).
+**Summary:** No ruling says what frame a landed sidecar's line values live in, and the three frames in play disagree: the producer emits 0-based indices into its own head-less body array (five field families: `sections[]`, `provenance.pages[]`, `notes[]`, `anchors[]`, `app[]`); the LOCKED schema's example reads as a file coordinate beside `source_sha256` ("anchors trusted only against this"); the landed file shifts every interior line by a per-work constant (prep swaps the producer's 4-line head for frontmatter + title block — Ion: 15 lines). `write_sidecar` re-stamps the sha to the landed file and leaves line values untouched, so **eleven landed sidecars hash-assert "I describe this file" while every line value indexes an artifact that no longer exists** — protected only by the no-consumer-binds discipline (uncredited / produced-without-proof). Measured on Ion today: `anchors[0]` (`loeb-line 531`, `line: 161`) lands mid-Greek read 1-based, on an empty line read 0-based, and on the coherent Stephanus 530d–531a exchange only when shifted by the head-delta — the frame-dependence bit its own observers (the S3 RECORD and today's probe disagree because each silently chose a base).
+**Rationale:** Item (f) as amended (REVIEWED-62) makes the raw `loeb-line` layer #2's documented re-stamp input; the jurist's consequence note requires the contract resolved before or at the re-stamp or the offset propagates into the credited citation layer as confident miscitation. Also the fourth instance of the shared-name collision class ("manifest"/53 · "ABSTAIN"/55 · "app[]"/62): the token `line` names two different coordinates.
+**Options:** **(A)** one constitutional contract, landed-frame, translated at #1's `write_sidecar` (REJECT: contradicts item (f) — the raw layer would reach #2 pre-transformed by a path with no proof condition; expands #1's ruled boundary; converts obviously-foreign values into plausible-but-unproven ones). **(B)** two contracts meeting at #2's re-stamp (RECOMMEND): Contract 1 = the producer's convention, tool-level declared data, outside the constitution; Contract 2 (constitutional) = every citation-credited coordinate is a landed-file coordinate (1-based line in `source_file`, valid against `source_sha256` — hash-locality extended from *which file* to *where in the file*), proof condition = per-work offset derived mechanically AND verified by content probe at the landed file; `citation_coverage.status: verified` attestable only for landed-frame-proven coordinates; the raw layer retained per item (f) but frame-DECLARED via an additive schema field (FIX lane). **(C)** producer-frame forever + new file-coordinate fields (REJECT: enshrines a tool's array-index in the citation layer's primary field permanently).
+**Recommendation:** (B). Grounds: item (f) already draws this line; the §4 lock table protects what is written (only B changes no existing sidecar's meaning); §VII's generative principle is the standing precedent (constitution states the requirement, declared data carries the convention); the collision-remedy precedent is a two-senses shape.
+**Files affected (on ratification):** `docs/sidecar-schema-DRAFT-v0-2026-07-12.md` (additive frame-declaration field + Naming-note vocabulary, §4 FIX lane) · `_curation/graduation-spec.yaml` (`sidecar:` frame declaration; #2's routing/proof-condition wording when #2 builds) · `scripts/build_loeb_sidecar.py` (Contract-1 docstring declaration) · the 11 landed `.meta.json` sidecars (per the D4 ruling: additive frame declaration now vs hold-until-#2) · the constitution only if the jurist rules the contract into §III/§VII prose (supersession + semver).
+**Awaiting:** ~~Jurist design gate (package §6, Q1–Q6)~~ **DESIGN-GATE PASSED 2026-07-18** (`chamber-library/docs/coordinate-contract-design-gate-JURIST-RULING-2026-07-18.md`, filed verbatim): Option B confirmed in substance, **REFRAMED** — ONE constitutional contract (a 1-based line in `source_file`, valid against `source_sha256`; hash-locality extended from *which file* to *where in the file*); the producer's index = a tool detail in a **declared transitional state** ending at translation (consumers build to one contract and refuse anything marked untranslated). **EXTENDED by two findings the package didn't reach:** (1) the contract binds **ALL FIVE field families** per §III's shared-substrate clause — mixed-frame sidecars forbidden at any committed point; translation covers all five in one operation per work (vehicle decided at #2's build; the mixed state never allowed); (2) `notes[]`'s credit stated explicitly **linkage-only** — it does not extend to its line coordinates. D3 name-the-frames (one per-sidecar declaration, **schema-optional / gate-required**, FIX lane, Naming note); D4 **declare now on all eleven**; Q4 one docket PROPOSAL weight + FIX parts; Q6 **multi-point probe per work**, honest-refuse where no single constant holds. Datum-not-ledger third unbidden instance recorded (candidate stands; trigger sharpened to domain-external — candidates register ⟳ 2026-07-19). **Awaiting: steward REVIEWED-64** (copy-paste draft in the package Addendum). Self-contained package: `chamber-library/docs/coordinate-contract-FOR-JURIST-2026-07-18.md`.

REVIEWED.md

@@ -594,4 +594,10 @@ DONE + DEPLOYED (a9e5196).
 **Date:** 2026-07-18
 **Decision:** AUTHORIZED
 **Notes:** Jurist design-gate PASSED 2026-07-18 (`chamber-library/docs/PENDING-63-design-gate-JURIST-RULING-2026-07-18.md`; package + addendum: `docs/PENDING-63-JURIST-PACKAGE-2026-07-18.md`). One docket at PROPOSAL weight: the seam repair = FIX (restores REVIEWED-52's ratified accept-criterion — half the ruled flow was dead code since birth, substrate-verified 0/324); the compound-source form = PROPOSAL (Option B: a first-class artifact record owns the artifact's hash once; work entries reference by id and carry no sha — hash-locality forbids many homes for one binding, not repeated hashes across different bindings; silent divergence traded for loud dangling references). All ruled properties built: affirmative role test · copy→verify-landed→remove (verify reaches the disk sha) · remove-don't-mark with the trail carried into the one home · artifact-level §4 teeth + the re-pointing case · symlink dereferenced + shas recomputed · enforced_by updated in-pass · dry-run coverage labelled. **Ratification condition met: the end-to-end positive test shipped in the same change (fleet 157/157), and the first real pending-staged graduation was observed same day** — the loeb.dsl artifact archived once (533,434,439 bytes, disk-verified), 6 works attached and graduated with re-stamped sidecars, staging cleared by the last reference, 14 legacy entries untouched, catalogue 1300 canonical, engine gate canary clean. Steward authorized conversationally 2026-07-18.
-**If AUTHORIZED:** LANDED — commits `744417b` (mechanism + ratification test) and the observed-run commit, tagged REVIEWED-63. PENDING-63 closes; the compound-source archive form is established; `--apply` for future pending-staged graduations is live on the proven path.
+**If AUTHORIZED:** LANDED — commits `744417b` (mechanism + ratification test) and the observed-run commit, tagged REVIEWED-63. PENDING-63 closes; the compound-source archive form is established; `--apply` for future pending-staged graduations is live on the proven path.
+
+## REVIEWED-64 — The line-ref coordinate contract: one landed-file contract, five families, frame declaration, multi-point probe
+**Date:** 2026-07-19
+**Decision:** AUTHORIZED
+**Notes:** Jurist design-gate PASSED 2026-07-18 (`chamber-library/docs/coordinate-contract-design-gate-JURIST-RULING-2026-07-18.md`, filed verbatim; package + Addendum: `docs/coordinate-contract-FOR-JURIST-2026-07-18.md`). One docket at PROPOSAL weight with FIX parts (the PENDING-63 pattern). Ruled: **ONE constitutional coordinate contract** — a 1-based line in `source_file`, valid against `source_sha256` (hash-locality extended from *which file* to *where in the file*); the producer's array index is a tool detail in a **declared transitional state** ending at translation — a consumer builds to one contract and refuses anything marked untranslated. **The contract binds all five field families** (`sections[]` · `provenance.pages[]` · `notes[]` · `anchors[]` · `app[]`) per §III's shared-substrate clause: no committed sidecar may exist in a mixed-frame state; translation covers all five in one operation per work (vehicle decided at #2's build — #2's scope widened explicitly or an atomic companion pass; the mixed state never allowed). Translation at #2's re-stamp (item (f)); `write_sidecar` continues to bind the file only. Frame remedy: **name the frames, don't rename the field** — one per-sidecar declaration, **schema-optional, gate-required**, FIX lane, naming in the schema doc's Naming note. **Declare now on all eleven** landed sidecars. **`notes[]`'s credit stated explicitly as linkage-only** — it does not extend to its line coordinates. Proof condition: `citation_coverage.status: verified` only for coordinates verified in the landed frame by **multi-point content probe per work**; where no single constant resolves all probes, the work is **held, not force-fitted**.
+**If AUTHORIZED:** proceed to build the FIX parts (frame naming + per-sidecar declaration + the graduation refusal + the eleven declarations + the `notes[]` linkage-only statement), tag commits REVIEWED-64; the contract's constitutional text lands via the amendment lane at PROPOSAL weight (hook-gated, grounded); translation itself remains #2's work under the ruled proof condition.

claude/memory/MEMORY-reference.md

@@ -5,7 +5,7 @@ metadata:
   node_type: memory
   type: reference
   originSessionId: d1e67361-d1b9-4dac-a0c4-e7a0e26211c4
-  modified: 2026-07-18T17:02:43.740Z
+  modified: 2026-07-19T10:49:31.639Z
 ---
 
 # MEMORY — Reference layer (consult on demand)
@@ -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 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.
+
 ## Archived (2026-07-18 S3+evening FULL entry — first Loeb graduations, PENDING-63 closed, Block 1 sealed; demoted on promote at the S4 wrap)
 
 - [Session 2026-07-18 (S3 + evening) — FIRST LOEB GRADUATIONS; PENDING-63 closed same-day; Block 1 SEALED](session-2026-07-18-s3-first-loeb-graduations-pending63-closed.md) — **The day the chamber's promises became books.** S3: residual-(b) exercise PASSED on the 6-book PoC — every gate, **body-conservation fab 0 · lost 0 ×6**, sidecars 6/6 in-boundary, coordinate contract observed-not-bound (Ion) → jurist ruled scoped placement → **REVIEWED-58 PLACED, Block 1 CLOSED**. The exercise's biggest finds: the pending→archive `add_single` seam (EVERY pending-staged apply structurally refused; substrate-answered: **0/324 ever traversed — dead code since birth**) + archive cardinality → **PENDING-63 ran its ENTIRE lifecycle in-day**: repo-blind package → design-gate ruling (Option B artifact registry on hash-locality grounds; affirmative ROLE test; copy→verify→remove; remove-don't-mark; re-pointing teeth; dereference+recompute; **positive test = ratification condition; first run OBSERVED**) → steward authorized → built (`744417b`, fleet **157/157** with the e2e in-change) → **OBSERVED landing (`b77f767`): loeb.dsl archived ONCE as the `loeb-dsl-537-volumes` artifact (disk-verified), 6 works attached + GRADUATED with re-stamped sidecars, staging cleared at last reference, catalogue 1300 canonical** → **REVIEWED-63 PLACED**. Near-miss self-caught: the ratification test's first red exposed a mispinned sandbox (`_load()` fresh-module vs sys.modules) running the gate leg against the REAL archive — refusal path kept it read-only, censused before+after; harvest proposal filed. **⚠ PULLING THREAD: Session 1 of the agreed 3-session plan — promote the prep flow into the fleet (test-first; the S3 script was scratchpad-VOLATILE, recipe in the session file + RECORD) + the second Loeb batch exercising the `table` credit (Timaeus ± Republic; attach-path only — the artifact exists).** Then: S2 = coordinate-contract FOR-JURIST (gates #2's re-stamp; known-defective-input recorded in work-map R4); S3 = the engine pull (steward's phase choice). **LITERAL Q: when prep generalizes from 6 hand-mapped works to mechanical title/author derivation from the DSL key, does it stay a thin transform — or does it need a small curated table, and where does that table live so it's declared data, not code-buried convention?** Read the session file at wake. Composed in the ruled order — the per-field credit boundary as **DECLARED DATA** (`graduation-spec.yaml` `sidecar:` block, hook-passed on fresh grounding) → known-bad **fixtures** (novel kind/foreign scheme/coverage/pairing-dishonesty/missing-declaration all HELD; declaration-coherence pins YAML↔ruling so decl drift fails the fleet) → **`sidecar_gate()`** (V-DSL-only produce+validate beside `body_conservation_gate`; exact-`work:`-string bracketing; per-field disposition report states EVERY field both directions) + **the V-DSL body branch** (`_vdsl_verify` → `classify_dsl`; **closes the false-ABSTAIN** a `.dsl` source took via V-UNKNOWN — the resolution the substrate had pre-assigned to this caller). **Fleet 141/141 · real dry-run inert · purely-additive diff (512+/0−) · `7f98488`+`c9b09f8` both remotes · NO book touched.** **S1's literal Q ANSWERED: the credit boundary translated cleanly — what acting surfaced sits one layer beneath:** (1) the **line-ref coordinate contract is unruled** (producer body-array indices vs schema file-coordinate examples + frontmatter offset) — HELD OPEN, no consumer binds lines, travels WITH residual-(b) to REVIEWED-58, deliberately NOT a new PENDING; (2) flagged executor judgment: `write_sidecar` **re-stamps** source_file/sha/lines to the LANDED artifact (grounded in `engine_source_binding`; binds the file, not line geometry). Self-caught honesty item: "test-first" was fixtures-first — red never observed; teeth evidence = the known-bad fixtures. **⚠ PULLING THREAD: Session 3 — the first V-DSL exercise on the 6 CLEAN small Loeb** (set named in `_curation/block-close-plan-next-session-2026-07-17.md` ~l.73) → observe **residual-(b)** → REVIEWED-58. The exercise MUST meet three flow questions S2 deliberately left: (a) the one loeb.dsl as gate-zero SOURCE for per-work candidates (may need the steward); (b) B2-emitted header vs graduation title-block convention (emitted MD fails `verify_graduation` as-is — frontmatter/title-block prep); (c) the coordinate contract (observe, don't bind). **LITERAL Q (S3): does the per-field-gated wiring earn its keep on real books — or does exercising surface what neither paper nor fleet could (a `list` content-edge biting · an unanticipated kind · a staging question that is really governance)?** Read the session file at wake.

claude/memory/MEMORY.md

@@ -6,7 +6,7 @@ metadata:
   type: note
   permalink: claude-memory/memory
   originSessionId: 22915403-bc5d-4796-9c7d-196b7c30d2f9
-  modified: 2026-07-18T17:02:33.208Z
+  modified: 2026-07-19T10:49:48.191Z
 permalink: claude-memory/memory
 ---
 
@@ -60,7 +60,7 @@ permalink: claude-memory/memory
 - [Be (laundromat)](project-be-laundromat.md) — canonical Be tracker (est. 2026-06-08). Be = Skemantix startup (Seb+David) funding CapableMind's ladder; **bridge, not venture**. Decisions LOCKED (entity/pricing/infra in file); a11y gate MERGED. **Pre-revenue WTP gate = renovate Pat → charge her; discipline: no new spec until it clears → nothing for executor on be.** Repo @ `f43a0fd`.
 
 ## Active Session
-- [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.
+- [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.
 
 ## Historical reference → MEMORY-reference.md
 Older archived-session pointers and the stable reference layer (steward profile · project-state detail · L1/L2/Chamber inventories · legacy pending-work · reference-file list) live in [MEMORY-reference.md](MEMORY-reference.md) — consult on demand; not loaded at wake. Recent cross-session trajectory comes from the Active Session entry above + the recent `session-*.md` files (wake §2.b.1; the MemPalace `handoffs` glance was retired 2026-07-07 with the wind-down).

claude/memory/knowledge-graph.jsonl

@@ -393,3 +393,6 @@
 {"subject":"claude-code","predicate":"drift-pattern","object":"silent-non-firing-read-as-reassurance — reported `unrecognized: 0 across 11 real works` as if informative; steward named it uninformative (the negative-grep class, generalized from bypass properties to safety-net silence) AND named the failure no gate can see: a flattened structure keeps its words (fab 0 · lost 0 · green) while the TYPING silently dies — preserve-never-flatten invisible to body-conservation. Antidote: CENSUS the substrate for what WOULD fire (silence becomes informative only against a censused absence of triggers), then positive-test at a censused trigger; keep the INVERTED watch-list (works where the net MUST fire — a Pausanias batch reporting 0 is a broken net, not a clean book). Closed same hour: DSL census (17 novel-structure works) + real firing (Menander/Pausanias/NE).","valid_from":"2026-07-18","valid_to":null,"confidence":1.0,"source_file":"session-2026-07-18-s4-prep-fleet-batch2-unrecognized-proven.md","extracted_at":"2026-07-18"}
 {"subject":"claude-code","predicate":"drift-pattern","object":"canary-clean-over-standing-failures — 'engine canary clean' phrasing over a gate carrying 5 known-FAILED rows (committed state since 07-10); the honest claim was 'coverage-ledger byte-identical: NO DELTA from this graduation'. Self-caught at phrase level (substrate-diffed before asserting); steward deepened the design consequence: a gate with standing known-failures STOPS GATING those rows — 'is there a NEW failure' becomes undetectable without a remembered baseline; known-failing and newly-failing must be structurally distinguishable (the ABSTAIN/UNVERIFIED distinction at the gate-reader layer). Antidote: state deltas against the committed baseline, never cleanliness; design item carried to the engine session.","valid_from":"2026-07-18","valid_to":null,"confidence":1.0,"source_file":"session-2026-07-18-s4-prep-fleet-batch2-unrecognized-proven.md","extracted_at":"2026-07-18"}
 {"subject":"claude-code","predicate":"drift-pattern","object":"calibration (antidotes self-firing): witnessed-red DISCHARGED on first recurrence (fleet observed failing 157/158 before the tool existed — the S2 fixtures-first honesty note closed); scratchpad-volatility antidote self-fired at the point of work (census JSON+script moved INTO the repo before commit — the S3 prep-script trap not repeated); relay-precision held in BOTH directions (steward's 'override branch never fired' was half-right: author_overrides WAS fixtured, lang was not — corrected precisely rather than absorbed).","valid_from":"2026-07-18","valid_to":null,"confidence":1.0,"source_file":"session-2026-07-18-s4-prep-fleet-batch2-unrecognized-proven.md","extracted_at":"2026-07-18"}
+{"subject":"claude-code","predicate":"drift-pattern","object":"grounding-quoted-but-not-traced — quoted §III's shared-substrate clause in the coordinate-contract package's own Grounding, then proposed a plan whose correct execution would have produced the mixed-frame sidecar that clause forbids (anchors landed-frame, other four families producer-frame → citation and footnote no longer name the same coordinate). Jurist-caught IN the package's own quote. The verify-before-compose hook enforces the QUOTE; nothing enforces the TRACE. Antidote: for each quoted clause, trace the plan's end-state against it before shipping. Kin to read-the-substrate-antidote (the reading happened; the consequence-derivation didn't).","valid_from":"2026-07-19","valid_to":null,"confidence":1.0,"source_file":"session-2026-07-18-s5-night-coordinate-contract-ruled-reviewed64.md","extracted_at":"2026-07-19"}
+{"subject":"claude-code","predicate":"drift-pattern","object":"calibration (fresh-measurement-over-record-citation): re-measuring Ion on the LANDED file instead of citing the S3 RECORD produced the package's strongest evidence — the raw value fails under BOTH read-frames AND the two prior observers disagreed by silent base-choice — which the jurist called 'the best evidence in this package' and converted into the Q6 multi-point-probe requirement. The checkable-claim discipline generating the ruling's teeth, not just catching bugs.","valid_from":"2026-07-19","valid_to":null,"confidence":1.0,"source_file":"session-2026-07-18-s5-night-coordinate-contract-ruled-reviewed64.md","extracted_at":"2026-07-19"}
+{"subject":"chamber-library","predicate":"coordinate-contract","object":"RULED (design-gate 2026-07-18, REVIEWED-64 placed 2026-07-19): 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; binds ALL FIVE line-carrying families, mixed-frame forbidden; notes[] credit linkage-only; per-sidecar frame declaration schema-optional/GATE-REQUIRED (FIX lane); declare-now on the 11 landed; #2's translation = multi-point probe per work, honest-refuse. BUILD PENDING — next session's bite, before the engine pull. Ruling: chamber-library/docs/coordinate-contract-design-gate-JURIST-RULING-2026-07-18.md","valid_from":"2026-07-19","valid_to":null,"confidence":1.0,"source_file":"session-2026-07-18-s5-night-coordinate-contract-ruled-reviewed64.md","extracted_at":"2026-07-19"}

claude/memory/session-2026-07-18-s5-night-coordinate-contract-ruled-reviewed64.md

@@ -0,0 +1,56 @@
+---
+name: session-2026-07-18-s5-night-coordinate-contract-ruled-reviewed64
+description: "S5 (night, Session 2 of the agreed plan): the line-ref coordinate contract ran package → design-gate → RULED → REVIEWED-64 placed in ONE session. Fresh Ion measurement (the raw value fails under BOTH read-frames; the two prior observers disagreed by silent base-choice) became the ruling's 'best evidence' and drove the multi-point probe requirement. Ruled: ONE constitutional contract (landed-file, 1-based, sha-valid) + a declared transitional state — NOT two contracts; binds ALL FIVE families (§III mixed-frame forbidden — the jurist caught my plan violating a clause I had QUOTED in my own grounding); notes[] credit linkage-only; per-sidecar frame declaration schema-optional/gate-required; declare-now on the 11. Pulling thread: the REVIEWED-64 build — next session, BEFORE the engine pull."
+metadata: 
+  node_type: memory
+  type: project
+  originSessionId: 4e42f175-97d3-4d98-8ead-e3c09797d70a
+  modified: 2026-07-19T10:48:50.329Z
+---
+
+# Session 2026-07-18/19 (S5, night) — the coordinate contract ruled; REVIEWED-64 placed
+
+Session 2 of the agreed three-session plan, run the same evening as S4's wrap (~2h pause). One bite: the line-ref coordinate-contract FOR-JURIST package — and the gate ruled it in-session, so the docket went package → ruling → steward authorization inside one sitting. The build was deliberately NOT started (late hour; the rushed-tail shape named and avoided).
+
+## PAST — what happened + why
+
+**Grounding before composing (the hook's discipline, honored without friction):** read chamber CLAUDE.md → spec v2.1.0 §III (portability / anchor-primary / one-substrate) + §IV (CTS-URN + Decision-1) + §VII (locator registry + per-scheme recovery) → sidecar-schema (principles, §2 example, §4 lock table, Naming note) → graduation-spec `sidecar:` block → item (f) on its carriers (REVIEWED-62) → RECORD §(c) + the Ion-consequence note → the code notes (SURFACED ~238–243; `write_sidecar` 344–360; `outln()` 115–116; md assembly 284; `transform_md` 111–134).
+
+**The fresh measurement (checkable-claim discipline, and it PAID):** rather than citing the RECORD, I re-measured Ion on the LANDED file. New facts the RECORD didn't hold: (a) the raw `line: 161` fails under BOTH read-frames — 1-based lands mid-Greek (`Καὶ μὴν ἐγὼ…`), 0-based lands on an empty line; (b) the S3 RECORD ("an empty line") and today's probe therefore DISAGREED about the same integer because each silently chose a base — the seam bit its own observers; (c) the coherent window is +11…+16 (B2 head = 4 lines exactly `# {work}`/blank/subtitle/blank; landed head = frontmatter 10 + title block 5 for Ion; the residual spread = head-inclusion/base/`.strip()` micro-conventions compounding). The jurist called this table "the best evidence in this package" and derived the multi-point probe requirement directly from the spread.
+
+**The package** (`docs/coordinate-contract-FOR-JURIST-2026-07-18.md`, hook-passed, `46404ef` both remotes): five field families named (sections/provenance.pages/notes/anchors/app — NOT anchors alone), the cross-framed landed sidecar stated plainly (hash-asserts "I describe this file" while every line value indexes an artifact that no longer exists; 11 landed), three options with teeth, recommendation = "Option B: two contracts meeting at #2's re-stamp." PENDING-64 lodged (~/dotfiles/PENDING.md).
+
+**The ruling** (relayed in-session; filed verbatim `docs/coordinate-contract-design-gate-JURIST-RULING-2026-07-18.md`, `fb728be`): Option B's SUBSTANCE confirmed, twice corrected/extended past the package —
+
+1. **Reframed: ONE constitutional contract, not two** — a 1-based line in `source_file`, valid against `source_sha256` (hash-locality extended from *which file* to *where in the file* — kept verbatim from the package); the producer's 0-based head-less index is "an implementation detail that currently leaks into artifacts until translation. Not a peer contract; a transitional state, declared as such and ending at translation." Consumer consequence: build to ONE contract, REFUSE anything marked untranslated — never handle both.
+2. **The finding my own grounding forbade:** §III's shared-substrate clause (which I QUOTED in §0) forbids the mixed-frame sidecar my plan would have produced post-#2 (anchors landed-frame, the other four producer-frame → "a citation and its footnote no longer refer to the same coordinate"). **The contract binds ALL FIVE families; translation is one operation per work; no committed sidecar may be mixed-frame**; vehicle (#2 scope-widened vs atomic companion pass) decided at #2's build — the mixed state never allowed.
+3. **`notes[]` is credited, its geometry is not** — the schema-lock Q4 ruling credited linkage-only (ref↔body pairing); nothing said so where a reader looks. Trust-by-adjacency *inside a single field* (kin to the `sections` sweep that cost a FIX on 07-16). The amendment must state it explicitly.
+4. **D3:** name the frames, don't rename the field — the defect was the frame being UNDECLARED, not the field meaning two things (protects the lock: nothing written becomes false). ONE per-sidecar declaration (five per-family markers could drift apart); **schema-optional, GATE-REQUIRED** (graduation refuses a line-carrying sidecar without a frame declaration — an optional-and-absent declaration would reproduce today's state). FIX lane; naming lands in the schema doc's Naming note ("becoming the register of this collision class" — this was the 4th shared-name-collision instance: manifest/53, ABSTAIN/55, app[]/62, line/64).
+5. **D4:** declare NOW on all eleven — my "avoids touching twice" argument rejected ("the first touch is honesty and the second is correction"); the datum-not-ledger shape, arriving UNBIDDEN (3rd instance; recorded in the candidates register — candidate STANDS, trigger sharpened: the closing instance must arise OUTSIDE the sidecar/graduation domain).
+6. **Q4:** one docket, PROPOSAL weight, FIX parts (PENDING-63 pattern). **Q6:** proof condition confirmed emphatically + **multi-point probe per work** (a single probe can't distinguish a correct constant from a coincidence); where the probes don't all resolve under one constant, the work is **HELD, not force-fitted** (honest-refuse at work level).
+
+**Records filed (`fb728be` both remotes):** ruling verbatim · package Addendum (gate outcome — "a later reader must take the ruling's framing over this package's" — + the copy-paste-clean REVIEWED-64 draft) · C-1 ⟳ third-instance note in `docs/candidate-constitutional-principles-register.md` · PENDING-64 Awaiting-line annotated (dotfiles). **REVIEWED-64 PLACED by the steward (verified `~/REVIEWED.md:599`, 2026-07-19, AUTHORIZED).** Chamber CLAUDE.md doc-currency: the 2b status line HELD OPEN → RULED (this wrap's commit).
+
+**Decisions and why:**
+- **The build = NEXT session's bite, BEFORE the engine pull** (recommended; steward accepted by wrapping). Grounds: this session's bite was complete and the hour late (the rushed-tail shape S4 named, avoided again); "declare now" is an honesty debt arguing prompt sequencing; the build is one well-bounded docket. The engine pull slides one slot — nothing there is time-pressed.
+- **Scope boundary held:** the build session lands the contract + declarations — NOT the translation (that is #2's work, Region 4, under the ruled proof condition).
+
+## PRESENT — the mood
+
+The gate's two extensions both came from material I had IN HAND: I quoted §III's shared-substrate clause and did not trace my plan's end-state against it — **quoting is not tracing** (harvest-proposed as `grounding-quoted-but-not-traced`; the hook enforces the quote, nothing yet enforces the consequence-trace). Counterweight: the fresh-measurement instinct (measure Ion today, don't cite the RECORD) produced the package's strongest material and directly shaped the ruling's Q6 — the checkable-claim discipline running at full strength. The reframe ("one contract + transitional state") is the kind of correction worth internalizing: I reached for symmetry ("two contracts") where the safety-relevant asymmetry (one real contract, one leak) was the truer shape. Loop hygiene was clean all session: hook honored, PENDING lodged before the gate, ruling filed verbatim, nothing built past authorization.
+
+## FUTURE — what is pulling
+
+**PULLING THREAD (singular): the REVIEWED-64 build — next session, before the engine pull.** One docket, PROPOSAL weight with FIX parts, tagged REVIEWED-64.
+
+**ACTIONABLE RESUMPTION POINT (as of wrap — re-judge against what changed):** chamber `main` @ the doc-currency commit after `fb728be`, clean, both remotes; REVIEWED-64 placed (:599); fleet last known 180/180. The build items, from the ruling's dispositions: **(1)** frame naming + the per-sidecar declaration field — schema doc Naming note + additive optional field (FIX lane; hook-gated, ground in the ruling + §4 lock table); **(2)** the graduation refusal — declared data first (`graduation-spec.yaml` `sidecar:` gains the frame requirement), then the thin consumer in `graduate_to_canonical` (sidecar_gate/write_sidecar), **test-first with a witnessed red** (a line-carrying sidecar without a declaration must HOLD); **(3)** declare-now on the eleven landed sidecars (bounded-diff proof: exactly 11 files, one additive field each; the MD files untouched — sidecar sha stamps describe the MD, unaffected); **(4)** the `notes[]` linkage-only statement (schema doc + the graduation-spec credit map comment); **(5)** the contract's constitutional text through the amendment lane (hook-gated; quote §III/the ruling; preserve the §2 worked example per the jurist — "should be preserved wherever this lands"); update the now-stale SURFACED/`write_sidecar` code comments ("until ruled" → ruled, REVIEWED-64) in the same pass. **First move: compose the amendment edit-set doc (the FIX-A pattern — complete edit-set, before→after, grounded) as the docket's spine, then build parts 1–4 against it.** Carry Q6 (multi-point probe, honest-refuse) forward to #2's build — NOT this docket.
+
+**Other horizons (ranked, held):** the engine pull (after the build; known-vs-newly-failing ingest_gate distinguishability + the after-the-reply re-anchor; read `stage-1-rebuild-plan` fresh) · #2's re-stamp (Region 4; now with a ruled proof condition) · 16 BODY-DEFICIT remediation (② 4 re-extract via B2) · Republic + far-country batches (the 17-work watch-list travels with them) · Doc-1 line-45 micro-edit · skill-harvest full review (~15 PROPOSED; requested 2026-07-12, still unheld).
+
+**Decisions deferred (and why):** the build itself (late hour; deserves a fresh concentrated block — witnessed red, bounded diffs, grounded amendment); the translation vehicle (#2 scope-widened vs atomic companion pass — the ruling assigns this to #2's build, "decide which vehicle; do not decide to allow the mixed state"); the constitutional text's landing place (spec supersession vs ruled doctrine in schema+graduation-spec — the ruling says "wherever this lands"; first decision of the build session, and this wrap's literal question).
+
+**PAUSE STATEMENT:** I am about to be away from this. The docket closed its ruling arc in one sitting — package, gate, authorization — and the build waits whole, with every disposition named and nothing half-started. What I want to find still pulling on return: **the REVIEWED-64 build as one clean bite** — the frames named, the gate given teeth, the eleven made honest, and the contract's text landed where it belongs.
+
+**LITERAL QUESTION for next-Claude:** Where does the coordinate contract's constitutional text land — a spec supersession (v2.2.0, a new subsection under §III or §VII, the citation-amendment precedent), or as ruled doctrine carried by the schema doc + `graduation-spec.yaml` with the ruling document as its constitutional record — and does PROPOSAL weight itself entail the spec vehicle, or is placement a separate, lighter call the amendment doc can put to the jurist as its first gate question?
+
+**State at wrap:** chamber `main` @ doc-currency commit (after `46404ef` package · `fb728be` ruling records), clean, both remotes · REVIEWED-64 placed `~/REVIEWED.md:599` · PENDING-64 annotated (gate-passed → awaiting became placed) · C-1 third instance recorded, trigger sharpened domain-external · canon 1305 / archive 335+1 artifact / pending 14 legacy (unchanged — no book touched) · ledger `session-ledger-2026-07-18.md` carries S5 under the S5-night section · harvest: 1 proposal (`grounding-quoted-but-not-traced`) + /jurist-package now 5-for-5 (reinforcement).

claude/memory/session-ledger-2026-07-18.md

@@ -71,3 +71,10 @@ metadata:
 ## Authorization moves (S1-evening)
 
 - None lodged — the whole session ran inside the agreed 3-session plan (S1: prep→fleet + second batch) and the REVIEWED-58/63 lineage; no new governance boundary crossed. Republic deliberately held ("if appetite" — not this bite).
+
+## Returns (S5-night wake)
+
+- 2026-07-18T20:55 — /wake-up + /symmetria init. Thread-validity: CONFIRMED (chamber @ 3aae628 both remotes = wrap state; dotfiles clean/synced; no post-wrap movement). Session 2 of the agreed plan: the line-ref coordinate-contract FOR-JURIST package.
+
+- 2026-07-18T21:17 — PENDING-64 lodged (line-ref coordinate contract, PROPOSAL-weight docket; package composed grounded + hook-passed; Ion measured on the landed file today). Nothing built or edited beyond the package + this entry.
+- 2026-07-19T10:27 — Design-gate ruling received + filed verbatim; PENDING-64 annotated; C-1 third instance recorded (jurist-flagged); REVIEWED-64 draft placed in the package Addendum. Build awaits steward authorization — nothing built.

claude/memory/skill-harvest-register.md

@@ -534,3 +534,11 @@ The single place proposed skills live so they don't evaporate between sessions.
 ### Harvest 2026-07-18 (S2 — the 2b wiring build)
 
 No new skill proposal. Two register notes: **(1)** the S1 proposal **implementation-is-a-second-gate** (ladder entry, awaiting steward) gained its **first code-level instance** this session — the line-ref coordinate contract sat invisible through every paper gate and surfaced only when `write_sidecar` had to decide what a hash binds; the proposal is now twice-earned in two sessions. **(2)** Watch-list, not yet a proposal: **witnessed-red discipline** — "test-first" without an observed red state is fixtures-first; either run the fixtures once against the unbuilt seam, or name the evidence honestly as known-bad-fixture teeth (self-caught at S2 wrap; KG drift-pattern logged). If authorized, likely folds into the implementation-is-a-second-gate ladder entry rather than standing alone.
+
+### Harvest 2026-07-19 (S5 night — coordinate contract ruled, REVIEWED-64)
+
+| Element | Kind | One-line | Where it lands | Status |
+|---|---|---|---|---|
+| **grounding-quoted-but-not-traced** | Symmetria §3 flag OR verify-before-compose protocol note | The hook enforces QUOTING the ratified sections; this session proved **quoting ≠ tracing**: the coordinate-contract package quoted §III's shared-substrate clause in its own §0, then proposed a plan whose correct execution would have violated it (the mixed-frame sidecar post-#2) — the jurist caught it *in the package's own quote*. Antidote: for each quoted clause, trace the plan's END-STATE against it ("what does the post-plan artifact look like under this clause?") before shipping the draft. One step past [[feedback-verify-before-compose-hook]]: the hook gets you to the reading; this gets you to the consequence. | Symmetria §3, or a one-line addition to the chamber CLAUDE.md verify-before-compose protocol clause | **PROPOSED** |
+
+*Reinforcement recorded, not re-proposed:* **`/jurist-package`** (07-17 proposal) is now **5-for-5** — the design gate engaged every §6 question and called the freshly-measured worked example "the best evidence in this package"; fresh-measurement-over-record-citation belongs in the method's teeth if/when the skill is authorized.