Obsidian Vault Integration — Architecture & Operations Guide

**Version**: 0.2.0 **Created**: 2026-03-01 **Updated**: 2026-03-01 **Status**: Phase 1-4 complete, Phase 5 deferred Knowledge generated by the agent ecosystem is fragmented across 6+ disconnected stores: | Store | Type | Weakness | |-------|------|----------| | `memory/*.md` files | Flat Markdown | No linking, manual curation, linear | | Kimi SQLite DB (`kimi_memory.db`) | Structured tables | Queryable but invisible, no graph | | Supabase | Cloud relational | API-only access, no browsing | | Orbit | Semantic memory | Black-box embeddings, no human navigation | | Discord threads | Chat messages | Ephemeral, unsearchable after scroll | | Plan files (`.claude/plans/`) | Task-scoped Markdown | Die when plans complete | None of these stores link ideas together. A synthesis about "N'Ko voice keyboards" doesn't know it's related to a Pulse session that built the "Speak" project, which connects to the "voice recognition" entity in the knowledge graph. **Obsidian's `[[bidirectional links]]`** solve this organically. Every `[[entity]]` reference creates a backlink, and over time the graph view reveals clusters, orphans, and unexpected connections between ideas. The `obsidian-headless` CLI (v0.0.3) makes the vault machine-writable without the desktop app.