Docs / 02-requirements/004-obsidian-knowledge-base
REQ-004 Company knowledge base in Obsidian
A full documentation and knowledge management system in Obsidian — folder structure, templates, SOPs, department wikis, prompt library, registers — serving as the curated core of RAG.
REQ-004 — Company knowledge base in Obsidian
Need (what is being asked)
Design and roll out the company’s documentation and knowledge system in Obsidian: folder structure, naming conventions, templates (SOP, meeting, requirement, process, prompt, agent, risk, training, vendor, status), department wikis and knowledge maps, decision log, risk register, change log, implementation tracker, glossary, data-source inventory, process map archive, lessons-learned database, and continuous-improvement backlog.
Context (why — what problem it solves)
Company knowledge lives in heads, email, and scattered files (assumption — to validate). Undocumented knowledge cannot feed RAG; the knowledge base is the substrate of every AI use case.
Current state (how it is done today)
No structured knowledge system.
Success criteria
- Vault (“vanos-brain”) designed by M3, seeded M4, adopted department-by-department from M5; SOP coverage and freshness KPIs met (kpi-framework); approved notes flow into RAG automatically.
Dependencies / related
Blueprint: obsidian-vault-blueprint; ingestion: rag-and-data-pipeline.
History
- 2026-07-03 — captured (source: CEO transformation brief)