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/MEMORY-reference.md

@@ -27,6 +27,12 @@ metadata:
 
 Split out of [MEMORY.md](MEMORY.md) on 2026-07-06 to keep the wake-loaded index under the harness load ceiling. **Lossless** — every line was relocated verbatim, nothing pruned. A separate future pass may prune genuinely-dead content here (much of the 2026-04/05 pending-work is long done); until then this is the complete historical record.
 
+## Relocated from MEMORY.md at the 2026-08-07 trim (steward-directed; verbatim)
+
+*One tracker entry relocated: a workstream the steward closed, whose only live clause is carried elsewhere in the wake-loaded index. Everything else in the 2026-08-07 trim was compressed in place toward its own linked file, not moved here.*
+
+- [MemPalace wind-down](project-mempalace-winddown.md) — DONE (steward 2026-07-07): `palace-memory` wound down, wake/wrap rewired to the files layer; KG exported (`knowledge-graph.jsonl`). Typography palace KEPT (separate instance). *(Relocation note, 2026-08-07: a completed workstream. Its one live clause — the typography-palace exception — is carried by the `reference-typography-palace-cli.md` standing preference, which stays wake-loaded; and `/wake-up`'s own constraints already forbid calling `mempalace_*` for palace-memory. Nothing depends on this line at wake.)*
+
 ## Canonical tracker — full relocated detail
 
 ### ARC — full chronological inline log (relocated verbatim from MEMORY.md line 40, 2026-07-06)