Files
dotfiles/claude/memory/project-chamber-versioned-releases.md
T
David F GliddenandClaude Opus 5 5c4055a071 memory: MEMORY.md trim, the engine tracker, and one superseded claim
MEMORY.md 20,413 -> 16,887 B (19.9 -> 16.5 KB), steward-directed at the
2026-08-06 evening wrap after three deferrals. Relocation, not deletion, and
verified as such: 0 dead pointers, 0 orphaned clauses, every dropped
backticked span traced to a home elsewhere in the corpus.

Method, derived rather than felt: an entry keeps its rule inline when it fires
at a moment I would not recognise as needing a lookup (spelling, quotation,
"am I deferring?"); it shrinks to a pointer when the trigger is loud enough
that the file gets opened anyway (chamber work, L1 work, a jurist package);
and a ⚠ constraint always travels with the workaround it limits, never
relocated away from it.

The mechanical diff of dropped spans caught two losses that re-reading did
not: `feedback-constitution-as-block-then-pull-based-corpus` dropped by
inattention (a fires-silently rule — restored), and the facet-formalism
pointer for the V1-purpose decision, which existed ONLY on the index line
being compressed. That second one is
`removing-a-claim-is-not-removing-the-reliance` exactly: the open decision
would have stayed live with its formalism unfindable. Relocated into
project-chamber-versioned-releases.md, its canonical surface, rather than
back into the index.

project-studium-engine.md — NEW, and the gap MEMORY.md itself had flagged as
"no tracker file yet". The engine's state had been living inline in the index
(one 950-character line pointing at the charter, a constitutional document
that holds no build state) plus per-session memories: two update surfaces and
no canonical one. Now holds current state, a chronological log, and the
open-thread stack captured mid-session so the day's accumulation cannot be
lost.

MemPalace wind-down relocated to MEMORY-reference.md — a workstream closed
2026-07-07 whose one live clause (the typography-palace exception) is carried
by a standing preference that stays wake-loaded.

session-2026-08-06-evening: the claim that Alexander's rating classes
"compare as identical" under @3 is marked SUPERSEDED and false. Measured
while landing the fix: old @3 gave COMPOST\ , COMPOST\\ , COMPOST — three
distinct strings. The ratings never collided; the real defect ran the
opposite way, corrupting the rating into a backslash residue and causing
false REFUSALS. I carried that generalisation into the record from the
package's Part III(a) without checking it against the package's own Part I
table, which printed the refutation.

session-ledger-2026-08-07: the day's returns, including that every defect
found today was found by a COUNT rather than a read — the dropped-span diff,
the span-count-versus-store (769 unreachable drawers), the adapter comparison
(3 of 253) — and that twice the instrument itself was at fault in the more
dangerous direction, failing healthy data in a way that invites editing the
data to satisfy the checker.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NEWjLBP4quXbDPDL2byEzZ
2026-08-07 17:22:29 +02:00

38 lines
6.4 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
name: project-chamber-versioned-releases
description: "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."
metadata:
node_type: memory
type: project
originSessionId: 58ba5886-9bb6-415f-9440-a4b87099ffa0
modified: 2026-08-07T09:58:00.358Z
---
**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.
> **Where the facet formalism lives:** `~/_Dev/studium-engine/docs/parallel-tracks-library-engine-and-capablemind-2026-08-03.md`. *(Relocated here 2026-08-07 at the MEMORY.md trim. This pointer had existed **only** on the MEMORY.md index line — compressing that line would have left the open decision live and its formalism unfindable. Recorded here because this file, not the index, is the canonical surface for the decision.)*
---
**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.