David/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

session 2026-07-28 evening: chamber scope verified + Harrison re-gate pilot decided

Browse Source 
Session record, MEMORY.md promote/demote, versioned-releases tracker update,
5 KG drift-patterns. Corpus scope verified from a regenerated quality ledger:
952/1297 clean, 69 apparatus-defect, 11 pass graduation — the gap is
conformance, not content. Docling trial proved re-conversion recovers
addressable apparatus (96.5%->99.1%). Nine instances of one shape:
instrument-coverage-never-established.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WuMjg3ipEVa3n8CoSzoyvc
This commit is contained in:
David F Glidden
2026-07-28 13:13:42 +02:00
co-authored by Claude Opus 5
parent dc9b6f53d9
commit 30fc1694a4
6 changed files with 98 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
claude/memory/project-chamber-versioned-releases.md
+12
View File
@@ -21,3 +21,15 @@ metadata:
- **Cheap re-anchoring is the one prerequisite** the jurist flagged (the 5 FAILED coverage-ledger rows since 2026-06-10, the PENDING-53 class) — worth having before the engine *depends* on any fenced set, independent of which set.
**The open decision (holds for a purpose-scoping bite):** which purpose anchors Chamber V1, and what bounded voice-set + capability envelope does it need? That decision scopes the constitution version, the engine version, and the corpus subset for V1 — and tells us which of the open library questions are V1-blocking vs V2-deferrable.
---
**2026-07-28 — the precondition surfaced, and it re-bounds the scoping rule.** Chasing "which purpose anchors V1" reached the corpus itself, and the corpus was never in the frame. Verified scope (fresh `corpus-quality-ledger.tsv`, self-test PASS): **952/1297 clean · 69 apparatus-class defects · but only 11 of 1297 pass current graduation** (323 fail, 963 never assessed). **The gap is conformance, not content** — the corpus predates its own constitution. So neither "rebuild" nor "retrofit" is the right word: it is **re-gate**.
**How this changes the scoping rule (sharpens, does not replace, the purpose-first rule above):** you never re-gate 1,297 files for a version. **You re-gate the bounded voice-set the chosen purpose needs** — which makes the corpus job and the purpose choice *the same decision*, not sequential ones. A version's corpus work is therefore finite by construction, exactly as the versioning frame intends.
**Proven, not argued:** Harrison *Dominion* through the docling `pdf_textlayer` lane (scratch only, nothing graduated) recovered **96.5% → 99.1%** of source words and turned an unmarked run-together region into **`## Works Cited` with one entry per line**. Per-entry addressability cannot be retrofitted onto paragraph blocks ⇒ **re-conversion is the remedy**. Blocking prerequisite for any corpus-wide PDF wave: a **general running-head detector** (14 false headings; the Auerbach-specific one was archived 2026-07-03; already in the runbook's `known_gaps`).
**Bearing on the purpose choice:** typography now carries a fourth ground — **8/23 of its sources have bibliography headings, ~10× the corpus rate** — which matters because the steward named **bibliography-as-convocation** (what works did an author use?) and **gap→acquisition** as functions he does not want lost. Those are one mechanism facing two directions: *what does this convocation fail to cover* → **summon** (on the shelves) or **acquire** (not yet). See [[project-studium-engine-telos-chamber-of-voices]].
**⚠ Re-anchor is the real cost of any re-gate**, not the conversion: a new canonical hash invalidates bindings across **both** repos (chamber catalogue + engine manifest/sidecar/coverage-ledger). Read `_curation/conversion-runbook.yaml` `reanchor:` before touching a canonical.