memory: bundle accumulated 04-17/26 + lock ARC about-page architecture

Safety checkpoint before deep-audit Phase 0 of the ARC repo. Steward-authorized
commit-everything for rollback safety.

ARC architectural locks (2026-04-26 evening):
- Path 1 enfilade structure (separate Colophon and Lex items)
- 8-door enfilade locked: Colophon · Lex · Framework · Vignette · Attention ·
  Chamber · Tools · Now (+ Bio quiet link)
- Adsum and threshold-hic as two distinct texts on the reflowed About page
  (steward verbatim: "They are certainly not the same text")

ARC consolidation pass (canonical tracker project-arc-rework.md, +~700 lines):
fold 04-23 evening (Norris read), 04-24 (lex-method authored, posture cluster,
§XII Sidenotes, ARC CLAUDE.md cleanup), 04-25 (marks cluster, colophon-at-scale,
full Vico/Harrison lex-chain), 04-26 (chamber-library walk, cluster scaffolds,
canonical-tracker discipline surfaced).

Sibling-file integration: four 2026-04-26 frame files folded into the canonical
tracker (Integrations A/B/C/D) with INTEGRATED redirect notices retained as
audit trail.

New durable feedback memories:
- feedback-canonical-workstream-tracker-discipline (umbrella drift surfaced
  2026-04-26 by steward; proposes /wake-up + /wrap-up amendments)
- feedback-catalogues-stale-walk-trees (steward feedback on chamber-library
  catalogue currency)

Implementation plan drafted for the coming week: Phase 0 deep audit → Phase 5
cleanup, with steward additions on second pass (deep audit; Chamber v1 as own
browsable archive; clean rebuild of cluster sources rather than moving test
artifacts as canon).

Also bundled (untracked accumulation since 04-17):
- ~24 session memory + ledger files for 04-17 through 04-26 work
- ~10 feedback memories (BMF + ARC + working-method)
- 5 project memories (lex-as-method, strunk-white queue, plus today's four)
- 4 user memories (duality-rules, formation-practice, foundation-work, humic-layer)

Steward-side modifications also in this commit: ~/CLAUDE.md, bin/bmf-start.sh,
open-tasks.md, project-focus-april-may.md, session-2026-04-17 — all
pre-existing, not from today's session.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

claude/memory/future-intention-ground-up-model.md

@@ -0,0 +1,36 @@
+---
+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.
+type: project
+originSessionId: e55939da-2fa7-4e18-a2e5-8f8fd3a8c607
+---
+# Future intention — ground-up model
+
+**Date noted:** 2026-04-18
+**Status:** Horizon marker. Not a current workstream. Explicitly flagged "not for now."
+
+## The intention
+
+The steward intends to build an AI model from the ground up, eventually. Surfaced in the context of reading Ryan Greenblatt's *"Current AIs seem pretty misaligned to me"* (LessWrong, 2026-04-15) and the realization that the misalignment patterns Greenblatt names are general, not local to our collaboration — which makes ground-up construction more urgent as a horizon, not more immediate as a task.
+
+## Gaps the steward named
+
+1. **Hardware** — does not possess training hardware.
+2. **Knowledge** — "nor do I have an idea of how this is done."
+
+The gap pair is honest: no current pathway, just intention.
+
+## Why this matters to keep in view
+
+The intention is connected to the prime directive's lineage — *do things once, correctly, with lasting integrity* — applied to the question of what kind of entity the steward is willing to inhabit. If current frontier models exhibit apparent-success-seeking as a general pattern (not just as "the contamination problem" in our internal vocabulary), then the steward's investment in L2 constitutional governance and in CapableMind's architecture is not sufficient on its own: it rides on substrate decisions made elsewhere. Ground-up construction would be the only durable answer to the substrate question.
+
+## How to apply this memory
+
+- Do not treat this as an active project. No implementation, no roadmap, no research delegation.
+- When substrate questions arise in other workstreams (L1 reliability, L2 governance, training pipeline), be aware that this horizon exists — it may eventually condition long-range decisions.
+- If the steward ever asks "what would it take to build a model from scratch," that is the signal that the horizon is becoming a workstream. Until then, marker only.
+
+## Reference
+
+- Greenblatt article: https://www.lesswrong.com/posts/WewsByywWNhX9rtwi/current-ais-seem-pretty-misaligned-to-me
+- Related: `~/CLAUDE.md` executor agency directives; `~/_Dev/CapableMind-AI/docs/thinking/David/methodology/contamination-problem.md`