session 2026-07-18 S4: prep→fleet + batch 2 graduated (table credit real); unrecognized census+positive-test; S4 session file + 3 KG lines + 1 harvest proposal

claude/memory/MEMORY.md

@@ -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 (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.
+- [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.
 
 ## 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).