Project vault
The project vault is what this codebase knows. Architecture decisions, naming conventions, stack choices, the patterns your team established. Built session by session from your AI conversations and code changes.
It lives alongside your code - committed to git, shared with your team.
What it stores
- Architecture decisions and their rationale
- Naming conventions and code style patterns
- Stack choices and library preferences
- Recurring workflows specific to this project
- Historical context: why things were built the way they were
How it's scoped
The project vault is associated with your project directory. Everyone working on the same codebase shares the same project vault. When one session seals, the knowledge propagates to all active sessions on the project.
What it produces
After synthesis runs, the project vault exports FAI-PROJECT.md - a structured
knowledge document that any connected AI reads on startup. This is what makes
session 10 smarter than session 1.
How it relates to other vaults
The project vault is one of two knowledge vaults (the other is your personal vault). Both contain the same four sub-vault types but store different scopes of knowledge. Session captures feed the project vault through synthesis.