dotfiles/claude/memory/project-chamber-rewrite-frame-2026-04-26.md

---
permalink: claude-memory/project-chamber-rewrite-frame-2026-04-26
---

---
name: Chamber page rewrite frame 2026-04-26 (v1 archived → v2 source-aware; awaiting direction)
description: Frame for rewriting ARC's /chamber/ pages to reflect Chamber's v1→v2 evolution. v1 was an elaborate simulation with fictional canon and deliberations (now archived). v2 is source-aware: constrained retrieval, verifiable citation, contamination-mitigation governance, "rigorous reading and thinking" as the working register. The rewrite must announce the shift, not gloss it. Awaiting steward direction.
type: project
originSessionId: 87dfe384-b862-4deb-9676-24e43046528f
---

> **INTEGRATED 2026-04-26 → `project-arc-rework.md` (Integration C).** Steward authorization: *"Integrate. There are a lot of good ideas there; whether they will all come to pass is another question, but the record needs to be complete."* Content folded into the canonical ARC workstream tracker. **Note: the 2026-04-23 entry in project-arc-rework.md already settled Chamber redistribution** (⟐ → §2 apparatus; v1 deliberations as "fruits of those labors" archive section; fictional canon → Heteronym ⁂; compass row removed; rewrite post-L2-unpark). The detail in this file is the executable detail for when the rewrite session arrives. This file retained as audit trail. **For current home of Chamber rewrite drop/keep/add + open questions, see `project-arc-rework.md` § "Integration C: Chamber page rewrite — drop/keep/add detail + open questions."**

---

# Chamber page rewrite — frame (v1 archived → v2 source-aware)

**Status:** Frame revised 2026-04-26 (afternoon) after reading the source-aware document. Steward to decide whether and how to proceed. Depends on About-pages path-decision (`project-about-pages-decision-frame-2026-04-26.md`).

**Steward verbatim 2026-04-26 (initial):** *"How would we rewrite the chamber page to reflect what it is becoming now? Do we talk about what it was before?"*

**Steward correction 2026-04-26 (substantive):** *"the fictional canon and deliberations we decided to archive as part of the v1 Chamber. This should be in your notes somewhere. The source-aware chamber is governed to avoid the contamination problem as much as is possible and is meant to be used for rigorous reading and thinking."*

---

## The keystone shift: v1 (Simulation) → v2 (Source-Aware)

This is not "evolution within the Chamber." It is a categorical reframe of what the Chamber *is*. The rewrite must announce the shift, not gloss it.

### v1 — Simulation (archived)

What the existing /chamber/ pages describe. Source: `chamber-from-simulation-to-source-aware.md` §2.

- 220+ voices simulated via Claude system prompts (`claude-v2-standard.md`, `claude-v2-first-light.md`, `claude-v2-shadow.md`)
- Voices drew on Claude's training data — vast, undifferentiated, unverifiable
- Citations were *assertions*, not retrievals: "Hegel argues in §142..." was plausible but not grounded
- **Fictional bibliography** with five-notation system (° invented · ~ hybrid · † contested · § synthesis · ∞ hermetic) — fictional works "made real through citation"
- **The Growing Canon** — Borges-tradition: authority grows through use rather than origin
- Functional for editorial work, but *cannot* verify, cannot bound knowledge, cannot detect appropriate silence, cannot train for accuracy

**Steward's decision:** archive. Fictional canon and deliberations preserved on the site but **not active going forward**. They are v1 artifacts — the record of where the Chamber-as-practice came from, not the current Chamber.

### v2 — Source-Aware (current direction)

What the Chamber is becoming. Source: `chamber-from-simulation-to-source-aware.md` §3.

- **Constrained retrieval against declared corpus.** Voices read from chamber-library (David's actual MD files), ingested via BMF (Entity Module → Author/Work/Edition/Passage; Vector Module → passage-level embeddings; Blob Module → original text with stable IDs)
- **Verifiable citation** at passage level, edition-aware. Post-generation citation checking: each claim verified against retrieved passage. Unverifiable claims flagged or suppressed.
- **Bounded, inspectable knowledge.** The corpus manifest declares scope. The system can answer: "What works by Harrison have been ingested? Which editions? How many passages?" Coverage is measurable.
- **Scoped silence as first-class outcome.** When retrieval finds nothing, the voice declares silence with calibrated confidence. `align.deliberation.silence` is a structural deliberation act, not failure.
- **Warrant taxonomy** (ReasonChain v1.8): W_DEM (direct citation), W_INF (interpretation), W_TRD (tradition). `effective_warrant_type` = transitive minimum (derivation chains can only weaken warrant, never strengthen) — anti-pilpul at the data level.
- **Means-of-knowing classification:** every event classified by epistemic basis (perception/testimony/inference).
- **The Disciple model** as quality control: Understudy → Candidate → Defense → Scholar. Understudies constrained to W_DEM only (citation, not interpretation). Advancement requires citation-accuracy ≥ 0.95, calibration ≥ 0.85, refusal ≥ 0.90.
- **Anti-pilpul safeguards:** source anchoring, warrant taxonomy, effective-warrant transitivity, authority boundary, "return to source" checkpoints.
- **Working register: rigorous reading and thinking.** Not hermetic theatre. Not Borges-laboratory. Slow, source-anchored, dissent-preserving deliberation.

### Why the shift: contamination mitigation

The contamination problem the global CLAUDE.md names — *"a structural pressure in LLM training toward outputs that satisfy the interlocutor rather than outputs that are true or revealing"* — is the deep target of v2's governance. v1's simulation was contamination-shaped by construction (plausible voices producing plausible citations from training data, with no boundary against fabrication). v2's source-awareness is the architectural commitment against that pattern: bounded knowledge, verifiable claims, structural silence, transitive warrant minimum.

**This makes Chamber-on-CapableMind a working-out of the steward's deepest architectural concern**, not a separate apparatus. The Chamber is contamination-mitigation expressed as deliberation form.

---

## How to rewrite (registrar's read — steward decides)

The rewrite has to do three things:

### 1. Announce the shift (don't gloss it)

The opening of the new /chamber/ page should make the v1→v2 distinction explicit and dignified. Something like:

> *The Chamber began as an elaborate simulation — voices conjured from training data, deliberations enacted, a fictional canon grown through citation. That work is preserved here as v1. The current Chamber is a different commitment.*

This is the colophon's revision-history move at higher stakes. The reader needs to understand which Chamber they are encountering.

### 2. Describe v2 in its own register

What the Chamber is now:

- **Source-aware:** every voice reads from the chamber-library, every claim cites a passage, every citation is checked
- **Bounded:** the system knows what it doesn't know; absence is detectable; silence is calibrated
- **Governed against contamination:** warrant taxonomy, effective-warrant minimum, return-to-source discipline, autonomy ≤ propose
- **Working register:** rigorous reading and thinking. Slow. Dissent preserved. No forced synthesis.
- **Built on CapableMind:** the engine lives there; ARC publishes what comes out of it

Three protocols (First Light, Standard, Shadow) likely survive into v2 with adjusted register — they were always about phasing and stance, not about simulation. *Verify against current chamber-facet-addendum before rewriting.*

The seal ⟐ likely survives. *Verify.*

### 3. Frame the archived v1 work as preserved-and-clearly-marked

`/chamber/canon/` and `/chamber/deliberations/` (current pages) are real artifacts of v1 work. Archiving doesn't mean deleting — it means making clear that:
- These are v1 outputs, not current Chamber
- They are preserved as the record of where the Chamber-as-practice came from
- They are not canonical and not growing
- They retain their fictional-bibliography notation (° ~ † § ∞) as part of their v1 form, not as a current system

A clear "v1 Archive" framing on those pages prevents the reader from mistaking archived v1 for current v2.

---

## Drop / Keep / Add (revised)

### Drop

- **Fictional bibliography notation system** (° ~ † § ∞) — gone with v1 (kept only on archived pages as historical form)
- **"The Growing Canon"** / "References to non-existent works...become real through citation" / "Authority grows through use rather than origin" — gone
- **Borges-tradition framing** — gone
- **Voices-as-characters** with names like *The Janitor Who Knows Where Sound Lives*, *The Unborn Child*, *The Algorithm* — these were v1 simulation devices; v2 voices are corpus-scoped retrieval engines, not characters
- **Hermetic apparatus** — Khunrath, "as above so below," "the editorial process mirrors cosmic transformation" — gone (the working register shifts to rigorous reading and thinking)
- **"Some processes resist documentation"** / "Some transformations cannot be described, only undergone" — gone (v2 is structurally documented)
- **"Private development"** hedging — replaced by clear v2-status framing

### Keep

- The amphitheater metaphor — likely survives in lighter form (voices gather across traditions)
- The three protocols (First Light, Standard, Shadow) — survive with adjusted register
- The seal ⟐ — likely survives as marker of v2 transformation
- Reply-as-ethical-event framing
- Refusal as valid outcome — now structural in v2 (`align.deliberation.silence`)
- Shadow examination as ethical reckoning
- "Some texts need the shadow to find their light. Others discover they should remain unwritten." — survives if Shadow protocol survives in v2 form

*Confirmation needed against current chamber-facet-addendum and v2 design docs.*

### Add (central to v2)

- **Source-awareness as commitment** — every voice reads from chamber-library, every citation is verifiable
- **The contamination problem the Chamber addresses** — governance against fabrication, plausibility-without-grounding, paraphrase-drift
- **Rigorous reading and thinking** as the working register
- **Bounded knowledge** — corpus manifest, coverage metrics, calibrated silence
- **Verifiable citation** — passage-level, edition-aware, post-generation checked
- **Warrant taxonomy** (W_DEM / W_INF / W_TRD) and transitive warrant minimum (effective_warrant) as anti-pilpul
- **The Disciple model** (Understudy → Candidate → Defense → Scholar) — quality control; Understudies cite only
- **The chamber-library** as substrate (named, linked if appropriate)
- **CapableMind** as the engine; ARC as publication-face — the architectural separation
- **Contamination-aware governance** as not just feature but commitment

---

## On whether to talk about what it was before — revised

**Yes, briefly and substantively.** Earlier I framed this as a small status-note exception. The v1 archive changes the answer.

The /chamber/canon/ and /chamber/deliberations/ pages are real, visible, on the site. A reader who lands on /chamber/ and clicks through has to encounter them. The new /chamber/ page must:

1. **Announce v2** as the current Chamber (its commitments, its register)
2. **Frame v1 as archived** — preserved as the record of where the Chamber came from, not as current operation
3. **Make the shift legible** — explain why v2 differs, in dignified compression. The contamination-problem framing is the through-line: v1 was a powerful simulation but its outputs could not be verified; v2 is built around verification.

This is the colophon's revision-history move at higher stakes — not just versioning a page but versioning a commitment.

---

## One redundancy worth surfacing

`/content/chamber/index.md` and `/content/chamber/about.md` cover substantially overlapping ground (both v1). Same Marie Kondo principle. **Collapse to /chamber/ as entry only** — content that survives the rewrite folds into one v2 page. /chamber/about/ disappears or redirects.

The chamber-enfilade then becomes:

> Chamber (v2 entry) · Canon (v1 archive) · Deliberations (v1 archive) · Voices (v1 archive, possibly v2 register grows alongside)

`/chamber/voices/` is a special case — voices in v2 are real retrieval-engines with corpus manifests; the v1 voice patterns may or may not map. Steward call.

---

## File state observations (worth a steward note)

- Two parallel trees: `/chamber/` (top-level dir with `permalink:` frontmatter) and `/content/chamber/` (Hakyll content path). Need to verify which is canonical.
- Current v1 pages dated `2025-07-05` with `date_display: Date unknown`, `bibliographic_date: Undated`, `origin_epoch: undetermined` — date-effaced register suited v1's hermetic theatre. v2's register is *dated, situated, source-anchored* — effacement may no longer fit.

---

## Status

- Frame revised on the table (2026-04-26 afternoon).
- Awaiting steward direction.
- Depends on About-pages path-decision (Path 2 makes Chamber a door from the threshold).

## Open questions to the steward

1. **Three protocols (First Light / Standard / Shadow)** — confirmed surviving v1→v2? (Source-aware document references them but with adjusted register.)
2. **The seal ⟐** — survives v2?
3. **Amphitheater metaphor** — keep, lighten, or retire? (v2 is colder and more rigorous; the amphitheater is warm and theatrical.)
4. **/chamber/voices/** — does v2 have its own voices page that grows alongside v1's? Or is v1 voices the only voices page until v2 is operational?
5. **Steward-specific phrasing for the v1→v2 announcement** — held for steward's voice; my drafting is registrar-only