dotfiles/claude/memory/project-chamber-versioned-releases.md

name, description, metadata

name	description	metadata
project-chamber-versioned-releases	The Chamber is realized as VERSIONED releases with soft borders, purpose-driven — Chamber V1 = a bounded (constitution vX + engine vY + a chosen voice-set), serving a specific USE; the full 2000-year Chamber (incl. image-based Warburg/Jung, Berger, Alexander) is the horizon, not V1. Bounds the enormity; makes the corpus usable-for-purpose, not an unbounded dream.	node_type type originSessionId modified memory project 58ba5886-9bb6-415f-9440-a4b87099ffa0 2026-07-25T08:04:23.830Z

Steward reframe (2026-07-25): the full Chamber — all the voices across 2000 years, including the image-based works (Warburg's Mnemosyne Atlas, Jung's Red Book) and the personally-foundational Berger and Christopher Alexander — cannot be realized all at once, and shouldn't be attempted that way. The Chamber is realized as versioned releases with soft borders: "Chamber V1 = constitution vX + engine vY + a bounded voice-set, serving a specific purpose"; then with capability x, "Chamber V2", and so on. The full Chamber is the horizon, not the V1 deliverable.

The driver is PURPOSE, not corpus-completeness. The steward needs to use the Chamber for concrete work, not only the unbounded dream of "talking to the library and the minds who formed him" (project-studium-engine-telos-chamber-of-voices — this is the practical bounding of that telos). Named purposes awaiting the Chamber: the Making Sequence · the violin / music-in-the-XXI-century treatise · ARC. And: this library/engine work directly informs CapableMind.

Why (load-bearing): the enormity was the paralysis — "the corpus must be trustworthy before I can use it" collapsed into "wait for everything." Versioning dissolves it: a bounded V1 whose properties are proven-or-named (the jurist's floor — feedback-census-by-mechanism-not-proxy kin; boundedness IS trust) is legitimately usable NOW. Selection criterion is stability (re-conversion breaks engine work, not imperfection), not quality.

How to apply — the scoping that re-bounds the library work:

• Purpose-first. The V-TEXT wave does NOT all need to clear for V1. A chosen purpose (Making / violin treatise / ARC) defines a bounded voice-set, and that set is Chamber V1's corpus. Scope every library bite by "what does V1's purpose need," not "graduate the whole corpus."
• Today's work was the first bricks of the versioned roadmap (2026-07-25): PENDING-75 kind-scoping is the constitutional mechanism that lets image-based works (Warburg/Jung) enter a later Chamber version as an additive new declared kind — NOT a re-founding; the mechanism-census (_curation/mechanism-census-2026-07-25.tsv) is what lets a soft border be drawn with knowledge of the corpus's real distribution.
• Subordinates the open library questions. The internal-nav curation ruling (the wrap's pulling thread) matters for V1 only if V1's chosen voices are nav-heavy books; otherwise it defers. Same for the class-leak, glyph-maps, the 47-file wave — they become inputs to V1 scoping, not open-ended obligations.
• 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.