Principle: Memory is what compounds. The models reset. The house keeps notes. See PRINCIPLES.md. This is the step most people skip, and it’s the only one that accrues value. Don’t skip it.
4.1 Make a vault
An Obsidian vault is ideal because it’s just a folder of Markdown — plain files you own, no lock-in — and you can open the same folder in the Obsidian app for a human view. But a bare directory of.md works fine to start.
On the box:
memory/ you can copy in, including a decision-note template (memory/decisions/0000-decision-template.md). Decisions are the highest-value thing to record: what you chose, why, and what you rejected. An agent that can read your past decisions stops re-litigating them.
- Obsidian: https://obsidian.md — Help: https://help.obsidian.md
4.2 Point the filesystem MCP server at it
In Step 3 you added a filesystem tool. Scope it to the vault so the agent can read and write notes there. With Claude Code, add the vault path as an allowed directory for the filesystem server (see the server’s README):- Filesystem MCP server (allowed directories, config): https://github.com/modelcontextprotocol/servers/tree/main/src/filesystem
4.3 Use it
Two habits make the memory real:- End sessions by writing back. Ask the agent to log what was decided or learned into
memory/before you close it. - Start sessions by reading. Have the agent skim recent notes for the project you’re working on so it walks in with context.
✅ Verification (the foundation is complete)
docs/grow-into.md for what comes next and in what order.