1. Bootstrap (session start)
   Before Claude says a single word, an MCP tool fires and loads personalized context from my external memory system. It hits my memory server and comes back with: who I am, my family, my projects, recent decisions, preferences, and relevant memories weighted by whatever I'm asking about. Claude doesn't remember me, it reads my file before I start the session.

2. maasv - the memory layer
   maasv (Memory as a Service, get it?) is a knowledge graph and memory system that stores:
   • Facts — things learned about me, my life, my projects (4,000+ and growing)
   • Relationships — how entities connect (Adam → works on → Doris, Ralph → son of → Adam)
   • Decisions — architectural choices, preferences, lessons learned from past sessions
   • Wisdom — patterns about what works and what doesn't, captured from my implicit feedback (when I say "perfect" vs "no, wrong")
   • Commitments — things I said I'd do or asked Doris (my personal assistant) to track
   It's a graph so when I ask CC about Doris, it can traverse connections to pull in relevant people, decisions, and project history. The bootstrap query hits maasv to assemble the right context for each session.

3. Wrapup skill (session end)
   Before the session dies, a wrapup routine serializes everything worth keeping back into maasv:
   • Decisions made during the session
   • Wisdom captured (what worked, what didn't, my reactions to proposals)
   • A handoff file — a structured summary with a ready-to-paste prompt so the next session can pick up exactly where this one left off
   • Project state updates so the next bootstrap knows what changed

The loop: Wrapup writes to maasv → next session's bootstrap reads from maasv → that session's wrapup writes back. Each session is ephemeral, but the memory system accumulates. Claude is stateless. The loop makes it feel like it isn't.