session 2026-07-13 (afternoon): 18 body-deficit cause-analysed → 3 remedy tracks; REORDER?→0; PENDING-57 CLOSED
This commit is contained in:
@@ -1500,3 +1500,5 @@ Disposition (verbatim capture + executor action-list: `chamber-library/docs/libr
|
||||
- **Condition 2 (43-book census gap) — CONFIRMED:** census = V-DSL 952 · V-TEXT 239 · V-SCAN 50 · V-SUSPECT 29 · V-NONE 14 = 1,284; the 43 = V-SUSPECT+V-NONE = the **fenced-out** tier (no confirmed source) → correctly EXCLUDED from the conservation sweep (can't re-verify a book with no source). Not a gap; the fence working.
|
||||
- Brief updated (§3.5 loss teeth + §6 census). Change-class PROPOSAL confirmed (distinct from REVIEWED-55's refusal-only-FIX: a FLAG/unresolved-REVIEW has no already-trusted fallback to canon).
|
||||
**Awaiting:** jurist confirmation the two conditions are closed (+ his call on loss auto-PASS vs REVIEW-routing for the masked-vocab edge) → steward ratification (REVIEWED-57) → land by supersession into `graduation-spec.yaml` + `verify_graduation.py`.
|
||||
|
||||
**CLOSED 2026-07-13 (REVIEWED-57 AUTHORIZED — fully ratified across three jurist rounds).** Gate WIRED into graduation as its own source-in-hand step `body_conservation_gate()` (`cdb3454`). §6 retroactive sweep RUN over all 952 Loeb → the corpus-health map (d9f6880/9afb0cf). Follow-on same day: the 18 body-deficit **cause-analysed** by reading the missing spans → three remedy tracks (re-match 8 / re-extract 4 / re-verify-and-reconvert 12); a wrong-match-by-fabrication classifier rule + the 2 REORDER? books resolved (both wrong/partial-key, CLEAN on re-match) → REORDER? dissolved to 0 (eb21eca/836b665/c54edbb). Nothing further awaited on PENDING-57. The reprocess itself (matcher fix → the 2b sidecar-wiring amendment gated on the steward's Loeb-first-vs-full-corpus call → B2 ②+③) is downstream work tracked in the session files + `chamber-library/docs/chamber-program-open-work.md`, not here.
|
||||
|
||||
@@ -20,6 +20,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-13 afternoon — the 18 body-deficit cause-analysed → 3 remedy tracks; REORDER?→0; demoted on promote)
|
||||
- [Session 2026-07-13 — keystone LANDED + wired + Loeb corpus-health map](session-2026-07-13-keystone-landed-loeb-health-map.md) — Keystone (PENDING-57) **wired into graduation** (`cdb3454`; `body_conservation_gate` its own source-in-hand step, NOT collect_checks) + its **§6 sweep run over all 952 Loeb** → the corpus-health **map**: 802 CLEAN · 126 apparatus-shaped · 18 body-deficit · 2 REORDER? · 4 MATCH-SUSPECT (`_curation/loeb-body-conservation-map-2026-07-13.tsv`; d9f6880/9afb0cf). Cross-extractor **drift-tolerance = two-sided boilerplate accounting**; the 126 floor = **apparatus criticus** the old extractor flattened (steward's app[] prediction) → apparatus-SHAPED-not-accounted, split by MAGNITUDE, **gate apparatus-credit FACT-GATED**; a **matcher bug** surfaced by restoring the REORDER? number → MATCH-SUSPECT. 3 commits pushed both remotes; 119/119; **PENDING-57 CLOSED**. **⚠ PULLING THREAD: the B2 corpus reprocess the map sizes** — first station the **2b sidecar-wiring amendment** (steward's Loeb-first-vs-full-corpus call) → populates app[] + reconverts the 126 + feeds the 18-book investigation. **Steward pref: shorter, very concentrated sessions.** Read the session file + the map + `docs/chamber-program-open-work.md` at wake. *[Superseded 2026-07-13 afternoon: opened the 18 → map now carries CAUSE, split into 3 remedy tracks (re-match 8 / re-extract 4 / re-verify-and-reconvert 12); the 2 REORDER? + 2 of the wrong-match books reclassified to MATCH-SUSPECT; REORDER? dissolved to 0 (both occupants were wrong/partial-key artifacts, CLEAN on re-match); see the 07-13 afternoon cause-analysis session. New pulling thread: the matcher key-selection fix.]*
|
||||
|
||||
## Archived (2026-07-13 — keystone LANDED + wired + Loeb corpus-health map; demoted on promote)
|
||||
- [Session 2026-07-12 evening — schema LOCKED · B2 fleet-v1 · PENDING-57 keystone RATIFIED](session-2026-07-12-evening-schema-lock-b2-fleet-keystone-ratified.md) — Continuation of the A1-to-docling day. **Sidecar schema → LOCKED** (3 jurist rounds; additive-only: new fields/`app[]`-kinds=FIX, change/remove-field=PROPOSAL; REVIEWED-56 filed). **B2 → fleet-v1** (`build_loeb_sidecar.py`, the preserve-aware Loeb extractor — DSL colors=render-cues NOT semantics; editorial-`<word>`-insertions the legacy strip_tags DELETES; genre-heterogeneous footnote pairing prose96/verse66/frag48 honest-flagged; generic flag-and-hold net; in test_tools, fleet→111). **THE KEYSTONE — PENDING-57 verbatim gate FULLY RATIFIED** (3 jurist rounds; V-DSL demonstrated after the naive-reuse-of-the-V-TEXT-check FALSE-FLAGGED a clean book → reflow-tolerant multiset; loss-teeth built; retroactive sweep folded; 43-book census=fenced-out tier; **REVIEWED-57 filed**). Retroactive probe: 7/9 graduated Loeb PASS, 2 false-positive stopword-drift → **the sweep needs cross-extractor drift-tolerance before the 952-run**. **Doc-currency pass** + institutionalized a standing **'Doc-currency on wrap'** protocol into BOTH chamber+studium CLAUDE.md. **All committed+pushed** (chamber f6d9010/1f9867c, studium 7e8e322, dotfiles d9692f7, CM-AI 5b6068c; dotfiles-Gitea-mirror lagging, non-blocking). **⚠ PULLING THREAD: LAND THE KEYSTONE next session** — wire verify_body_conservation into verify_graduation + graduation-spec (source-access + tier-dispatch + the drift-tolerance) → run the diagnostic sweep for the corpus-health map. Read the session file + `docs/chamber-program-open-work.md` at wake. *[Superseded 2026-07-13: keystone LANDED+wired (cdb3454), §6 sweep RUN over 952 → the corpus-health map (d9f6880/9afb0cf); PENDING-57 CLOSED; see the 07-13 session.]*
|
||||
|
||||
|
||||
@@ -57,7 +57,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-13 — keystone LANDED + wired + Loeb corpus-health map](session-2026-07-13-keystone-landed-loeb-health-map.md) — Keystone (PENDING-57) **wired into graduation** (`cdb3454`; `body_conservation_gate` its own source-in-hand step, NOT collect_checks) + its **§6 sweep run over all 952 Loeb** → the corpus-health **map**: 802 CLEAN · 126 apparatus-shaped · 18 body-deficit · 2 REORDER? · 4 MATCH-SUSPECT (`_curation/loeb-body-conservation-map-2026-07-13.tsv`; d9f6880/9afb0cf). Cross-extractor **drift-tolerance = two-sided boilerplate accounting**; the 126 floor = **apparatus criticus** the old extractor flattened (steward's app[] prediction) → apparatus-SHAPED-not-accounted, split by MAGNITUDE, **gate apparatus-credit FACT-GATED**; a **matcher bug** surfaced by restoring the REORDER? number → MATCH-SUSPECT. 3 commits pushed both remotes; 119/119; **PENDING-57 CLOSED**. **⚠ PULLING THREAD: the B2 corpus reprocess the map sizes** — first station the **2b sidecar-wiring amendment** (steward's Loeb-first-vs-full-corpus call) → populates app[] + reconverts the 126 + feeds the 18-book investigation. **Steward pref: shorter, very concentrated sessions.** Read the session file + the map + `docs/chamber-program-open-work.md` at wake.
|
||||
- [Session 2026-07-13 (afternoon) — the 18 body-deficit cause-analysed → 3 remedy tracks; REORDER?→0](session-2026-07-13-afternoon-18-body-deficit-cause-analysed.md) — Opened the 18 BODY-DEFICIT Loeb by **READING the missing spans**: the "same apparatus story, just larger" hypothesis **REFUTED** → THREE mechanisms, three remedies (**① re-match 8 · ② re-extract 4 · ③ re-verify-and-reconvert 12**). Folded cause into the map via a **wrong-match-by-fabrication** classifier rule (`m_fab>5% cand → MATCH-SUSPECT`, checked BEFORE arrangement; bounded-change proven). **Read + resolved the 2 REORDER? books** — augustine (PARTIAL key: full 'Confessions' vs matched 'Books 1–8') + philo-on-abraham (WRONG sibling: 'On Abraham' vs 'On the Migration of…'), both **fab=0/lost=0 CLEAN on re-match** → **REORDER? dissolved to 0** (both were wrong/partial-key artifacts; detector kept — absence-here≠cannot-exist). Map now: 802 CLEAN · 126 APPARATUS-SHAPED · 16 BODY-DEFICIT · 8 MATCH-SUSPECT · 0 REORDER?. 3 commits both remotes (eb21eca/836b665/c54edbb); 119/119; **PENDING-57 fully CLOSED**. **⚠ PULLING THREAD: the matcher key-selection fix** (near-dup/split/part-vs-whole keys) — resolves all 8 MATCH-SUSPECT, finalizes the reprocess target set BEFORE B2; ready now, FIX-class; 2 of 8 (augustine/philo) one re-match from CLEAN. Behind it: the steward's **Loeb-first-vs-full-corpus scoping call** → the 2b amendment → the B2 reprocess proper (②+③, blocked on the amendment). **Steward pref: shorter, very concentrated sessions.** Read the session file + `_curation/loeb-body-deficit-cause-analysis-2026-07-13.md` + the map 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).
|
||||
|
||||
@@ -360,3 +360,5 @@
|
||||
{"subject": "claude-code", "predicate": "drift-pattern", "object": "withheld-a-reportable-number-behind-a-soft-label (labeled REORDER? 'magnitude unresolved' when only the CAUSE was unresolved — the position-blind multiset deficit was in the data; steward: restore it). Restoring the number EXPOSED a matcher bug the soft label was hiding. A checkable claim is a defect-detector; a soft classification can be true-shaped and wrong.", "valid_from": "2026-07-13", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-07-13-keystone-landed-loeb-health-map.md", "extracted_at": "2026-07-13"}
|
||||
{"subject": "claude-code", "predicate": "drift-pattern", "object": "reordering-panic-from-a-weak-test (read '50% of the missing Greek appears elsewhere' as reordering; it was common-Greek-function-words trivially recurring as set-members — the position-BLIND multiset COUNT refuted it, ratio~1.0=real deficit). Verify with the position-independent measure before claiming reordering. Kin to a-check-proven-for-one-case-not-another (proved _uncovered_runs on prose, not verse).", "valid_from": "2026-07-13", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-07-13-keystone-landed-loeb-health-map.md", "extracted_at": "2026-07-13"}
|
||||
{"subject": "PENDING-57", "predicate": "status", "object": "CLOSED 2026-07-13 (REVIEWED-57) — keystone wired into graduation (cdb3454) + §6 retroactive sweep run over 952 Loeb → corpus-health map (802 CLEAN/126 apparatus-shaped/18 body-deficit/2 REORDER?/4 MATCH-SUSPECT); chamber d9f6880/9afb0cf", "valid_from": "2026-07-13", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-07-13-keystone-landed-loeb-health-map.md", "extracted_at": "2026-07-13"}
|
||||
{"subject": "claude-code", "predicate": "drift-pattern", "object": "inherited-marker-read-as-current-state RECURRED at wake — briefing said REVIEWED-55 placement still owed; it was placed 2026-07-12 (REVIEWED.md:490). Verify a governance item state against REVIEWED/PENDING before relaying; records drift in BOTH directions (a stale 'owed' describing done governance). Steward-caught.", "valid_from": "2026-07-13", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-07-13-afternoon-18-body-deficit-cause-analysed.md", "extracted_at": "2026-07-13"}
|
||||
{"subject": "claude-code", "predicate": "drift-pattern", "object": "counted-the-bundled-representation-as-items — stated the remedy track as 10 (table ROWS) when it was 12 BOOKS; the final row bundled the 3 Aeschylus plays. Count items, not their grouped display rows. Kin to census-through-a-pattern; steward-caught by the arithmetic (8+4+12=24=16+8).", "valid_from": "2026-07-13", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-07-13-afternoon-18-body-deficit-cause-analysed.md", "extracted_at": "2026-07-13"}
|
||||
|
||||
@@ -0,0 +1,54 @@
|
||||
---
|
||||
name: Session 2026-07-13 (afternoon) — the 18 BODY-DEFICIT cause-analysed → 3 remedy tracks; REORDER? dissolved to 0
|
||||
description: "Answered the wrap's literal question by READING the actual missing spans: the 18 BODY-DEFICIT Loeb are NOT one apparatus story but THREE mechanisms → three remedies (re-match 8 / re-extract 4 / re-verify-and-reconvert 12). Folded cause into the map via a wrong-match-by-fabrication classifier rule; read + resolved the 2 REORDER? books (both wrong/partial key, fab=0/lost=0 CLEAN on re-match) → REORDER? has 0 genuine members corpus-wide. 3 commits (eb21eca/836b665/c54edbb) both remotes; fleet 119/119; PENDING-57 fully closed. Pulling thread: the matcher key-selection fix (resolves all 8 MATCH-SUSPECT, finalizes the reprocess target set before B2) — next session's concentrated bite. The B2 reprocess proper sits behind the steward's Loeb-first-vs-full-corpus scoping call → the 2b sidecar-wiring amendment."
|
||||
metadata:
|
||||
node_type: memory
|
||||
type: project
|
||||
originSessionId: 91c1a97c-0d2b-4f5a-aa58-9e1f26eec531
|
||||
---
|
||||
|
||||
# Session 2026-07-13 (afternoon) — the 18 body-deficit, read and split by cause
|
||||
|
||||
Woke into the keystone-landed state; pulling thread = "the B2 reprocess the map now sizes." The steward chose my lean (open the 18 body-deficit books). Ended with the corpus-health map carrying CAUSE, not just magnitude — the reprocess honestly sized as three remedy tracks, and the REORDER? bucket dissolved to zero. Three commits, both remotes, 119/119, PENDING-57 truly closed.
|
||||
|
||||
## PAST — what we did + why
|
||||
|
||||
**1. Answered the wrap's literal question by READING the missing spans (probe, read-only).** Method: full-census script-mix of the missing multiset (greek=source-original vs latin-script=translation/apparatus) + the largest uncovered runs read as actual text, per book. **Answer: the "same apparatus story, just larger" hypothesis is REFUTED.** The 18 are three phenomena, three remedies:
|
||||
- **① wrong/partial match (2 → MATCH-SUSPECT: re-match)** — plutarch-moralia-other-fragments (true key "Other Fragments" 13891≈cand; matcher grabbed "…Other Named Works" 59997) + suetonius (candidate is the Rhetoricians text, matched to the Grammarians sibling key). `m_fab>0` = the extractor can't add content, so the reference is wrong. NOT conservation loss.
|
||||
- **② bilingual source-half dropped (4: re-extract via B2)** — the original-language column under-captured, translation intact: aristotle-history-of-animals (89.5%, all top runs contiguous Greek source), sophocles-trachis (one 4241-tok Greek run), plautus (Latin original + speaker labels), demosthenes-42 (one Greek run). B2 preserve-typing recovers by construction. **The deficit is BODY, not apparatus → does NOT go in app[].**
|
||||
- **③ real mixed body loss (12: re-verify-and-reconvert)** — continuous *translation* prose genuinely gone + source + apparatus: athenaeus (199k), macrobius (an 18847-tok pure-English run missing), euripides/pindar/aristophanes fragments, philo-special-laws, sextus, longus, catullus, and the 3 Aeschylus verse plays (drop BOTH Greek column AND English runs). Genuine extractor failures; must VERIFY each passage returns, not assume.
|
||||
|
||||
**2. Folded ① into the map via a NEW classifier rule (`eb21eca`).** `wrong-match-by-fabrication` in `sweep_body_conservation.classify_book`: `m_fab > 5%` of candidate ⇒ the matched DSL key is wrong/partial → MATCH-SUSPECT (unifies with the holds>110% case). Threshold justified by a clean gap (fab is 0 for 943/952, 1 for one more; wrong-matches at ≥1298). Regenerated the map with a BOUNDED-CHANGE PROOF (exactly plutarch+suetonius change disp; 948/952 byte-identical). **augustine + philo (the 2 REORDER? books) carried the SAME signal LARGER but were FLAGGED-NOT-MOVED** — spans unread, REORDER? a held bucket; moving on the number alone is the refused move.
|
||||
|
||||
**3. Read + resolved the 2 REORDER? books (`836b665`) — the steward's context-caution earned real information.** His sharpening: a high fab means one thing in a book with no reordering, and might mean something specific to reordered bilingual text; inferring the same cause across two contexts without reading either is the refused move. Read both (identical method) + a CHECKABLE re-match to the truer key each span pointed to:
|
||||
- **augustine-confessions = PARTIAL key** (matched 'Confessions. Books 1–8'; candidate is the FULL 'Confessions' 123953) → re-match fab 36371→**0**, lost 29673→**0**.
|
||||
- **philo-on-abraham = WRONG sibling** (matched 'On the Migration of Abraham'; true 'On Abraham' 36734) → fab 11890→**0**, lost 15325→**0**.
|
||||
Both provably CLEAN against their true key — not merely "comparison invalid." **The REORDER? displacement was a pure ARTIFACT of the wrong/partial key** (comparing against a different/partial work manufactures both the fab AND the apparent rearrangement). **REORDER? has zero genuine members on this corpus** (detector kept — a right-key book could still truly reorder; absence-here ≠ cannot-exist). Classifier now **validates the key BEFORE diagnosing arrangement**. Reclassified → MATCH-SUSPECT (verified, not on the number). These 2 are the cheapest map wins: re-match → graduate CLEAN, no reconversion.
|
||||
|
||||
**4. Corrected a doc miscount (`c54edbb`).** The ③ summary cell counted table ROWS (10), not books (12) — its final row bundles the 3 Aeschylus plays. Surfaced by the steward's remedy-track arithmetic check (8+4+12=24=16+8). Map correct; note's cell was the sole inconsistency.
|
||||
|
||||
**Artifacts:** findings note `_curation/loeb-body-deficit-cause-analysis-2026-07-13.md`; map updated (802 CLEAN · 126 APPARATUS-SHAPED · 16 BODY-DEFICIT · 8 MATCH-SUSPECT · 0 REORDER?); tool-evolution-log ×2 entries; chamber CLAUDE.md map pointer. All three commits pushed both remotes.
|
||||
|
||||
## PRESENT — the mood
|
||||
|
||||
Tightly steered, and the steering was the value. The steward's discipline — **checkable claim over soft label; flag-don't-move on a signal until the substrate is read; the number IS the bug-detector** — held the whole session. Returns worth carrying: **flag-don't-move held** (augustine/philo flagged, not moved, until read+re-matched to 0/0); **verified against substrate not signal** (every reclassification rests on the missing text, then a checkable re-match); **the steward caught a stale governance marker at wake** (I'd said "REVIEWED-55 placement still owed" — FALSE, it was placed 07-12; the `inherited-marker-read-as-current-state` drift, corrected against ~/REVIEWED.md:490). Recalibrations: **a high fab means different things in different contexts** (a partial key and a wrong sibling are different failures producing the same reorder-looking artifact — only reading told them apart); **count books, not the bundled representation** (the ③ Aeschylus row = 3 books counted as 1); **verify a governance item's state against REVIEWED/PENDING before relaying**. The negative result (REORDER?=0 corpus-wide) is the load-bearing finding — it put the fix at the right layer (key-before-arrangement), not two patched rows.
|
||||
|
||||
## FUTURE — what is pulling
|
||||
|
||||
**PULLING THREAD: the matcher key-selection fix.** Fix `match_key`'s key-selection for near-duplicate / granularity-split / part-vs-whole DSL keys (exact-title preference + granularity aggregation + part-vs-whole handling). It resolves **all 8 MATCH-SUSPECT** to their true disposition, finalizing the reprocess target set BEFORE B2 runs, and cashes the map's accuracy (removes "comparison invalid" from 8 rows). Ready NOW — FIX-class (matcher, not the gate; no governance loop). **Built-in correctness check:** augustine + philo MUST re-match to CLEAN (proven 0/0 today); plutarch→'Other Fragments', suetonius→Rhetoricians key, the 4 holds>110% → the true keys the map details name.
|
||||
|
||||
**ACTIONABLE RESUMPTION POINT (as of wrap — re-judge against what changed):**
|
||||
- chamber-library clean, all 3 commits pushed both remotes (`c54edbb` at HEAD). Fleet 119/119.
|
||||
- First step: open `scripts/sweep_body_conservation.py` `match_key` + `_norm_set` — the near-duplicate/split/part-vs-whole key selection is the fix site. Read the 8 MATCH-SUSPECT map rows for their true-key hints (`_curation/loeb-body-conservation-map-2026-07-13.tsv`).
|
||||
- End state: re-run the sweep (bounded-change proof), the 8 MATCH-SUSPECT land on true disposition (augustine/philo→CLEAN as the check), map+note updated, committed+pushed, fleet green. One concentrated session.
|
||||
|
||||
**Other open horizons (ranked):**
|
||||
- **The steward's Loeb-first-vs-full-corpus SCOPING CALL** — his decision, not a build; unblocks the **2b sidecar-wiring graduation amendment** (the reprocess's first governance station). Once it lands, B2 graduates → populates app[] → the `DSL-full = candidate-body + sidecar-app[]` reconciliation runs → confirms 126-apparatus / 18-body as a FACT.
|
||||
- **The reprocess proper** — ② re-extract (4) + ③ re-verify-and-reconvert (12) — genuinely BLOCKED on the 2b amendment (B2 graduating into the flow). Not next-session candidates.
|
||||
- Everything from the 07-12 program open-work register that predates today still stands behind the B2 run.
|
||||
|
||||
**PAUSE STATEMENT:** I am about to be away from this. The map now carries cause the whole way down, and the reprocess is honestly sized (8/4/12) rather than lumped under one magnitude label. What I want to find still pulling on return: the matcher key-selection fix (the cheapest, most-ready bite — two of its eight are one re-match from CLEAN), and behind it the steward's scoping call that unblocks the B2 reprocess.
|
||||
|
||||
**LITERAL QUESTION for next-Claude:** When `match_key` is fixed and re-run, do all 8 MATCH-SUSPECT resolve to a *confident* true key — or does the fix expose a residual where a candidate has no single correct DSL sibling (a work genuinely split across many keys, or absent from the DSL)? augustine/philo/plutarch/suetonius have named true keys; the 4 holds>110% (aristotle-problems, galen, diogenes-6.2, lucian) are asserted-from-the-map-detail but NOT yet substrate-verified to re-match cleanly — that's the first thing to check, and the answer decides whether the matcher fix fully closes MATCH-SUSPECT or leaves a small genuinely-hard residual.
|
||||
|
||||
**State at wrap:** chamber-library clean + 3 commits pushed both remotes (eb21eca/836b665/c54edbb); fleet 119/119; map at `_curation/loeb-body-conservation-map-2026-07-13.tsv` (802/126/16/8/0); findings note beside it; PENDING-57 marked CLOSED under REVIEWED-57. dotfiles committed+pushed at wrap.
|
||||
@@ -14,6 +14,8 @@ metadata:
|
||||
- Literal-question ANSWER (substrate-verified): source IS reachable at gate-time — NOT from frontmatter `source:` (prose/bare-filename, e.g. Levi "olmOCR of Vintage International…"), but via gate zero's existing resolution: canonical_slug → Chamber Sources manifest (324 entries, each carries `archived_file`) or resolve_pending_source(slug) for a just-staged source. Source-access needs NO greenfield design — just a path-returning resolver sibling to manifest_has (which returns bool only). Tier derivable from archived extension (.epub→V-TEXT / .pdf→V-SCAN-abstain / Loeb DSL→V-DSL, forward-only: 0 Loeb canon graduated yet).
|
||||
|
||||
## Open horizons
|
||||
- 2026-07-13T15:53 — WAKE (20-min brief-pause, post-keystone-landed). Thread Confirmed: the B2 corpus reprocess the map now sizes. First station = the 2b sidecar-wiring graduation amendment, gated on the steward's Loeb-first-vs-full-corpus scoping call. Concentrated candidate bite = the 18 BODY-DEFICIT books (the wrap's literal question: same apparatus story as the 126, or genuinely different?). Nothing moved externally (chamber @ 9afb0cf, dotfiles clean). Doc-drift to fix: PENDING-57 block still reads "awaiting jurist" though REVIEWED-57 authorized → mark CLOSED. Steward pref active: shorter, very concentrated.
|
||||
- 2026-07-13T15:5x — RETURN (steward-caught): my wake briefing said "REVIEWED-55 placement still owed" — FALSE. Verified against substrate: REVIEWED-55 IS placed (~/REVIEWED.md:490, dated 2026-07-12, AUTHORIZED, full dispositions). Inherited a stale "owed" from this ledger's Authorization-moves shorthand and relayed it unchecked = `inherited-marker-read-as-current-state`. Nothing owed on -55. Antidote reaffirmed: verify a governance item's state against REVIEWED/PENDING before relaying.
|
||||
- 2026-07-13 — STEWARD-FLAGGED, for step 5 (the sweep), NOT now: "cross-extractor drift-tolerance" is under-defined and doing real work in that sentence. Must be spelled out with the same rigor V-DSL's reflow-vs-loss got (the whole reason V-DSL needed rebuilding was reflow looking like loss) BEFORE the retroactive sweep runs — do not assume it from the name. Present a written definition for concurrence when step 5 comes up.
|
||||
- 2026-07-13 — Integration point CONCURRED (steward): body_word_conservation lands as its OWN gate step in the graduation flow (with/after source_gate, source-in-hand layer), NOT inside collect_checks. FIX-class (where the call lives, not what it decides — the gate was ratified REVIEWED-57). Reuse gate zero's canonical_slug resolution (PENDING-52 holding under a use it wasn't built for). Build order: (1) resolver → (2) source_dispatch → (3) gate step → (4) spec reflect → (5) sweep [needs the drift-tolerance definition first].
|
||||
- 2026-07-13T07:56 — PULLING THREAD: land the keystone. Wire `verify_body_conservation` into `verify_graduation.py` + `graduation-spec.yaml` (per-tier dispatch V-DSL/V-TEXT/V-SCAN → FLAG/REVIEW/PASS), fold the cross-extractor drift-tolerance (retroactive probe: 7/9 PASS, 2 false-positive stopword drift), run the diagnostic sweep → corpus-health map. PENDING-57 ratified (REVIEWED-57 filed), schema LOCKED, B2 fleet-v1 built.
|
||||
@@ -37,6 +39,17 @@ metadata:
|
||||
- DISPOSITION for the diagnostic sweep (read-only, produces the corpus-health MAP; not a hard forward gate): residual 0 → clean · residual>0 → surface by size + contiguity note for human triage → sizes the 952-book reprocess.
|
||||
- Probe scripts: scratchpad probe_drift.py (raw) + probe_drift_accounted.py (mechanism). AWAITING STEWARD CONCURRENCE before building/running the 952-sweep.
|
||||
|
||||
## THE 18 — literal question ANSWERED by reading the missing spans (probe_18_spans.py, read-only)
|
||||
- METHOD: full-census script-mix of the missing multiset (greek=source-original vs latin-script=translation/apparatus) + top-3 uncovered runs read as actual text, per book. Script-mix is FULL census; the run reads are top-N sample (honest scope).
|
||||
- ANSWER: NO — the 18 do NOT resolve into the 126's apparatus story, and they are NOT one mechanism. They are THREE:
|
||||
· (D) MATCHER ERROR, not loss — 2 books: plutarch-moralia-other-fragments (true key "Other Fragments" 13891≈cand13399; matched to "...Other Named Works" 59997) + suetonius-grammarians-rhetoricians (candidate=Rhetoricians text, matched to Grammarians sibling key; fab=rhetorician/rhetor/antony). fab>0 is a reliable sub-110% wrong-match detector. SAME root cause as the 4 MATCH-SUSPECT → pull from reprocess; fix = matcher key-selection. Re-matched they likely go CLEAN.
|
||||
· (B) BILINGUAL SOURCE-HALF DROPPED — Greek/Latin ORIGINAL column under-captured, translation retained: aristotle-history-of-animals 89.5% (top runs all Greek source), demosthenes-42 88.8% (one Greek run), + the Greek-verse portion of the Aeschylus plays (persians/suppliants/eumenides) + sophocles-trachis. B2 preserve-the-typing recovers it. KEY: the deficit is BODY, not apparatus → does NOT go in app[].
|
||||
· (C) REAL MIXED BODY LOSS — continuous TRANSLATION passages genuinely gone + source + apparatus, large magnitude: athenaeus 70.1%(199k), macrobius 67.8%(79k, an 18847-tok pure-English run missing), euripides-dramatic-fragments 81.8%, philo-special-laws 84.4%, sextus-empiricus 75.8%, longus 57.9%, catullus 57.2%, pindar-fragments 58.9%, aristophanes-attributed-fragments 82.7%, plautus-three-dollar-day 87.0%. Genuine reconversion targets; must VERIFY passages recovered, not just re-typed.
|
||||
- COROLLARY (the wrap's held sub-question): for the 18, DSL-full ≠ candidate-body + sidecar-app[] by multiset — the deficit is body, so app[]-population will NOT reconcile it (unlike the 126). ⇒ a clean DISCRIMINATING TEST once B2 runs: reconciles→apparatus(126); doesn't→body(18).
|
||||
- CONSEQUENCE for the pulling thread: the B2 reprocess is NOT one sidecar-population job. B2+sidecar solves (B)+the 126; the matcher fix solves (D); (C) needs genuine body-recovery reconversion + per-book verify. Three tracks, not one.
|
||||
- LANDED (steward-directed "write it"): map folded (via a wrong-match-by-fabrication rule in classify_book, m_fab>5% cand → MATCH-SUSPECT) + regenerated with BOUNDED-CHANGE PROOF (exactly plutarch+suetonius change disp; augustine/philo detail-only flag; 948/952 byte-identical; new tallies 802/126/16/6-MATCH-SUSPECT/2) + findings note `_curation/loeb-body-deficit-cause-analysis-2026-07-13.md` + tool-evolution-log entry + CLAUDE.md pointer. Fleet 119/119. Committed `eb21eca` [FIX], pushed BOTH remotes. augustine/philo surfaced-not-folded (larger fab, spans unread → flagged, held in REORDER?). Matcher key-selection fix now gates 6 MATCH-SUSPECT + 2 REORDER? leads = highest-leverage small corpus-health fix.
|
||||
- CLOSED the augustine/philo lead (steward-directed, same method): span-read + CHECKABLE re-match to the truer key each span pointed to. BOTH resolved to fab=0/lost=0 CLEAN against true key (augustine = PARTIAL key: candidate is full 'Confessions', matched to 'Books 1-8'; philo = WRONG sibling: true 'On Abraham', matched to 'On the Migration of Abraham'). The REORDER? displacement was a pure wrong/partial-key ARTIFACT; REORDER? has 0 genuine members on this corpus. Classifier now validates key BEFORE arrangement. Reclassified to MATCH-SUSPECT (verified, not on the number). Bounded-change proven (exactly augustine+philo change disp; 948/952 byte-identical). Tallies now 802/126/16/8-MATCH-SUSPECT/0-REORDER?. Fleet 119/119. Committed 836b665 [FIX], pushed both remotes. These 2 = cheapest map wins (re-match to named true key -> graduate CLEAN, no reconversion). Steward's context-caution earned real info: the fab signal is a reliable match-problem detector even inside a reordering context; the reorder was a symptom of the wrong key, not an independent phenomenon.
|
||||
|
||||
## Sub-agent dialogues
|
||||
|
||||
## RETURN — the verse cluster (caught by staying with the run, 25-book batch)
|
||||
|
||||
Reference in New Issue
Block a user