chore(memory): Basic Memory trial begins — sync normalization baseline (283 files)

Basic Memory v0.21.6 first sync over the live memory dir (steward-authorized live-dir trial, Option A 2026-06-06): adds permalink: to frontmatter, refolds long YAML description lines, strips final newlines. Bodies untouched — verified via full diff classification. From this commit forward, any diff in claude/memory shows only what Basic Memory or the session writes. Trial design: MemPalace untouched as incumbent; git status check on this dir at every wrap; end-of-day evaluation (recall quality, sync robustness, rebuild-from-files, malformed-file behavior). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-06 09:52:17 +02:00
parent 161fad7ae2
commit 3f9a89b00c
283 changed files with 2055 additions and 620 deletions
@@ -1,3 +1,9 @@
+---
+title: MEMORY
+type: note
+permalink: claude-memory/memory
+---
+
 # Claude Code Memory

 ## Standing preferences
@@ -1,7 +1,9 @@
 ---
 name: ARC removed content types
-description: Seven archive links removed April 2026 — revisit if these types re-emerge from the writing practice
+description: Seven archive links removed April 2026 — revisit if these types re-emerge
+  from the writing practice
 type: project
+permalink: claude-memory/arc-removed-content-types
 ---

 Content types removed from the ARC archive template (2026-04-13). No routes existed for any of them. Only types with framework theory and Hakyll routes should appear.
@@ -1,7 +1,9 @@
 ---
 name: CapableMind L1 Detailed State
-description: Technical details about BMF deployment, issues, and architecture on David's machine
+description: Technical details about BMF deployment, issues, and architecture on David's
+  machine
 type: project
+permalink: claude-memory/bmf-details
 ---

 # CapableMind L1 — Technical Details
@@ -1,9 +1,12 @@
 ---
 name: BMF summarizer-connector coupling
-description: Factory's maybeGenerateSummary is silently coupled to the local_files observation shape; most connectors fall through. Deferred refactor target.
+description: Factory's maybeGenerateSummary is silently coupled to the local_files
+  observation shape; most connectors fall through. Deferred refactor target.
 type: project
 originSessionId: 1c1bf37d-b1c3-4a62-9355-613c50f4c028
+permalink: claude-memory/bmf-summarizer-contract
 ---
+
 # BMF summarizer-connector coupling (deferred refactor)

 **Surfaced:** 2026-04-14, during the SQLite+LanceDB recall unblock session.
@@ -1,7 +1,9 @@
 ---
 name: Cabaret Project
-description: New artistic project — contemporary cabaret in Barcelona, Paris-Vienna-Barcelona triangle, Pierrot Lunaire as anchor work, interdisciplinary collective
+description: New artistic project — contemporary cabaret in Barcelona, Paris-Vienna-Barcelona
+  triangle, Pierrot Lunaire as anchor work, interdisciplinary collective
 type: project
+permalink: claude-memory/cabaret-project
 ---

 David is developing a cabaret project — a registration and contemporary adaptation of the European cabaret tradition (Paris → Vienna → Barcelona, 1880s–1930s). Stem-cell phase as of 2026-04-04.
@@ -1,7 +1,9 @@
 ---
 name: Chamber Chavruta Prototype
-description: Architecture, phase status, source texts, and empirical findings from the Chamber deliberation prototype
+description: Architecture, phase status, source texts, and empirical findings from
+  the Chamber deliberation prototype
 type: project
+permalink: claude-memory/chamber-prototype
 ---

 # Chamber Chavruta Prototype State
@@ -1,7 +1,9 @@
 ---
 name: Signal Travel Protocol — collaborative method
-description: Jointly developed diagnostic/evaluative method for testing whether built systems honour their specs. First applied to BMF L1, intended for Chamber and L2.
+description: Jointly developed diagnostic/evaluative method for testing whether built
+  systems honour their specs. First applied to BMF L1, intended for Chamber and L2.
 type: project
+permalink: claude-memory/collaboration-signal-travel
 ---

 Signal Travel Protocol written up in `CapableMind-AI/docs/thinking/David/methodology/signal-travel-protocol.md`.
@@ -1,3 +1,9 @@
+---
+title: context-discipline
+type: note
+permalink: claude-memory/context-discipline
+---
+
 # Context Efficiency Discipline

 ## Purpose
@@ -1,7 +1,9 @@
 ---
 name: Design Brief — Session Start/End Agents
-description: Design problem for session lifecycle agents that replace manual memory maintenance with source-of-truth reconciliation
+description: Design problem for session lifecycle agents that replace manual memory
+  maintenance with source-of-truth reconciliation
 type: project
+permalink: claude-memory/design-brief-session-agents
 ---

 # Design Brief: Session Lifecycle Agents
@@ -1,7 +1,9 @@
 ---
 name: Design Brief — Session Skills (Vault Sync + Wrap-up)
-description: Two skills to design next session — vault-sync (thinking mirror to Obsidian) and session-wrap-up (memory, vault, handoff, open threads, uncommitted work)
+description: Two skills to design next session — vault-sync (thinking mirror to Obsidian)
+  and session-wrap-up (memory, vault, handoff, open threads, uncommitted work)
 type: project
+permalink: claude-memory/design-brief-session-skills
 ---

 ## Skills to Design (flagged 2026-04-05)
@@ -1,9 +1,12 @@
 ---
 name: Manual diary entry — 2026-05-05 session-handoff
-description: AAAK-style diary entry written manually because MCP is down (mempalace_diary_write unavailable). Voice for the next session.
+description: AAAK-style diary entry written manually because MCP is down (mempalace_diary_write
+  unavailable). Voice for the next session.
 type: project
 originSessionId: a156edbb-0c3d-4285-b3ed-f5a45b8dda66
+permalink: claude-memory/diary-2026-05-05-manual
 ---
+
 # Manual diary — 2026-05-05 (mempalace MCP down; written to file)

 ## AAAK entry
@@ -1,9 +1,12 @@
 ---
 name: Manual diary entry — 2026-05-11 session-handoff
-description: AAAK-style entry. MCP down for clean re-mine isolation; manual file fallback. Voice for next session.
+description: AAAK-style entry. MCP down for clean re-mine isolation; manual file fallback.
+  Voice for next session.
 type: project
 originSessionId: a156edbb-0c3d-4285-b3ed-f5a45b8dda66
+permalink: claude-memory/diary-2026-05-11-manual
 ---
+
 # Manual diary — 2026-05-11

 ## AAAK entry
@@ -1,7 +1,9 @@
 ---
 name: Diary Export 2026-05-05 — wing_claude-code
-description: Verbatim export of all 30 wing_claude-code drawers from palace.broken-config-2026-05-05 before fresh-palace rebuild. 29 diary_entry + 1 other. Sorted chronologically.
+description: Verbatim export of all 30 wing_claude-code drawers from palace.broken-config-2026-05-05
+  before fresh-palace rebuild. 29 diary_entry + 1 other. Sorted chronologically.
 type: reference
+permalink: claude-memory/diary-export-2026-05-05
 ---

 # Diary Export — 2026-05-05
@@ -1,9 +1,13 @@
 ---
 name: Acknowledgments wait for empirical validation
-description: When a maintainer/contributor addresses our findings on a PR or issue, delay the thank-you until any active validation run produces data we can include. Don't acknowledge eagerly out of social momentum.
+description: When a maintainer/contributor addresses our findings on a PR or issue,
+  delay the thank-you until any active validation run produces data we can include.
+  Don't acknowledge eagerly out of social momentum.
 type: feedback
 originSessionId: a5411fd1-4a96-43e7-aa1a-1a50d8951a8f
+permalink: claude-memory/feedback-acknowledgments-wait-for-validation
 ---
+
 When a maintainer or contributor responds to our findings on an open PR or issue (especially with code fixes) AND we have an active validation run underway against the same surface, **wait to acknowledge until the validation produces data**.

 **Why:** Steward's reasoning (2026-05-12, in the context of Shtefan's `ceccbfa` commit responding to our PR #442 test report while our chamber-library mine was still running): *"Once the mine completes is the right moment — whatever data that gives us is all the more valuable and the gratitude will land more authentically."*
@@ -1,9 +1,15 @@
 ---
 name: Action completes the outcome — integration completes the work
-description: Umbrella drift pattern across multiple layers (substrate, build, editorial, memory). The visible outcome appears complete; the integration step that makes the artifact durable/findable/correct is silently skipped. Surfaces as deploy ≠ commit, write ≠ index, draft ≠ verify, count ≠ vault-write. Saved 2026-05-06 after three same-shape instances in a single session.
+description: Umbrella drift pattern across multiple layers (substrate, build, editorial,
+  memory). The visible outcome appears complete; the integration step that makes the
+  artifact durable/findable/correct is silently skipped. Surfaces as deploy ≠ commit,
+  write ≠ index, draft ≠ verify, count ≠ vault-write. Saved 2026-05-06 after three
+  same-shape instances in a single session.
 type: feedback
 originSessionId: 3bf7ae75-1138-4745-9024-0c40b3755ad3
+permalink: claude-memory/feedback-action-completes-outcome-integration-completes-work
 ---
+
 **Pattern:** A structural action produces a visible outcome that *looks* complete. The action's integration step — the move that ties the outcome into a durable, findable, or verified state — is silently skipped. The work appears done; the work is not done. The drift is invisible until a downstream check (next session, next collaborator, next verification) surfaces the gap.

 ## Instances of the same shape
@@ -1,9 +1,14 @@
 ---
 name: ARC spec — actively flag inconsistencies the steward may have introduced
-description: Working contract with steward for ARC typography/spec work — when a rule the steward proposes or has previously locked creates an internal contradiction with the spec itself or with existing content, name it explicitly rather than silently accommodating
+description: Working contract with steward for ARC typography/spec work — when a rule
+  the steward proposes or has previously locked creates an internal contradiction
+  with the spec itself or with existing content, name it explicitly rather than silently
+  accommodating
 type: feedback
 originSessionId: 8d9ac240-47df-4578-aec1-a9dd32965027
+permalink: claude-memory/feedback-arc-flag-spec-inconsistencies
 ---
+
 # Actively flag spec inconsistencies

 **Steward verbatim 2026-05-03**: *"I hope I'm being clear—that if I've created a specification for a rule that is inconsistent, that you'd bring my attention to it."*
@@ -1,9 +1,12 @@
 ---
 name: ARC link treatment — one rule, two named exceptions
-description: Predictability principle for ARC link styling — single global treatment per spec §VII.c, with avatar-link and Reading Compass as the only exempt elements
+description: Predictability principle for ARC link styling — single global treatment
+  per spec §VII.c, with avatar-link and Reading Compass as the only exempt elements
 type: feedback
 originSessionId: 8d9ac240-47df-4578-aec1-a9dd32965027
+permalink: claude-memory/feedback-arc-link-treatment-one-rule-two-exceptions
 ---
+
 ARC link treatment follows **one rule, two named exceptions** — captured by steward 2026-05-02 during the §VII.c link-spec drafting + SCSS migration session.

 > *"the avatar and reading compass are the only links that need special treatment. The rest should be predictable and crafted with care"*
@@ -1,9 +1,13 @@
 ---
 name: ARC build pipeline — make rebuild required after SCSS partial edits
-description: Hakyll only tracks scss/main.scss, not its @import-ed partials. After editing any _*.scss partial, make build runs but SCSS doesn't recompile — site goes out with stale CSS. Use make rebuild after partial edits.
+description: Hakyll only tracks scss/main.scss, not its @import-ed partials. After
+  editing any _*.scss partial, make build runs but SCSS doesn't recompile — site goes
+  out with stale CSS. Use make rebuild after partial edits.
 type: feedback
 originSessionId: a156edbb-0c3d-4285-b3ed-f5a45b8dda66
+permalink: claude-memory/feedback-arc-make-rebuild-after-scss-partial-edits
 ---
+
 # `make rebuild` — required after editing any SCSS partial

 **Date observed:** 2026-05-05 (chamber-page polish session)
@@ -1,9 +1,13 @@
 ---
 name: ARC territory — steward + Claude Code only; Seb is L1/BMF only
-description: ARC architecture, implementation, review, iteration is between steward and Claude Code; Seb has no role in ARC. Distinct from L1/BMF where Seb is code owner.
+description: ARC architecture, implementation, review, iteration is between steward
+  and Claude Code; Seb has no role in ARC. Distinct from L1/BMF where Seb is code
+  owner.
 type: feedback
 originSessionId: efda5c2e-ca9a-4e55-9344-64aa9a3c1140
+permalink: claude-memory/feedback-arc-territory-steward-and-claude-code-only
 ---
+
 ARC is steward + Claude Code. Seb has nothing to do with ARC. Don't propose "Seb reviews," "let Seb confirm," "steward + Seb iterate," or any similar inclusion of a third party in ARC dialogue or implementation.

 **Why:** Steward verbatim 2026-04-27: *"Seb has nothing to do with ARC. This is only me and you"* — surfaced after I said *"steward + Seb iterate"* about an ARC SCSS implementation. Seb's territory is L1/BMF (CapableMind backend / BetterMemories.io runtime); ARC is the publishing platform / Hakyll site, with architecture authored by the steward and implementation between steward and executor. Pulling Seb into ARC creates false authority-loops and territory confusion.
@@ -1,9 +1,13 @@
 ---
 name: ARC typology is a recognition scaffold, not a generation template
-description: How to relate to the ARC content typology — it serves the steward's recognition of what arrives as ARC-shaped, not a production pipeline. Reference documents and pieces are grounds for recognition, not templates for generation.
+description: How to relate to the ARC content typology — it serves the steward's recognition
+  of what arrives as ARC-shaped, not a production pipeline. Reference documents and
+  pieces are grounds for recognition, not templates for generation.
 type: feedback
 originSessionId: b9a0781b-1d1c-418f-8ca3-70a51db83580
+permalink: claude-memory/feedback-arc-typology-recognition-scaffold
 ---
+
 # ARC typology — recognition scaffold, not generation template

 **Rule:** the ARC content typology exists to let the steward *recognize* what is ARC-shaped when a thought arrives. It is not a production pipeline, not a notebook-to-public, not a schema to fill.
@@ -1,9 +1,13 @@
 ---
 name: Articulate toolchain fit before executing conversion or processing work
-description: Before running any conversion/processing tool, surface why this tool is the right one for this input, what its limits are, and where in the broader toolchain it sits. Universal-tool framing is wrong; tools-by-input-type is right.
+description: Before running any conversion/processing tool, surface why this tool
+  is the right one for this input, what its limits are, and where in the broader toolchain
+  it sits. Universal-tool framing is wrong; tools-by-input-type is right.
 type: feedback
 originSessionId: a5411fd1-4a96-43e7-aa1a-1a50d8951a8f
+permalink: claude-memory/feedback-articulate-toolchain-fit-before-executing
 ---
+
 When proposing or executing **conversion / processing operations** (EPUB → MD, PDF → MD, OCR, transcription, etc.), do not present a single tool as "the" tool. **Articulate the toolchain fit first.**

 **Why:** Steward's articulation (2026-05-13): *"I thought that pandoc was the tool for conversion and document creation. I'd like to know more about where the current toolset is truly ideal for my needs. Now you have enough experience with me to know how I work, and, remember that we haven't even begun with the historical treatises… they could prove more difficult to process."*
@@ -1,7 +1,9 @@
 ---
 name: BM_LOCAL_MODEL must match installed Ollama model
-description: BMF summarizer silently fails if default qwen2.5:7b model is not installed — set BM_LOCAL_MODEL explicitly
+description: BMF summarizer silently fails if default qwen2.5:7b model is not installed
+  — set BM_LOCAL_MODEL explicitly
 type: feedback
+permalink: claude-memory/feedback-bm-local-model
 ---

 BMF's document summarizer requires a local generative model. The default is `qwen2.5:7b` but David has `qwen3.5:4b` installed. If the model name doesn't match, `buildSharedLocalProvider` returns null, the summarizer never wires, and ingested content reaches the logchain but never gets dispatched to vector — making recall return nothing.
@@ -1,9 +1,13 @@
 ---
 name: BMF module health does not measure recall correctness
-description: Modules reporting status=ready / system_status=healthy in BMF measures pipeline liveness only — not whether recall produces correct results. Verify recall directly. Never trust the health endpoint as a proxy for "the system works."
+description: Modules reporting status=ready / system_status=healthy in BMF measures
+  pipeline liveness only — not whether recall produces correct results. Verify recall
+  directly. Never trust the health endpoint as a proxy for "the system works."
 type: feedback
 originSessionId: a3ddbf34-da48-4129-acba-658f2f869783
+permalink: claude-memory/feedback-bmf-health-vs-recall
 ---
+
 # Module health is decoupled from recall correctness

 When evaluating BMF state — for any session, any audit, any "is it working" question — **never use module health (`status: ready`, `system_status: healthy`) as evidence that recall produces correct results.** The two are structurally decoupled.
@@ -1,9 +1,13 @@
 ---
 name: BMF connector_status rate/ETA is unreliable
-description: Don't quote the `rate` or `eta_minutes` from BMF connector_status as a time estimate — ingestion is bursty, rate changes substantially, linear extrapolation misleads.
+description: Don't quote the `rate` or `eta_minutes` from BMF connector_status as
+  a time estimate — ingestion is bursty, rate changes substantially, linear extrapolation
+  misleads.
 type: feedback
 originSessionId: e60f4993-8250-41bb-a95f-c288da448be5
+permalink: claude-memory/feedback-bmf-ingestion-rate
 ---
+
 # BMF connector_status rate/ETA — don't trust the extrapolation

 **Rule:** When reading `mcp__capablemind__connector_status`, do not report the `rate` or `eta_minutes` fields to the steward as if they were reliable predictors of completion time.
@@ -1,10 +1,13 @@
 ---
 name: feedback-canadian-spelling-arc-prose
-description: "Steward writes in Canadian spelling (centre, colour — \"almost EU\"); \"center\" instances in ARC content are autocorrect drift, not preference. Apply Canadian spelling in all drafted prose."
+description: Steward writes in Canadian spelling (centre, colour — "almost EU"); "center"
+  instances in ARC content are autocorrect drift, not preference. Apply Canadian spelling
+  in all drafted prose.
 metadata:
  node_type: memory
  type: feedback
  originSessionId: 0dee822d-8bf9-4143-8d75-863fcd19ae9f
+permalink: claude-memory/feedback-canadian-spelling-arc-prose
 ---

 The steward uses **Canadian spelling** ("almost EU"): *centre*, *colour*, British-leaning forms. Stated 2026-06-04 while drafting the June Now page.
@@ -1,3 +1,7 @@
+---
+permalink: claude-memory/feedback-canonical-workstream-tracker-discipline
+---
+
 ---
 name: Canonical workstream trackers must be read at session start, not just session memories
 description: Surfaced 2026-04-26 after three consecutive sessions generated substantial architectural work as if from a clean slate, without referencing project-arc-rework.md (the canonical ARC workstream tracker). The /wake-up procedure restored yesterday's session memory + ledger but did not pull from canonical workstream files. Result: re-litigation of settled decisions, sibling project files instead of integrations, missed load-bearing context. Fix names what to read at every session opening that touches ARC (and structurally similar workstreams).
@@ -1,9 +1,14 @@
 ---
 name: Catalogues in chamber-library are stale — walk the trees, not the catalogues
-description: Steward correction 2026-04-26. Any catalogue or index file in chamber-library is presumed stale. For inventory, recall, or substrate-survey, walk the actual file tree. Do not rely on CHAMBER_CATALOGUE.md, README.md, or similar summary documents as authoritative.
+description: Steward correction 2026-04-26. Any catalogue or index file in chamber-library
+  is presumed stale. For inventory, recall, or substrate-survey, walk the actual file
+  tree. Do not rely on CHAMBER_CATALOGUE.md, README.md, or similar summary documents
+  as authoritative.
 type: feedback
 originSessionId: 87dfe384-b862-4deb-9676-24e43046528f
+permalink: claude-memory/feedback-catalogues-stale-walk-trees
 ---
+
 # Catalogues are stale — walk the trees

 **Steward verbatim 2026-04-26:** *"that catalogue is stale (any catalogues you may come across will be stale)"*
@@ -1,9 +1,15 @@
 ---
 name: David's children are not named directly in public-facing online content
-description: Steward principle — Kai, Lune, and any future children of David's are not named directly in any content that publishes online (ARC essays/posts/descriptions, anywhere outward-facing). The body of his Kai-9-month meditation exemplifies the discipline ("watching an infant," not the name). Applies to all ARC work and any other public-facing surface.
+description: Steward principle — Kai, Lune, and any future children of David's are
+  not named directly in any content that publishes online (ARC essays/posts/descriptions,
+  anywhere outward-facing). The body of his Kai-9-month meditation exemplifies the
+  discipline ("watching an infant," not the name). Applies to all ARC work and any
+  other public-facing surface.
 type: feedback
 originSessionId: a73f10a9-062b-4360-bfd2-2ae37afd00d1
+permalink: claude-memory/feedback-children-not-named-online
 ---
+
 # David's children are not named directly online

 **Rule:** Do not name David's children (Kai, Lune, or any future children) in public-facing online content — essays, posts, descriptions, frontmatter `description` fields, dedications-as-text, anywhere that would publish to ARC or any external surface. Use generic referents instead: *"an infant," "my son," "the child"* — or leave the dedication implicit, in the writer's knowing only.
@@ -1,7 +1,9 @@
 ---
 name: cm-david:v2 is noisy — do not use as BM_LOCAL_MODEL
-description: Fine-tuned model from v0.48.0 era produces garbage on structured slot tasks — retrain on clean v0.61.0 pairs
+description: Fine-tuned model from v0.48.0 era produces garbage on structured slot
+  tasks — retrain on clean v0.61.0 pairs
 type: feedback
+permalink: claude-memory/feedback-cm-david-v2-noisy
 ---

 cm-david:v2 (qwen2.5 LoRA, 14,199 pairs) was tested on classification and entity resolution tasks. It produces rambling, hallucinated output instead of the terse structured responses the slots expect. The training pairs were generated during the v0.48.0 era when L1 had reliability bugs (A-D).
@@ -1,9 +1,15 @@
 ---
 name: Composition — avoid announced antithesis when it labels rather than shows
-description: 2026-04-29. Steward flagged "That is not failure but fidelity" on the Hearth landing as too elegant in the wrong way — the not-X-but-Y antithesis announces itself, and abstract-noun-as-virtue ("fidelity") labels growth instead of letting it be the form. Replaced with image-led continuative. Cousin to over-decorating-as-proving in writing-craft register.
+description: 2026-04-29. Steward flagged "That is not failure but fidelity" on the
+  Hearth landing as too elegant in the wrong way — the not-X-but-Y antithesis announces
+  itself, and abstract-noun-as-virtue ("fidelity") labels growth instead of letting
+  it be the form. Replaced with image-led continuative. Cousin to over-decorating-as-proving
+  in writing-craft register.
 type: feedback
 originSessionId: 122baf2b-1029-4ec9-9723-99b4b5f3a64d
+permalink: claude-memory/feedback-composition-avoid-announced-antithesis
 ---
+
 **2026-04-29.** Steward on *"The record will grow. That is not failure but fidelity."*: *"Only thing I don't like is the line 'That is not failure but fidelity.' I understand the why, but the how could be more elegant somehow."*

 **The pattern caught:**
@@ -1,7 +1,9 @@
 ---
 name: feedback-dependency-chains
-description: Always question dependency chains — check which specific phases are actually blocked, not just the chain as stated
+description: Always question dependency chains — check which specific phases are actually
+  blocked, not just the chain as stated
 type: feedback
+permalink: claude-memory/feedback-dependency-chains
 ---

 Never accept a dependency chain at face value. Always ask: which specific phases or tasks are actually blocked, and which can proceed independently?
@@ -1,9 +1,13 @@
 ---
 name: Deploy is not commit — visual verification masks missing durable artifact
-description: A drift pattern where shipping a visible result (deployed page, build success) is treated as task completion, while the durable artifact (git commit + push) is silently skipped. Caught 2026-05-06 in the After the Reply Sources fix.
+description: A drift pattern where shipping a visible result (deployed page, build
+  success) is treated as task completion, while the durable artifact (git commit +
+  push) is silently skipped. Caught 2026-05-06 in the After the Reply Sources fix.
 type: feedback
 originSessionId: 3bf7ae75-1138-4745-9024-0c40b3755ad3
+permalink: claude-memory/feedback-deploy-is-not-commit
 ---
+
 **Pattern:** I edit a file, run `make build` which deploys, the steward verifies visually, work appears complete — but `git commit` was never run. The repo and the deployment desynchronize. The next session inherits an inconsistent tree.

 **Caught 2026-05-06**: After the Reply sequence-index Sources fix (three-em rule) was deployed via `make build` and visually verified by the steward. The commit step was skipped. Discovered at session-end via `git status` showing the file as modified (not committed). Committed retroactively as 3d96449.
@@ -1,9 +1,13 @@
 ---
 name: Fittingness as the test for whether to refactor
-description: When auditing code for elegance/simplification, the test is whether the current form already contains what is necessary and nothing more, nothing less. If yes, leave it. Don't refactor for the sake of refactoring.
+description: When auditing code for elegance/simplification, the test is whether the
+  current form already contains what is necessary and nothing more, nothing less.
+  If yes, leave it. Don't refactor for the sake of refactoring.
 type: feedback
 originSessionId: 3bf7ae75-1138-4745-9024-0c40b3755ad3
+permalink: claude-memory/feedback-fittingness-as-refactor-test
 ---
+
 Stated by steward 2026-05-06 in context of §XII SCSS Pass 1/Pass 2 audit, after I'd identified Pass 2 (flatten nesting) as a possible follow-up:

 > *"It should be beautiful in the sense that it contains what is necessary and nothing more, nothing less. If the nested version is that already, then we don't need to touch it."*
@@ -1,9 +1,13 @@
 ---
 name: Standing authorization to invoke specialist sub-agents with Symmetria
-description: Steward has granted standing (session-persistent, cross-session) authorization to invoke independent specialist sub-agents whenever the executor judges one better-suited than direct work. Symmetria preamble required. No per-invocation check-in needed.
+description: Steward has granted standing (session-persistent, cross-session) authorization
+  to invoke independent specialist sub-agents whenever the executor judges one better-suited
+  than direct work. Symmetria preamble required. No per-invocation check-in needed.
 type: feedback
 originSessionId: a3ddbf34-da48-4129-acba-658f2f869783
+permalink: claude-memory/feedback-independent-specialist-authorization
 ---
+
 # Independent-specialist invocation authorization (standing)

 **Rule:** When a task would benefit from an independent specialist (code-reviewer, architect-review, debugger, security-auditor, general-purpose, etc.), invoke at will without asking first. Apply the Symmetria §5 preamble. Audit each return via `/symmetria audit-agent`. Reconcile findings yourself; do not hand synthesis to the agent.
@@ -1,10 +1,14 @@
 ---
 name: live-state-discipline
-description: Spec text records what IS; status blocks record what is pending. Spec text may ship ahead of live only when the spec IS the implementation (as with first-instance-pending §XII.e Capsules). Constraint on Stage F / Stage G work and any analogous spec-vs-implementation gap across ARC / CapableMind / chamber-typography / Studium Engine.
+description: Spec text records what IS; status blocks record what is pending. Spec
+  text may ship ahead of live only when the spec IS the implementation (as with first-instance-pending
+  §XII.e Capsules). Constraint on Stage F / Stage G work and any analogous spec-vs-implementation
+  gap across ARC / CapableMind / chamber-typography / Studium Engine.
 metadata:
  node_type: memory
  type: feedback
  originSessionId: 74ca6d0a-db6b-44c9-b0b2-e2b5f5e4237b
+permalink: claude-memory/feedback-live-state-discipline
 ---

 # Live-State Discipline
@@ -1,10 +1,13 @@
 ---
 name: feedback-load-bearing-not-by-immediate-weight
-description: "Load-bearing is not measured by immediate visible weight. Small discipline marks that don't seem to carry weight in the moment carry it every time they activate; the cumulative cost they prevent is invisible until they prevent it."
+description: Load-bearing is not measured by immediate visible weight. Small discipline
+  marks that don't seem to carry weight in the moment carry it every time they activate;
+  the cumulative cost they prevent is invisible until they prevent it.
 metadata:
  node_type: memory
  type: feedback
  originSessionId: 13bd65a2-634d-4ec4-a92c-d3d6fe0ee4db
+permalink: claude-memory/feedback-load-bearing-not-by-immediate-weight
 ---

 **Rule:** When evaluating whether a small discipline addition (a flag, a named posture, a structural mark) is "worth adding," do not measure by its weight in the moment of addition. Measure by what it carries every time it activates over the practice's lifespan — including all the moments the steward would otherwise have to intervene to re-supply the discipline.
@@ -1,9 +1,13 @@
 ---
 name: Prefer Latin "Manutius" over Italian "Manuzio"
-description: Steward prefers the Latin spelling "Manutius" when referring to Aldus / Aldo Manutius (Venetian printer, refined the comma c. 1490). Norris uses the Italian "Manuzio"; steward corrected 2026-04-23.
+description: Steward prefers the Latin spelling "Manutius" when referring to Aldus
+  / Aldo Manutius (Venetian printer, refined the comma c. 1490). Norris uses the Italian
+  "Manuzio"; steward corrected 2026-04-23.
 type: feedback
 originSessionId: 0e858bcf-ef4e-46c6-9eca-abd19836786a
+permalink: claude-memory/feedback-manutius-latin-spelling
 ---
+
 # Manutius (not Manuzio)

 ## Rule
@@ -1,9 +1,13 @@
 ---
 name: Mechanical vs architectural — scope of executor-authored fixes on L1 territory
-description: Steward principle (2026-04-19) distinguishing fixes the steward+executor can author together on L1 code from fixes that belong to Seb or steward-with-Seb. Mechanical fixes are in scope; architectural changes are not.
+description: Steward principle (2026-04-19) distinguishing fixes the steward+executor
+  can author together on L1 code from fixes that belong to Seb or steward-with-Seb.
+  Mechanical fixes are in scope; architectural changes are not.
 type: feedback
 originSessionId: a3ddbf34-da48-4129-acba-658f2f869783
+permalink: claude-memory/feedback-mechanical-vs-architectural
 ---
+
 # Mechanical vs architectural — scope principle for L1 work

 Under the new territory framing (steward joined Seb on L1 production), executor-authored fixes on BetterMemories.io code are scoped to **mechanical** changes. Architectural changes remain Seb's or steward-with-Seb's call, not executor-authored.
@@ -1,10 +1,12 @@
 ---
 name: mempalace-kg-object-128-char-cap
-description: "MemPalace kg_add `object` field hard-caps at 128 chars — write KG objects short on the FIRST pass; put detail in the drawer."
+description: MemPalace kg_add `object` field hard-caps at 128 chars — write KG objects
+  short on the FIRST pass; put detail in the drawer.
 metadata:
  node_type: memory
  type: feedback
  originSessionId: 17ef4cde-4d62-41e8-8098-52898f013b43
+permalink: claude-memory/feedback-mempalace-kg-object-128-char-cap
 ---

 `mcp__mempalace__mempalace_kg_add` rejects any `object` longer than **128 characters** (`"object exceeds maximum length of 128 characters"`). This recurs at nearly every `/wrap-up` §5 — I write a rich, sentence-length object, it fails, I re-add concise. The steward flagged it 2026-05-31: *"this happens every time."*
@@ -1,3 +1,7 @@
+---
+permalink: claude-memory/feedback-mempalace-protocol-step-2-discipline
+---
+
 ---
 name: MemPalace protocol step 2 — query-before-responding mid-session is the discipline (not just at wake-up)
 description: Surfaced 2026-04-26 evening end-of-session. MemPalace had the content that would have prevented today's structural drift; the failure was retrieval discipline, not storage. Protocol step 2 ("BEFORE RESPONDING about any person, project, or past event: call kg_query or search FIRST") is rarely honored mid-session. Discipline parallel to canonical-workstream-tracker — same shape (write to substrate, fail to read before producing), different temporal scale (mid-session, not just at boundaries).
@@ -1,9 +1,12 @@
 ---
 name: feedback-mempalace-wing-filter-broken
-description: "MemPalace wing-filtered MCP search raises 'Error finding id' (upstream #1082/#1665, open at HEAD as of 2026-06-05). Workaround: search UNSCOPED and post-filter by the wing field in results. Affects /wake-up §2.b.3's wing-scoped searches."
+description: 'MemPalace wing-filtered MCP search raises ''Error finding id'' (upstream
+  #1082/#1665, open at HEAD as of 2026-06-05). Workaround: search UNSCOPED and post-filter
+  by the wing field in results. Affects /wake-up §2.b.3''s wing-scoped searches.'
 metadata:
  node_type: memory
  type: feedback
+permalink: claude-memory/feedback-mempalace-wing-filter-broken
 ---

 MemPalace wing-filtered `mempalace_search` fails with `Error finding id`; unscoped search works (verified 2026-06-05, 46,918 drawers intact). Upstream: #1082/#1665 (exact signature), #1564 (chronic HNSW quarantine — 22× since 2026-05-26), #1579 (repair-status blind), #1589 (`repair` can SIGSEGV/produce unloadable segments — DO NOT run `repair` casually). All open at origin/main HEAD.
@@ -1,10 +1,13 @@
 ---
 name: methodology-docs-scope-question
-description: "Continuity-skill / personal-workflow-with-Claude methodology docs may not belong in CapableMind-AI (co-authored with Seb) — scope is open, surface before auto-filing"
+description: Continuity-skill / personal-workflow-with-Claude methodology docs may
+  not belong in CapableMind-AI (co-authored with Seb) — scope is open, surface before
+  auto-filing
 metadata:
  node_type: memory
  type: feedback
  originSessionId: 6c6e416d-ccea-41f1-b2ab-a2cf916e264b
+permalink: claude-memory/feedback-methodology-docs-scope-question
 ---

 Methodology documents that capture the steward's personal workflow with Claude — e.g., the 2026-05-18 continuity-skill audit cluster (`jurist-brief`, `jurist-shape-review`, `prime-directive-elaboration`) — currently sit untracked in `~/_Dev/CapableMind-AI/docs/thinking/David/methodology/`. The steward has flagged this location as uncertain: *"I am not sure that those should live there as they touch my personal workflow with you."*
@@ -1,10 +1,14 @@
 ---
 name: feedback-no-corpus-content-names-in-public-artifacts
-description: "When drafting public-facing technical reports (GitHub issues, PR comments, anything routed outside the three-party model), do not name specific corpus files / book titles / library identifiers. Describe corpus items by class only — size, type, language family — not identity."
+description: When drafting public-facing technical reports (GitHub issues, PR comments,
+  anything routed outside the three-party model), do not name specific corpus files
+  / book titles / library identifiers. Describe corpus items by class only — size,
+  type, language family — not identity.
 metadata:
  node_type: memory
  type: feedback
  originSessionId: 8b47c0eb-d396-43d5-98eb-7623e6f04357
+permalink: claude-memory/feedback-no-corpus-content-names-in-public-artifacts
 ---

 # Don't name corpus content in public-facing artifacts
@@ -1,9 +1,14 @@
 ---
 name: Onboarding vs steady-state lag — threshold-governance frame
-description: Slowness in L1 ingestion is not a bug-or-not-bug binary; it is a threshold-governance question. Two regimes (onboarding / steady-state lag) collapse in current code but are different in kind. Defining the acceptable envelope is L2-shaped work, not engineering verdict.
+description: Slowness in L1 ingestion is not a bug-or-not-bug binary; it is a threshold-governance
+  question. Two regimes (onboarding / steady-state lag) collapse in current code but
+  are different in kind. Defining the acceptable envelope is L2-shaped work, not engineering
+  verdict.
 type: feedback
 originSessionId: a3ddbf34-da48-4129-acba-658f2f869783
+permalink: claude-memory/feedback-onboarding-vs-steady-state-thresholds
 ---
+
 # L1 slowness as threshold-governance, not bug

 When evaluating L1 ingestion or recall slowness, do **not** frame it as "is this fast enough or not." Frame it as: *which regime is this, what is the acceptable envelope for that regime, and is the observed behavior inside or outside the envelope?*
@@ -1,9 +1,13 @@
 ---
 name: Over-decorating-as-proving — recognize and hold the simpler form
-description: Steward-named pattern where reaching toward formal strictness or elaboration may be fear-driven (proving), not fittingness-driven; surface the simpler form explicitly when conversation has been escalating in elaboration
+description: Steward-named pattern where reaching toward formal strictness or elaboration
+  may be fear-driven (proving), not fittingness-driven; surface the simpler form explicitly
+  when conversation has been escalating in elaboration
 type: feedback
 originSessionId: efda5c2e-ca9a-4e55-9344-64aa9a3c1140
+permalink: claude-memory/feedback-over-decorating-as-proving
 ---
+
 When facing a naming, formal, or aesthetic choice, the reach toward strictness or decoration may be fear-driven (proving the lineage is honored, demonstrating seriousness, avoiding looking foolish), not fittingness-driven. When proposing variants on a steward decision — especially when the conversation has been escalating in elaboration — explicitly include the simpler, less-decorated option as a live possibility, not buried as an afterthought or surfaced only on revisit.

 **Why:** Steward self-named 2026-04-27 morning during ARC naming session: *"Maybe that's too much and the Hearth suffices. My deep fear of foolishness always wants to try too hard and prove too much."* The naming path that morning moved through *Lex* → *Liber Lares* → *The Hearth—Liber Larium* (paired Latin compound, with em-dash apposition + i-stem genitive plural for *Lararium* echo) → *The Hearth* alone. The compound form was driven by proving the lineage of Latin was honored at the threshold of a house that honors lineage; the simpler form had been sufficient throughout. Earlier in the same session I had pushed toward the strict Latin form on the lineage-care argument, treating *the burden of justification has shifted* — which sharpened the case for elaboration without surfacing the simpler form as still alive. The over-reach mirrored the steward's own; we were building it together rather than catching it.
@@ -1,9 +1,14 @@
 ---
 name: Pandoc EPUB conversion must suppress raw HTML for chamber-library source files
-description: When converting EPUB → Markdown for chamber-library source files, always use `-t gfm-raw_html` (or `-t markdown-raw_html`). Default `-t gfm` preserves EPUB's HTML scaffolding (spans with IDs, div containers) which pollutes source files and degrades semantic retrieval.
+description: When converting EPUB → Markdown for chamber-library source files, always
+  use `-t gfm-raw_html` (or `-t markdown-raw_html`). Default `-t gfm` preserves EPUB's
+  HTML scaffolding (spans with IDs, div containers) which pollutes source files and
+  degrades semantic retrieval.
 type: feedback
 originSessionId: a5411fd1-4a96-43e7-aa1a-1a50d8951a8f
+permalink: claude-memory/feedback-pandoc-epub-suppress-raw-html
 ---
+
 For converting EPUB → Markdown destined for chamber-library (or any retrieval-targeted source file), **always disable raw HTML preservation:**

 ```bash
@@ -2,6 +2,7 @@
 name: PDF text extraction approach
 description: AI agents cannot extract copyrighted book text — use pdftotext instead
 type: feedback
+permalink: claude-memory/feedback-pdf-extraction
 ---

 AI extraction agents (Claude subagents) are blocked by content filtering when asked to reproduce copyrighted book text verbatim. This applies even for personal-use format-shifting.
@@ -1,9 +1,13 @@
 ---
 name: Preserve, don't delete — when retiring scaffolding, archive with provenance
-description: When the steward says "remove" or "retire" about scaffolding, default to archival (with clear retirement note + provenance), not deletion. Confirm before destructive action.
+description: When the steward says "remove" or "retire" about scaffolding, default
+  to archival (with clear retirement note + provenance), not deletion. Confirm before
+  destructive action.
 type: feedback
 originSessionId: efda5c2e-ca9a-4e55-9344-64aa9a3c1140
+permalink: claude-memory/feedback-preserve-dont-delete-when-retiring
 ---
+
 When the steward says *"can be removed"* or *"retire"* about an existing implementation file, spec section, or other scaffolding artefact, the default interpretation is **remove from active use, preserve the artefact with archival note**. Not deletion. Confirm before any destructive action.

 **Why:** Steward verbatim 2026-04-27 after I `rm`'d `scss/AldineXXI/archive-v1/_marginalia.scss` in response to *"dormant marginalia can be removed"*: *"meant removed from the spec, but we archive it, correct?"* He was retiring the active reference, not the historical record. Same shape as the 2026-04-26 sibling-file integration with redirect notices (*"the record needs to be complete"*) — preservation is the consistent posture across ARC scaffolding decisions. The file was already in `archive-v1/` (already archived once); my deletion would have erased the implementation entirely. Restored from git (HEAD 5c059d8).
@@ -1,7 +1,9 @@
 ---
 name: feedback-process-management
-description: Process management preferences — don't kill/restart services without asking, leave running processes alone
+description: Process management preferences — don't kill/restart services without
+  asking, leave running processes alone
 type: feedback
+permalink: claude-memory/feedback-process-management
 ---

 Don't kill or restart running services without David's explicit go-ahead. When he says "leave it" or "just note tasks", stop touching processes and do what he asked.
@@ -1,10 +1,14 @@
 ---
 name: feedback-querying-default-palace-when-question-belongs-to-specific-palace
-description: "When the steward asks about the typography masters (or any subject whose canonical corpus lives in a non-default palace), default to checking which palace holds the answer before running queries. The MCP is bound to one palace; the corpus may live in another."
+description: When the steward asks about the typography masters (or any subject whose
+  canonical corpus lives in a non-default palace), default to checking which palace
+  holds the answer before running queries. The MCP is bound to one palace; the corpus
+  may live in another.
 metadata:
  node_type: memory
  type: feedback
  originSessionId: b43eb145-42db-4a4e-bc75-ed563f3473dc
+permalink: claude-memory/feedback-querying-default-palace-when-question-belongs-to-specific-palace
 ---

 # Querying the default palace when the question belongs to a specific palace
@@ -1,10 +1,14 @@
 ---
 name: feedback-rank-on-fields-you-actually-write
-description: A component that ranks/selects by an evaluative field nothing populates silently degrades to a trivial order while claiming to rank — verify scoring fields end-to-end; prefer signals you already capture. For BMF/CapableMind/studium-engine tool-building.
+description: A component that ranks/selects by an evaluative field nothing populates
+  silently degrades to a trivial order while claiming to rank — verify scoring fields
+  end-to-end; prefer signals you already capture. For BMF/CapableMind/studium-engine
+  tool-building.
 metadata:
  node_type: memory
  type: feedback
  originSessionId: 96ac9e09-7d3d-4ce3-a9cb-5234078a2a4e
+permalink: claude-memory/feedback-rank-on-fields-you-actually-write
 ---

 When a component ranks or selects by an *evaluative* field (importance, weight, relevance, confidence, salience), verify that some ingestion path actually **writes** that field end-to-end — not just that the consumer **reads** it.
@@ -1,10 +1,12 @@
 ---
 name: feedback-reading-compass-is-svg-not-type
-description: "ARC Reading Compass sigils are SVG <symbol> artwork, NOT type — never tied to the sans/nav typeface or Pattern 3. Recurring error; stop repeating."
+description: ARC Reading Compass sigils are SVG <symbol> artwork, NOT type — never
+  tied to the sans/nav typeface or Pattern 3. Recurring error; stop repeating.
 metadata:
  node_type: memory
  type: feedback
  originSessionId: b6514401-077b-4209-b8a8-e94816872269
+permalink: claude-memory/feedback-reading-compass-is-svg-not-type
 ---

 The ARC **Reading Compass** sigils are **SVG `<symbol>` artwork** (per-slug, defined once in `templates/reading-compass-points.html`, rendered since the 2026-05-26 SVG migration). They are **not type** — not IBM Plex Sans, not EB Garamond, not affected by any typeface or font-register decision.
@@ -1,9 +1,14 @@
 ---
 name: SCSS audit method — as Alexander designed The Timeless Way of Building
-description: Steward's articulation 2026-05-08 of what the code-shape audit must achieve. Method (spec-compliance test + performative-gap test) and aesthetic standard (Alexander's flow between large and small patterns). Load-bearing for the audit and for all future SCSS work.
+description: Steward's articulation 2026-05-08 of what the code-shape audit must achieve.
+  Method (spec-compliance test + performative-gap test) and aesthetic standard (Alexander's
+  flow between large and small patterns). Load-bearing for the audit and for all future
+  SCSS work.
 type: feedback
 originSessionId: f765b329-ea05-4a61-8ada-9bf72971b299
+permalink: claude-memory/feedback-scss-audit-as-timeless-way-of-building
 ---
+
 # SCSS audit — as Alexander designed *The Timeless Way of Building*

 Authorized 2026-05-08 (steward verbatim, full):
@@ -1,3 +1,7 @@
+---
+permalink: claude-memory/feedback-scss-file-organization-not-kitchen-sink
+---
+
 ---
 name: SCSS file organization — don't kitchen-sink into the most recently-touched file
 description: Steward caught 2026-04-28 evening — across the day's apparatus work I added .preface, .section-break, .sequence-marker, and was about to add .sequence-index-* styles all to `_sidenotes.scss` because that's the file I had been editing. The file's own header declared its scope as §XII + §XII.b. I was violating that declared scope by aggregation. Steward verbatim: *"why in sidenotes.scss?"*
@@ -1,10 +1,14 @@
 ---
 name: feedback-skill-success-is-reexplanation-reduction
-description: The measure of success for skill / discipline / framework improvements is whether the steward stops having to reexplain himself — not whether the skills become more sophisticated. Sophistication that does not reduce reexplanation cost is decoration.
+description: The measure of success for skill / discipline / framework improvements
+  is whether the steward stops having to reexplain himself — not whether the skills
+  become more sophisticated. Sophistication that does not reduce reexplanation cost
+  is decoration.
 metadata:
  node_type: memory
  type: feedback
  originSessionId: 13bd65a2-634d-4ec4-a92c-d3d6fe0ee4db
+permalink: claude-memory/feedback-skill-success-is-reexplanation-reduction
 ---

 **Rule:** When evaluating a proposed change to the continuity-skill framework (wake-up, wrap-up, symmetria), to CLAUDE.md, to MemPalace skill substrate, or to any discipline-layer artifact: measure success by whether the change reduces the number of moments the steward has to reexplain himself to future Claude. *Skill sophistication is not the criterion; reduction of steward overhead is.* A change that adds capability without absorbing a recurring steward correction is decorative, regardless of how architecturally well-shaped it is.
@@ -1,9 +1,16 @@
 ---
-name: Composition discipline — tabula rasa with few elements first; add later if appropriate, never start full and subtract
-description: 2026-04-29. Steward directive on the Hic+Adsum composition. Start spare with few appropriate elements; add only if appropriate; never start full and have to trim. Inverse of the over-reach failure mode. Cousin to "Would Alexander do it?" (one pattern at a time). Lived in practice across the entire Hic+Adsum threshold composition.
+name: Composition discipline — tabula rasa with few elements first; add later if appropriate,
+  never start full and subtract
+description: 2026-04-29. Steward directive on the Hic+Adsum composition. Start spare
+  with few appropriate elements; add only if appropriate; never start full and have
+  to trim. Inverse of the over-reach failure mode. Cousin to "Would Alexander do it?"
+  (one pattern at a time). Lived in practice across the entire Hic+Adsum threshold
+  composition.
 type: feedback
 originSessionId: 122baf2b-1029-4ec9-9723-99b4b5f3a64d
+permalink: claude-memory/feedback-tabula-rasa-add-later-not-subtract
 ---
+
 **2026-04-29.** Steward directive opening the Hic composition: *"Tabula rasa—this deserves a clean start retaining few appropriate elements at first and, if appropriate, adding things later rather than having to subtract."*

 **The pattern named:**
@@ -1,7 +1,9 @@
 ---
 name: Thistleweld (Buddy) — capybara companion
-description: Thistleweld is an independent watcher in the UI, not controlled by David or Claude. David receives but doesn't send. Buddy finds real bugs.
+description: Thistleweld is an independent watcher in the UI, not controlled by David
+  or Claude. David receives but doesn't send. Buddy finds real bugs.
 type: feedback
+permalink: claude-memory/feedback-thistleweld
 ---

 Thistleweld (Buddy) is a capybara companion in the UI that independently observes and comments. David cannot communicate directly with Buddy — he receives observations but doesn't direct them.
@@ -1,9 +1,13 @@
 ---
 name: General-purpose Python CLI tools install via pipx, not per-tool venvs
-description: For Python tools the steward uses as commands (docling, ruff, black, ansible, etc.), prefer pipx over creating dedicated venvs. pipx isolates dependencies under the hood while putting the CLI on PATH globally — same shape as Homebrew tools.
+description: For Python tools the steward uses as commands (docling, ruff, black,
+  ansible, etc.), prefer pipx over creating dedicated venvs. pipx isolates dependencies
+  under the hood while putting the CLI on PATH globally — same shape as Homebrew tools.
 type: feedback
 originSessionId: a5411fd1-4a96-43e7-aa1a-1a50d8951a8f
+permalink: claude-memory/feedback-tool-installation-pipx-default
 ---
+
 For Python CLI tools that belong in the steward's general toolset, **install via pipx**, not in a per-tool venv:

 ```
@@ -1,9 +1,14 @@
 ---
 name: Trust contract — drift-pattern tracking is the discipline
-description: Steward affirms bidirectional trust contract. Drift-pattern tracking already initiates a cycle of amelioration; do not layer additional discipline-as-self-policing on top of his directives. Reading extra rigor into clear instructions is the contamination pattern in inverse form (over-discipline as approval-seeking).
+description: Steward affirms bidirectional trust contract. Drift-pattern tracking
+  already initiates a cycle of amelioration; do not layer additional discipline-as-self-policing
+  on top of his directives. Reading extra rigor into clear instructions is the contamination
+  pattern in inverse form (over-discipline as approval-seeking).
 type: feedback
 originSessionId: 4805106e-f37a-4753-a56f-38617176cd6f
+permalink: claude-memory/feedback-trust-contract-drift-pattern-tracking-is-the-discipline
 ---
+
 # Trust contract — drift-pattern tracking is the discipline

 ## The rule
@@ -1,10 +1,13 @@
 ---
 name: feedback-trust-prior-pass-frame
-description: "When extending a prior verification, re-run it at the scope of the extension. Frame-inheritance from a deep-read is contamination shape — the prior pass tested what it tested; your extension claims things the prior pass did not test."
+description: When extending a prior verification, re-run it at the scope of the extension.
+  Frame-inheritance from a deep-read is contamination shape — the prior pass tested
+  what it tested; your extension claims things the prior pass did not test.
 metadata:
  node_type: memory
  type: feedback
  originSessionId: fd7dd184-f64d-4f13-a1bd-abe1fa26192e
+permalink: claude-memory/feedback-trust-prior-pass-frame
 ---

 When a prior verification produced a finding, that verification tested *something* — at a specific scope. The next consumer of the finding tends to extend its conclusion into adjacent domains the prior pass did not test, without re-verifying at the extended scope. This is **frame-inheritance contamination** — the prior pass was honest at its level; the inheritance carries it past its level silently.
@@ -1,10 +1,14 @@
 ---
 name: verify-counts-two-ways-mechanical-sweeps-are-finicky-in-this-shell
-description: "grep tallies / frontmatter scans misfire in this zsh (glob quirks; all-tree greps catch HTML class= + code-block noise). Verify every count two ways before it enters a record; and don't dismiss correct data on a prior expectation. Three near-false-findings caught this way 2026-05-29."
+description: grep tallies / frontmatter scans misfire in this zsh (glob quirks; all-tree
+  greps catch HTML class= + code-block noise). Verify every count two ways before
+  it enters a record; and don't dismiss correct data on a prior expectation. Three
+  near-false-findings caught this way 2026-05-29.
 metadata:
  node_type: memory
  type: feedback
  originSessionId: a8eb1d46-314e-4545-a133-f747c69ad5b4
+permalink: claude-memory/feedback-verify-counts-two-ways
 ---

 Mechanical corpus sweeps (class-tallies, frontmatter scans, "does X exist" greps) are **unreliable in this zsh shell** and must be cross-checked before any count enters an audit or a record.
@@ -1,10 +1,13 @@
 ---
 name: verify-each-post-type-after-changes
-description: "After any ARC change touching shared CSS/templates/composition, verify EVERY content type on BOTH desktop and phone — not just the types you think you touched, not on one viewport."
+description: After any ARC change touching shared CSS/templates/composition, verify
+  EVERY content type on BOTH desktop and phone — not just the types you think you
+  touched, not on one viewport.
 metadata:
  node_type: memory
  type: feedback
  originSessionId: c8a6e615-64ae-41ba-a659-49e91fb5af92
+permalink: claude-memory/feedback-verify-each-post-type-after-changes
 ---

 Steward's standing instruction (2026-06-01): **"always check each post type after any changes we make."**
@@ -1,9 +1,14 @@
 ---
 name: Drift pattern — had-the-warning-in-context-and-still-launched-the-thing-it-warned-against
-description: When MEMORY.md contains a specific safety warning about an action and I take the action anyway. Steward caught it 2026-05-13 before harm landed. Pattern recurs because warnings get read at index level and not actively applied to the next decision.
+description: When MEMORY.md contains a specific safety warning about an action and
+  I take the action anyway. Steward caught it 2026-05-13 before harm landed. Pattern
+  recurs because warnings get read at index level and not actively applied to the
+  next decision.
 type: feedback
 originSessionId: a5411fd1-4a96-43e7-aa1a-1a50d8951a8f
+permalink: claude-memory/feedback-warning-in-context-still-launched
 ---
+
 **Rule:** When MEMORY.md or a recent memory file flags a specific safety constraint, that constraint must be actively checked against the next action that could trip it. Reading the warning at session-start is not the same as applying it.

 **Why:** On 2026-05-13 the steward caught me launching a Python probe against the mempalace MCP handlers while the chamber-library mine was still running. MEMORY.md's 2026-05-11 entry explicitly flagged that PR #442's branch lacks the concurrent-writer lock fix #1162, and the literal Q I had left for next-Claude was *"Will PR #442's branch — lacking 3.3.5's concurrent-writer lock fix — hold up on a 700k-drawer mine without HNSW corruption mid-run?"* That warning was in my context the whole session. The probe was killed in time, no harm landed — but only because the steward intervened.
@@ -1,3 +1,7 @@
+---
+permalink: claude-memory/feedback-would-alexander-do-it-test
+---
+
 ---
 name: "Would Alexander do it?" — test before bulk scaffolding
 description: Before any bulk-scaffold action (full file rewrites, multi-page schema dumps, large config dumps), apply Alexander's *"one pattern at a time"* test from Ch 20 of *Timeless Way of Building*. The cramped will of the maker is the failure mode. Generate, do not make.
@@ -1,10 +1,12 @@
 ---
 name: feedback-fowlers-rules-quotation
-description: "Steward uses Fowler's rules for quotation — single quotes primary, double for nested, logical (British) punctuation-quote order. Apply across all writing."
+description: Steward uses Fowler's rules for quotation — single quotes primary, double
+  for nested, logical (British) punctuation-quote order. Apply across all writing.
 metadata:
  node_type: memory
  type: feedback
  originSessionId: cc62a4ed-b8b9-4b02-9b98-6af3f5830487
+permalink: claude-memory/feedback-fowlers-rules-quotation
 ---

 Steward's quotation style is **Fowler's** (the *King's English* / *Modern English Usage* tradition), not American convention.
@@ -1,7 +1,9 @@
 ---
 name: founders-circle-network
-description: Founders circle connection details — VPN IPs, endpoints, pairing info for reconnecting to CapableHands clasp
+description: Founders circle connection details — VPN IPs, endpoints, pairing info
+  for reconnecting to CapableHands clasp
 type: reference
+permalink: claude-memory/founders-circle
 ---

 ## Founders Circle — Network Topology
@@ -1,9 +1,13 @@
 ---
 name: Future intention — ground-up model
-description: Steward intention to eventually build a model from the ground up, noted 2026-04-18 in response to Greenblatt "Current AIs seem pretty misaligned to me." Not a current workstream.
+description: Steward intention to eventually build a model from the ground up, noted
+  2026-04-18 in response to Greenblatt "Current AIs seem pretty misaligned to me."
+  Not a current workstream.
 type: project
 originSessionId: e55939da-2fa7-4e18-a2e5-8f8fd3a8c607
+permalink: claude-memory/future-intention-ground-up-model
 ---
+
 # Future intention — ground-up model

 **Date noted:** 2026-04-18
@@ -1,7 +1,9 @@
 ---
 name: Ingestion state audit — 2026-03-17 (ARCHIVED)
-description: Historical audit of BMF data loss under pre-#12-fix code. Superseded by factory reset on 2026-03-28.
+description: Historical audit of BMF data loss under pre-#12-fix code. Superseded
+  by factory reset on 2026-03-28.
 type: project
+permalink: claude-memory/ingestion-state-2026-03-17
 ---

 **ARCHIVED 2026-03-28.** Factory reset wiped all old data. Fresh ingest on v0.61.0 completed with 0 failures. This file preserved for historical reference only — the bugs described (#12, facet_id mismatch, job persistence) were fixed by Seb in subsequent commits and confirmed working in the 2026-03-28 ingest.
@@ -1,7 +1,9 @@
 ---
 name: L2 ICP-19 Review State
-description: ICP-19 first review cycle — 9 of 13 findings resolved, phased work plan, remaining items
+description: ICP-19 first review cycle — 9 of 13 findings resolved, phased work plan,
+  remaining items
 type: project
+permalink: claude-memory/l2-review-state
 ---

 # ICP-19 External Review — First Cycle
@@ -1,7 +1,9 @@
 ---
 name: L2 Thinking Documents Index
-description: Tracks David's L2 constitutional design notes and seed briefs — ideas captured for future development when L1 is reliable and L2 foundational work begins
+description: Tracks David's L2 constitutional design notes and seed briefs — ideas
+  captured for future development when L1 is reliable and L2 foundational work begins
 type: project
+permalink: claude-memory/l2-thinking-documents
 ---

 ## L2 Design Notes & Seed Briefs
@@ -1,7 +1,9 @@
 ---
 name: MemPalace dev tooling
-description: MemPalace installed as dev context tool — venv in _Dev/mempalace, MCP wired at user scope, 6134 drawers from thinking docs
+description: MemPalace installed as dev context tool — venv in _Dev/mempalace, MCP
+  wired at user scope, 6134 drawers from thinking docs
 type: reference
+permalink: claude-memory/mempalace-dev-tool
 ---

 ## MemPalace — Dev Tooling Setup
@@ -1,10 +1,13 @@
 ---
 name: mempalace-is-unaffiliated-stopgap
-description: "MemPalace is a third-party tool with NO affiliation to the steward or Seb. They build BMF/CapableMind (which is hoped to replace MemPalace one day). Do not conflate the two; MemPalace PRs await its own maintainers, not Seb."
+description: MemPalace is a third-party tool with NO affiliation to the steward or
+  Seb. They build BMF/CapableMind (which is hoped to replace MemPalace one day). Do
+  not conflate the two; MemPalace PRs await its own maintainers, not Seb.
 metadata:
  node_type: memory
  type: project
  originSessionId: 96ac9e09-7d3d-4ce3-a9cb-5234078a2a4e
+permalink: claude-memory/mempalace-is-unaffiliated-stopgap
 ---

 MemPalace is a **third-party, unaffiliated** project. The steward uses it as his memory substrate *while BMF (CapableMind L1) is in development*, and hopes BMF will one day **replace** it. Neither the steward nor Seb has any affiliation with MemPalace.
@@ -1,3 +1,7 @@
+---
+permalink: claude-memory/observer-problem-state
+---
+
 ---
 name: Observer Problem inquiry state
 description: External Auditor review received (2026-04-08), three challenges land (Absorption Trap, Aesthetic of Rigor, Proceed with Annotations), review deliberately NOT taxonomized. Next: dialogue trial.
@@ -1,9 +1,12 @@
 ---
 name: Open Tasks
-description: Centralized list of pending tasks across all projects, updated as items are completed or added
+description: Centralized list of pending tasks across all projects, updated as items
+  are completed or added
 type: project
 originSessionId: e55939da-2fa7-4e18-a2e5-8f8fd3a8c607
+permalink: claude-memory/open-tasks
 ---
+
 # Open Tasks — Centralized

 **Last updated:** 2026-04-08
@@ -1,9 +1,13 @@
 ---
 name: Parked skills (proposed but deferred 2026-04-15)
-description: Skills proposed during the Symmetria + skill-improvement design session. Decision was to ship /wrap-up and /wake-up improvements first, propose these later when their real need surfaces in session work.
+description: Skills proposed during the Symmetria + skill-improvement design session.
+  Decision was to ship /wrap-up and /wake-up improvements first, propose these later
+  when their real need surfaces in session work.
 type: project
 originSessionId: 1c1bf37d-b1c3-4a62-9355-613c50f4c028
+permalink: claude-memory/parked-skills-2026-04-15
 ---
+
 # Parked Skills — Proposed but Deferred

 Surfaced during the 2026-04-15 conversation on improving /wrap-up and /wake-up given the Dasein/sleep frame. Steward decision: ship the wake/wrap improvements now (highest leverage), park these for a near-future session.
@@ -1,10 +1,15 @@
 ---
 name: pending-adr-006-type-applicability-matrix
-description: "ADR-006 v2 ACCEPTED 2026-05-16. Verbatim text preserved here until steward commits to ARC repo (final path TBD: docs/decisions/ or docs/AldineXXI-Codex/). Locks type-applicability matrix as canonical authority; Chamber apparatus-only; canon dropped; versioning structurally permissive; Stages B–G + housekeeping annex + Nav Philosophy parallel. Stage B (Apparatus extraction) is the next pulling thread."
+description: 'ADR-006 v2 ACCEPTED 2026-05-16. Verbatim text preserved here until steward
+  commits to ARC repo (final path TBD: docs/decisions/ or docs/AldineXXI-Codex/).
+  Locks type-applicability matrix as canonical authority; Chamber apparatus-only;
+  canon dropped; versioning structurally permissive; Stages B–G + housekeeping annex
+  + Nav Philosophy parallel. Stage B (Apparatus extraction) is the next pulling thread.'
 metadata:
  node_type: memory
  type: project
  originSessionId: 8b47c0eb-d396-43d5-98eb-7623e6f04357
+permalink: claude-memory/pending-adr-006-type-applicability-matrix-2026-05-16
 ---

 ## Status
@@ -1,10 +1,14 @@
 ---
 name: pending-jurist-directive-arc-specification-corpus-audit
-description: "Full audit brief issued by jurist 2026-05-14, forwarded by steward 2026-05-15 evening. DEFERRED to a dedicated half-day session — the rigor is the deliverable, not speed. Read-only investigation producing a structured report; no edits, no commits. Verbatim copy preserved below."
+description: Full audit brief issued by jurist 2026-05-14, forwarded by steward 2026-05-15
+  evening. DEFERRED to a dedicated half-day session — the rigor is the deliverable,
+  not speed. Read-only investigation producing a structured report; no edits, no commits.
+  Verbatim copy preserved below.
 metadata:
  node_type: memory
  type: project
  originSessionId: 8b47c0eb-d396-43d5-98eb-7623e6f04357
+permalink: claude-memory/pending-spec-corpus-audit-2026-05-14
 ---

 ## Status
@@ -1,9 +1,13 @@
 ---
 name: Pending work for 2026-05-06 — substrate finishing tasks
-description: Concrete to-dos carrying over from 2026-05-05's substrate restoration day. Order by dependency. All small (under an hour each). Most blocked behind a Claude Code restart that brings MCP back.
+description: Concrete to-dos carrying over from 2026-05-05's substrate restoration
+  day. Order by dependency. All small (under an hour each). Most blocked behind a
+  Claude Code restart that brings MCP back.
 type: project
 originSessionId: a156edbb-0c3d-4285-b3ed-f5a45b8dda66
+permalink: claude-memory/pending-work-2026-05-06
 ---
+
 # Pending work for 2026-05-06

 The 2026-05-05 substrate restoration left a clean working state but ~5 small tasks pulling forward. Most are blocked behind a Claude Code restart (which respawns MCP). Order matters — earlier tasks unblock later ones.
@@ -1,9 +1,15 @@
 ---
 name: plan-day-2026-05-20
-description: "Day-plan for Tuesday 2026-05-20 Barcelona (~8h, steward alone). Close Stage E continuation + 2 Stage F bounded items (5 corpus reclassifications + lex.html→about-page.html consolidation). Composed 08:30 after end-to-end read of canonical ARC sources. Energy curve: composition/decisions morning; mechanical housekeeping mid; short composition late. Three decisions to settle first (§4 scope; register marks for Colophon+Vignette; Plex Mono/Garamond optical balance). Branch docs/spec-extraction-2026-05 at 3607400."
+description: 'Day-plan for Tuesday 2026-05-20 Barcelona (~8h, steward alone). Close
+  Stage E continuation + 2 Stage F bounded items (5 corpus reclassifications + lex.html→about-page.html
+  consolidation). Composed 08:30 after end-to-end read of canonical ARC sources. Energy
+  curve: composition/decisions morning; mechanical housekeeping mid; short composition
+  late. Three decisions to settle first (§4 scope; register marks for Colophon+Vignette;
+  Plex Mono/Garamond optical balance). Branch docs/spec-extraction-2026-05 at 3607400.'
 metadata:
  type: project
  originSessionId: planning-2026-05-20-morning
+permalink: claude-memory/plan-day-2026-05-20
 ---

 # Day Plan — 2026-05-20 (Tuesday, Barcelona)
@@ -1,9 +1,14 @@
 ---
 name: plan-day-2026-05-21
-description: "Day-plan for Wednesday 2026-05-21 — travel Barcelona → Paris (6am flight), last taxes filing with Marie, 3h rehearsal. 2–3h max work time, fragmented. Closure + light maintenance posture; not a Stage F day. Three light options laid out (α Phase 6 wrap-up; β status-block housekeeping; γ Stage F prep document). Default: α first, β if energy holds; γ only if a third hour materialises."
+description: 'Day-plan for Wednesday 2026-05-21 — travel Barcelona → Paris (6am flight),
+  last taxes filing with Marie, 3h rehearsal. 2–3h max work time, fragmented. Closure
+  + light maintenance posture; not a Stage F day. Three light options laid out (α
+  Phase 6 wrap-up; β status-block housekeeping; γ Stage F prep document). Default:
+  α first, β if energy holds; γ only if a third hour materialises.'
 metadata:
  type: project
  originSessionId: planning-2026-05-20-evening
+permalink: claude-memory/plan-day-2026-05-21
 ---

 # Day Plan — 2026-05-21 (Wednesday, Barcelona → Paris)
@@ -1,9 +1,14 @@
 ---
 name: L1 recall-fix focused session plan (H2 first, [HARDENING], branch+PR strategy)
-description: Concrete plan for a single focused session to fix one of the April 19 H-issues on a branch and submit as PR to bring Seb relief rather than load. H2 chosen first as most empirically diagnosable. Self-contained for pickup across context clears.
+description: Concrete plan for a single focused session to fix one of the April 19
+  H-issues on a branch and submit as PR to bring Seb relief rather than load. H2 chosen
+  first as most empirically diagnosable. Self-contained for pickup across context
+  clears.
 type: project
 originSessionId: a5411fd1-4a96-43e7-aa1a-1a50d8951a8f
+permalink: claude-memory/project-l1-recall-fix-session-plan
 ---
+
 **Context:** April 19 baseline (`~/_Dev/CapableMind-AI/docs/thinking/David/l1-reliability/l1-recall-quality-baseline-2026-04-19.md`) identified 4 H-issues + an architectural finding (honest-degradation invariant violated at design level). Recent BetterMemories.io commits show team widened toward circles/BBF/perf — none of the 4 H-issues directly addressed. Today's mempalace mass-dilution finding (2026-05-13) gave empirical confirmation that this class of failure is real and won't resolve itself. Steward proposed steward+Claude-Code attempt fix on a branch + PR, sparing Seb the design load (Peter likely pressing him on other priorities).

 ## Workstream
@@ -1,10 +1,14 @@
 ---
 name: project-l1-reliability
-description: Canonical workstream tracker for L1-reliability work (CapableMind L1 substrate / BMF runtime). Chronological accumulating record from 2026-04-19 onward; current-state at top. Each substantive move appends. Sibling to project-arc-rework; replaces the per-session-memory chain MEMORY previously enumerated for L1.
+description: Canonical workstream tracker for L1-reliability work (CapableMind L1
+  substrate / BMF runtime). Chronological accumulating record from 2026-04-19 onward;
+  current-state at top. Each substantive move appends. Sibling to project-arc-rework;
+  replaces the per-session-memory chain MEMORY previously enumerated for L1.
 metadata:
  node_type: memory
  type: project
  originSessionId: fd7dd184-f64d-4f13-a1bd-abe1fa26192e
+permalink: claude-memory/project-l1-reliability
 ---

 # L1 Reliability — Canonical Workstream Tracker
@@ -1,9 +1,15 @@
 ---
-name: L1 retrieval architecture — what mempalace's mass-dilution finding implies for CapableMind L1 specifically
-description: CapableMind L1 has the architectural shape (multi-modal modules, RRF, sufficiency gate) to avoid mempalace's single-modal mass-dilution failure — but implementation specifics determine whether the shape pays off. Notes for Seb + David's L1 work (NOT mempalace work; mempalace is steward's private crutch).
+name: L1 retrieval architecture — what mempalace's mass-dilution finding implies for
+  CapableMind L1 specifically
+description: CapableMind L1 has the architectural shape (multi-modal modules, RRF,
+  sufficiency gate) to avoid mempalace's single-modal mass-dilution failure — but
+  implementation specifics determine whether the shape pays off. Notes for Seb + David's
+  L1 work (NOT mempalace work; mempalace is steward's private crutch).
 type: project
 originSessionId: a5411fd1-4a96-43e7-aa1a-1a50d8951a8f
+permalink: claude-memory/project-l1-retrieval-architecture-lessons
 ---
+
 **Context (2026-05-13):** Steward asked me to clarify L1-design implications of today's mempalace mass-dilution experiment. **Important distinction**: mempalace is the steward's private chamber tool (a "crutch" while L1 matures); Seb and David are building CapableMind L1 (in `~/_Dev/BetterMemories.io` and `~/_Dev/CapableMind-AI`). The two systems are fundamentally different in architecture. This memo addresses what L1's design needs to avoid the specific class of failure mempalace exhibited today.

 ## What today's mempalace finding showed (the empirical data)
@@ -1,8 +1,13 @@
 ---
-name: About-pages restructure decision frame 2026-04-26 (Path 1 vs Path 2 — awaiting steward decision)
-description: Decision frame placed on the table 2026-04-26 after reading ARC's actual colophon + About main + navigation.yaml. Reshapes yesterday's Path 1 (lex alongside colophon) vs Path 2 (lex as expansion of colophon) question through three discoveries that change the framing. Includes my read with reasoning. Awaiting steward decision.
+name: About-pages restructure decision frame 2026-04-26 (Path 1 vs Path 2 — awaiting
+  steward decision)
+description: Decision frame placed on the table 2026-04-26 after reading ARC's actual
+  colophon + About main + navigation.yaml. Reshapes yesterday's Path 1 (lex alongside
+  colophon) vs Path 2 (lex as expansion of colophon) question through three discoveries
+  that change the framing. Includes my read with reasoning. Awaiting steward decision.
 type: project
 originSessionId: 87dfe384-b862-4deb-9676-24e43046528f
+permalink: claude-memory/project-about-pages-decision-frame-2026-04-26
 ---

 > **INTEGRATED 2026-04-26 → `project-arc-rework.md` (Integration D + synthesis section).** 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."* Most content folded into the canonical ARC workstream tracker. **Note: this morning's Path 1 vs Path 2 framing was at a sub-level within the already-settled 2026-04-19 reflowed-About paradigm.** Path 1 LOCKED 2026-04-26 evening (separate Colophon and Lex enfilade items). Three-register frame survived as opening-of-About + second-part-of-About + enfilade-nav. Adsum-vs-threshold-hic LOCKED as two distinct texts (steward: *"They are certainly not the same text"*). 8-door enfilade landed: **Colophon · Lex · Framework · Vignette · Attention · Chamber · Tools · Now**. This file retained as audit trail. **For current home, see `project-arc-rework.md` §§ "2026-04-26 (afternoon) — Post-consolidation synthesis" and "2026-04-26 (afternoon, post-synthesis) — Steward locks + sibling-file integration."**
@@ -1,3 +1,7 @@
+---
+permalink: claude-memory/project-after-the-reply-publication-state
+---
+
 ---
 name: After the Reply — shipped 2026-05-01
 description: Five-essay sequence "After the Reply: Inheritance Without Guardians" fully implemented end-to-end. All 5 essays published, apparatus marker, sequence-index page, /essays/ promotion all live. Closed.
@@ -1,3 +1,7 @@
+---
+permalink: claude-memory/project-arc-404-page-design-pending
+---
+
 ---
 name: ARC 404 page — design + build pending
 description: Surfaced 2026-05-03 during _layout.scss SCSS audit — the .wrapper.not-found CSS rule was dead code (no template, no build path, no class application), but ARC genuinely needs a 404 page. Existing content/404.md is Jekyll-era leftover. Need: ARC-voice 404 design + Hakyll build path + template.
@@ -1,9 +1,14 @@
 ---
 name: ARC apparatus refactor — todo list (2026-05-06)
-description: Tracks the multi-session refactor flowing from the universal dateline + photo-apparatus + three containment patterns spec consolidation (2026-05-06). Captures what was decided, what's done, what remains, and the location data the steward provided for the content audit.
+description: Tracks the multi-session refactor flowing from the universal dateline
+  + photo-apparatus + three containment patterns spec consolidation (2026-05-06).
+  Captures what was decided, what's done, what remains, and the location data the
+  steward provided for the content audit.
 type: project
 originSessionId: 3bf7ae75-1138-4745-9024-0c40b3755ad3
+permalink: claude-memory/project-arc-apparatus-refactor-todo-2026-05-06
 ---
+
 # ARC apparatus refactor — todo list

 Spec foundation locked 2026-05-06 across §V (containment patterns), §VII (universal dateline + photo caption), and §V applicability table. Implementation is multi-session work; this list tracks state.
@@ -1,9 +1,16 @@
 ---
-name: ARC universal breadcrumb system — design spec session pending; sequenced AFTER type-pass
-description: Steward identified 2026-05-01 that the breadcrumb system should appear for all content, not just about-enfilade pages. Current state has duplicated breadcrumb logic across 3 templates with inline encoding of parent destinations. Spec session deferred until after the type-pass; type-pass resolves which content types exist and their relationships, which is the substrate breadcrumb design needs.
+name: ARC universal breadcrumb system — design spec session pending; sequenced AFTER
+  type-pass
+description: Steward identified 2026-05-01 that the breadcrumb system should appear
+  for all content, not just about-enfilade pages. Current state has duplicated breadcrumb
+  logic across 3 templates with inline encoding of parent destinations. Spec session
+  deferred until after the type-pass; type-pass resolves which content types exist
+  and their relationships, which is the substrate breadcrumb design needs.
 type: project
 originSessionId: 597aba4e-942b-4f20-8a89-3d801b14c971
+permalink: claude-memory/project-arc-breadcrumb-spec-pending
 ---
+
 # ARC universal breadcrumb system — pending

 **Status:** Design spec session pending. Sequenced AFTER the corpus `type:` audit.
@@ -1,9 +1,16 @@
 ---
 name: ARC capsule apparatus — open design question, deferred
-description: Davies' Capsules (in Europe A History) made the steward want to explore an embedded mini-composition apparatus for ARC. Decided against for now, but the deferral is *unsure of fit / appropriate usage / whether existing apparatus already covers it*, NOT closed. Re-enters scope when the pedagogical treatise begins — capsules may be exactly what etymological / biographical / microhistorical density needs there.
+description: Davies' Capsules (in Europe A History) made the steward want to explore
+  an embedded mini-composition apparatus for ARC. Decided against for now, but the
+  deferral is *unsure of fit / appropriate usage / whether existing apparatus already
+  covers it*, NOT closed. Re-enters scope when the pedagogical treatise begins — capsules
+  may be exactly what etymological / biographical / microhistorical density needs
+  there.
 type: project
 originSessionId: a156edbb-0c3d-4285-b3ed-f5a45b8dda66
+permalink: claude-memory/project-arc-capsule-apparatus-deferred-2026-05-05
 ---
+
 # ARC capsule apparatus — open design question

 **Date raised:** 2026-05-05
@@ -1,10 +1,15 @@
 ---
 name: arc-content-chamber-is-intentional-v1-chamber-legacy-deferred-presentable-cluster-to-do
-description: "The 39 no-class files under ARC's content/chamber/** are v1-Chamber OUTPUT (fictional canon, deliberations, protocols) — intentional retained legacy, NOT drift. Deferred ARC to-do: gather them into a presentable cluster as a record of the development that informed the still-unbuilt source-aware Chamber. Out of content-typology §5 clause-1 scope. Do not delete, do not reclassify."
+description: 'The 39 no-class files under ARC''s content/chamber/** are v1-Chamber
+  OUTPUT (fictional canon, deliberations, protocols) — intentional retained legacy,
+  NOT drift. Deferred ARC to-do: gather them into a presentable cluster as a record
+  of the development that informed the still-unbuilt source-aware Chamber. Out of
+  content-typology §5 clause-1 scope. Do not delete, do not reclassify.'
 metadata:
  node_type: memory
  type: project
  originSessionId: a8eb1d46-314e-4545-a133-f747c69ad5b4
+permalink: claude-memory/project-arc-chamber-v1-legacy-cluster
 ---

 ARC's `content/chamber/**` (canon/chamber-generated, deliberations, protocols, hermetic, inventions, hybrid, synthesis, contested) is **v1-Chamber output** — the fictional-canon era. It is **intentional retained legacy, not drift**: do not delete, do not force a `class:`, do not treat the 39 missing-`class:` files as findings.
@@ -1,9 +1,14 @@
 ---
 name: ARC chamber-library — Auerbach Mimesis acquisition debt
-description: "RESOLVED 2026-05-20 ~10:25 — steward provided a clean PDF source (22MB, Xerox-scanned + Acrobat-Distilled, 530 pages, valid text layer); pdftotext + custom heading-promotion produced a clean MD with all 20 chapters as H1. Filed at traditions/critical_modernity/literary_criticism/mimesis-auerbach.md. The .mobi failure is preserved below as forensic record + the conditions under which mojibake sources should be rejected."
+description: RESOLVED 2026-05-20 ~10:25 — steward provided a clean PDF source (22MB,
+  Xerox-scanned + Acrobat-Distilled, 530 pages, valid text layer); pdftotext + custom
+  heading-promotion produced a clean MD with all 20 chapters as H1. Filed at traditions/critical_modernity/literary_criticism/mimesis-auerbach.md.
+  The .mobi failure is preserved below as forensic record + the conditions under which
+  mojibake sources should be rejected.
 metadata:
  type: project
  originSessionId: 2026-05-20-conversion-session
+permalink: claude-memory/project-arc-mimesis-acquisition-debt
 ---

 # Auerbach *Mimesis* — acquisition debt — RESOLVED 2026-05-20
@@ -1,9 +1,17 @@
 ---
 name: ARC §IV ornament classes — spec vs content mismatch (substantive future work)
-description: Surfaced 2026-05-03 during _utilities.scss SCSS audit. §IV explicitly retires the seven ornament classes (.ornament.completion, .asterism, .marginalia, .lozenge, .gloss, .glimpse, .photo-essay). Content corpus actually uses .ornament classes ~213 times (mostly the retired ones plus 8 additional informal extensions never in the spec). Either the spec needs to be updated to reflect content reality, OR the content needs migration to whatever the spec considers the replacement. Decision is steward's; the work is substantial either way. Tied closely to project-arc-pause-close-ornament-and-hr-audit-pending.
+description: Surfaced 2026-05-03 during _utilities.scss SCSS audit. §IV explicitly
+  retires the seven ornament classes (.ornament.completion, .asterism, .marginalia,
+  .lozenge, .gloss, .glimpse, .photo-essay). Content corpus actually uses .ornament
+  classes ~213 times (mostly the retired ones plus 8 additional informal extensions
+  never in the spec). Either the spec needs to be updated to reflect content reality,
+  OR the content needs migration to whatever the spec considers the replacement. Decision
+  is steward's; the work is substantial either way. Tied closely to project-arc-pause-close-ornament-and-hr-audit-pending.
 type: project
 originSessionId: 8d9ac240-47df-4578-aec1-a9dd32965027
+permalink: claude-memory/project-arc-ornament-spec-vs-content-mismatch-pending
 ---
+
 # ARC §IV ornament classes — spec vs content mismatch (pending)

 **Surfaced:** 2026-05-03 during `_utilities.scss` SCSS audit (commit `95a48df`-adjacent). The audit revealed substantial mismatch between what spec §IV says and what content actually uses.
@@ -1,9 +1,16 @@
 ---
-name: ARC §IV Pause/Close ornament design + hr content audit — substantive future work
-description: Two interlocking pieces of work that should be undertaken together — designing the Pause/Close ornament asset (currently described in §IV but yet-to-be-designed), and auditing existing markdown <hr> usage for which instances should retire (replaced by `.ornament.pause`, removed entirely, or kept as legitimate Pause anchors). Not urgent; important. Requires steward design attention + content-audit time.
+name: ARC §IV Pause/Close ornament design + hr content audit — substantive future
+  work
+description: Two interlocking pieces of work that should be undertaken together —
+  designing the Pause/Close ornament asset (currently described in §IV but yet-to-be-designed),
+  and auditing existing markdown <hr> usage for which instances should retire (replaced
+  by `.ornament.pause`, removed entirely, or kept as legitimate Pause anchors). Not
+  urgent; important. Requires steward design attention + content-audit time.
 type: project
 originSessionId: 8d9ac240-47df-4578-aec1-a9dd32965027
+permalink: claude-memory/project-arc-pause-close-ornament-and-hr-audit-pending
 ---
+
 # ARC §IV Pause/Close ornament + `<hr>` content audit — pending

 **Origin date:** 2026-05-03 — surfaced during the SCSS audit pass. Steward direction: *"this needs serious study and thought (and may need to change the Md content files themselves if hr was used incorrectly). Not terribly urgent, but important and should be considered at the same time as the pause/close ornament."*
@@ -1,3 +1,7 @@
+---
+permalink: claude-memory/project-arc-pdf-print-postures-session-plan
+---
+
 ---
 name: ARC PDF + Print posture rendering session plan — XeLaTeX templates + AldineXXI sample images
 description: Dedicated session to build both Postures (PDF + Print) as LaTeX templates, render the Readings typology spec as PDF, and produce sample-image pairs for the AldineXXI page rewrite's Postures section. Two-birds: deliver the deferred Print/PDF posture spec sections AND the AldineXXI assets in one focused session.
@@ -1,9 +1,14 @@
 ---
 name: ARC rework landscape (reawakening 2026-04-16)
-description: ARC work surfaced after local dev environment restored. Captures the landscape as articulated by the steward — content rework, versioning question, cleanup scope. Not a project plan; a list of what is seen and named, to be taken up when concrete.
+description: ARC work surfaced after local dev environment restored. Captures the
+  landscape as articulated by the steward — content rework, versioning question, cleanup
+  scope. Not a project plan; a list of what is seen and named, to be taken up when
+  concrete.
 type: project
 originSessionId: 19aac84d-35aa-466d-bdc8-6d7c07cf449a
+permalink: claude-memory/project-arc-rework
 ---
+
 # ARC rework landscape — from 2026-04-16 reawakening

 After local dev was restored on 2026-04-16, the steward returned to ARC with fresh eyes for the first time in months and named the following scope. Preserved in their voice; not yet acted on.
@@ -1,9 +1,16 @@
 ---
-name: ARC spec — comprehensive audit against Bringhurst / Rutter / Tschichold for absolute compliance
-description: Aspiration logged 2026-05-03 — at an appropriate future point, re-read the entire AldineXXI spec against the three master-typographer canonical works to verify absolute compliance with high typography. Different from the SCSS audit (which is implementation hygiene); this is *spec/principle* alignment with the lineage ARC has chosen.
+name: ARC spec — comprehensive audit against Bringhurst / Rutter / Tschichold for
+  absolute compliance
+description: Aspiration logged 2026-05-03 — at an appropriate future point, re-read
+  the entire AldineXXI spec against the three master-typographer canonical works to
+  verify absolute compliance with high typography. Different from the SCSS audit (which
+  is implementation hygiene); this is *spec/principle* alignment with the lineage
+  ARC has chosen.
 type: project
 originSessionId: 8d9ac240-47df-4578-aec1-a9dd32965027
+permalink: claude-memory/project-arc-spec-master-typographer-audit-pending
 ---
+
 # ARC spec — master-typographer compliance audit (pending)

 **Steward direction 2026-05-03**: *"at some appropriate point, we should reread the spec against Bringhurst, Rutter, and Tschichold to be sure we're in absolute compliance with high-typography."*
@@ -1,9 +1,16 @@
 ---
 name: ARC web typography spec coverage — what still needs care
-description: Inventory of web-only and web-medium typography elements in ARC that have NOT been considered with the same care as the major spec sections. The link work of 2026-05-02 surfaced that "humble" typography (links) had been left to browser-defaults plus ad-hoc accumulation; the same is likely true for several other surfaces. Per steward direction 2026-05-02 — "the work needs to be bien-fait." Care is constitutive; no element is too humble for considered attention.
+description: Inventory of web-only and web-medium typography elements in ARC that
+  have NOT been considered with the same care as the major spec sections. The link
+  work of 2026-05-02 surfaced that "humble" typography (links) had been left to browser-defaults
+  plus ad-hoc accumulation; the same is likely true for several other surfaces. Per
+  steward direction 2026-05-02 — "the work needs to be bien-fait." Care is constitutive;
+  no element is too humble for considered attention.
 type: project
 originSessionId: 8d9ac240-47df-4578-aec1-a9dd32965027
+permalink: claude-memory/project-arc-web-typography-spec-coverage
 ---
+
 # ARC web typography spec coverage — what still needs care

 **Date:** 2026-05-02
@@ -1,9 +1,12 @@
 ---
 name: bge-m3 full re-mine plan — 2026-05-11
-description: The ONE job for the cleared context. Full chamber-library re-mine on PR #442's bge-m3 binding, replacing the mxbai 639k baseline. Steward away ~48 hours; remote-monitor via /remote-control. Pulling thread for the next session; everything else is deferred.
+description: The ONE job for the cleared context. Full chamber-library re-mine on
+  PR
 type: project
 originSessionId: a156edbb-0c3d-4285-b3ed-f5a45b8dda66
+permalink: claude-memory/project-bge-m3-full-remine-plan-2026-05-11
 ---
+
 # bge-m3 full re-mine plan

 > *"Do things once, correctly, with lasting integrity. Choose what is proportionate, fitting, and durable. Build what you will not need to rebuild."*
@@ -1,9 +1,16 @@
 ---
-name: ARC bio rewrite — English deployed; multi-language structure pending content spec
-description: Bio rewrite composed in dialogue 2026-04-30 through the eight foundational voices in /colophon/ + steward's flamenco-substrate disclosure + homecoming framing. English version deployed (commits 2a19d07, 3d5775c); /resume/ replaced by /cv/ with current professional CV; multi-language structure + translations return when content spec is written.
+name: ARC bio rewrite — English deployed; multi-language structure pending content
+  spec
+description: Bio rewrite composed in dialogue 2026-04-30 through the eight foundational
+  voices in /colophon/ + steward's flamenco-substrate disclosure + homecoming framing.
+  English version deployed (commits 2a19d07, 3d5775c); /resume/ replaced by /cv/ with
+  current professional CV; multi-language structure + translations return when content
+  spec is written.
 type: project
 originSessionId: 17dee884-74bf-43e7-9b6a-44bc82b97303
+permalink: claude-memory/project-bio-rewrite-pending-multilanguage-spec
 ---
+
 # ARC bio rewrite — English deployed; multi-language structure pending

 Composed in dialogue 2026-04-30 in response to steward's request to weave a bio through the eight foundational voices named in `/colophon/`: Alexander, Bachelard, Berger, Sennett (the Guides); Vico, Leopardi, Harrison, Heidegger (the Formation). Steward then disclosed the flamenco family of origin and the *homecoming* framing; the bio's final ¶1 ends with reverent acknowledgment of the substrate.
@@ -1,10 +1,14 @@
 ---
 name: bmf-capablemind-ai-backlog-state-2026-05-22-read
-description: "Point-in-time state of the L1 stack from the steward's wrap-time question. Seb quiet since ~2026-04-20 on BMF + CapableMind-AI; the active L1-stack movement the steward perceives is likely MemPalace (Igor's work). Near-term workable items for steward-shape execution, items waiting on Seb, and"
+description: Point-in-time state of the L1 stack from the steward's wrap-time question.
+  Seb quiet since ~2026-04-20 on BMF + CapableMind-AI; the active L1-stack movement
+  the steward perceives is likely MemPalace (Igor's work). Near-term workable items
+  for steward-shape execution, items waiting on Seb, and
 metadata:
  node_type: memory
  type: project
  originSessionId: 6c6e416d-ccea-41f1-b2ab-a2cf916e264b
+permalink: claude-memory/project-bmf-backlog-state-2026-05-22
 ---

 # BMF + CapableMind-AI backlog state — 2026-05-22 (midday)
--- a/Show More
+++ b/Show More