Vaults
Three vaults. One portable workbench.
Everything fai captures lives in vaults - git-backed, version-controlled, readable by any AI you connect. You never interact with vaults directly. They appear as you work.
Where you are right now
fai captures every AI interaction, file change, and terminal activity during the current session - scoped to this working context. When you seal a session, the session captures merge into your project vault. The next session starts from what was left behind.
What this project knows
Architecture decisions, naming conventions, stack choices, patterns your team established. Committed to git alongside your code and shared with everyone on the project. Every sealed session adds to it - over time it becomes a complete record of how this codebase was built and why.
How you work, everywhere
Your workflow preferences, coding instincts, and patterns across every project.
Lives at ~/.fai/ - follows you regardless of which codebase you're in.
Grows richer with every session across every project. By month 6, any AI you work
with knows how you prefer to think about problems.
Inside a knowledge vault
Inside a knowledge vault
Both the project vault and personal vault are knowledge vaults. Each contains four sub-vaults that organize different kinds of knowledge:
Current focus
What's active right now in this project. Changes frequently - synthesised at session end.
Recurring behaviours
Recurring workflows and behaviors. Changes occasionally - synthesised daily.
Architectural choices
Architectural choices and their rationale. Changes rarely - synthesised weekly.
The distilled whole
Aggregates context + patterns + decisions into a unified knowledge base.
Exports FAI-PROJECT.md and FAI-PERSONAL.md - the files connected AIs
read on startup.
What vaults look like on disk
~/.fai/sessions/ ← active session captures
~/.fai/workbenches/{project-id}/
├── context/ ← ContextVault
├── patterns/ ← PatternVault
├── decisions/ ← DecisionVault
├── petnames/ ← PetnamesVault
├── FAI-PROJECT.md ← aggregated knowledge (read by AIs)
└── CLAUDE.md ← same knowledge in Claude format
Next
- → Sessions - how sessions open, seal, and propagate
- → Knowledge flow - how captures become compound intelligence
- → Session vault detail
- → Project vault detail
- → Personal vault detail
- → Knowledge vault internals