// Session 1You: We use Tailwind with semantic tokens,
never raw hex. Spacing is 4px base.
AI: Got it! I'll follow that.
// Session 2 — next dayYou: Why did you use #3B82F6 again?
AI: Sorry, can you remind me of your
color conventions?
// Session 47 — same question, again
With Soleri
// Session 1You: We use Tailwind with semantic tokens.
AI: Captured to vault. I'll enforce this.
// Session 47You: Review this component.
AI: Found 2 raw hex values. Your vault says
semantic tokens only. Fixing now.
✓ Pattern applied from vault✓ Brain confidence: 94%
One engine.
One vault.
No coordination overhead.
A Vault for knowledge,
a Brain that learns, Memory that persists.
Single process. Feed it knowledge — it organizes, vectorizes, and learns.
VaultBrainMemory
Configuration as code
One command generates the config. Voice, domains, vault backends — all declarative, all version-controlled.
Ask about buttons — the vault searches here first.
Backend
Domain
API conventions
Database schemas
Auth patterns
Performance
Ask about queries or API design — the vault pulls from here.
Cross-cutting
Domain
Git workflows
Code review
Testing strategies
Documentation
Patterns that span domains. The graph finds connections automatically.
Layered like living systems
Each layer grows independently. Swap transports, plug in knowledge, customize
your agent — the engine stays the same.
Agents
Your agent's config (agent.yaml): identity, voice, domain wiring. Create in one command, customize anytime.
Domains
Pluggable knowledge domains. The engine loads relevant domains based on your agent's vault structure.
Engine
Single MCP server process. Vault (knowledge), Brain (learning), Memory (context), Planning (workflows). Your agent runs on it. Updates via npm update.
Transports
Protocol adapters isolated from core: mcp.ts ships now, rest.ts and lsp.ts ready for VS Code, Cursor, Zed, and custom dashboards. Adding a transport = one adapter file.