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

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

@@ -5,7 +5,7 @@ metadata:
   node_type: memory
   type: project
   originSessionId: 58ba5886-9bb6-415f-9440-a4b87099ffa0
-  modified: 2026-07-25T08:04:23.830Z
+  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.
@@ -22,6 +22,8 @@ metadata:
 
 **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**.