06 — Knowledge Base

Design workspace for vanos-brain, the company-wide Obsidian knowledge vault to be created for Prime Products Ltd. This is the client-facing counterpart of key-account-prime: same Knowledge-OS philosophy (one concept per file, YAML frontmatter, kebab-case, decision logs, git-backed), but owned by PRIME PRODUCTS and populated by its 15 departments.

Documents

Document	What it is
obsidian-vault-blueprint.md	Complete design of the vanos-brain vault: rationale, folder tree, naming, tagging, linking, frontmatter, governance, RAG connection, rollout.
obsidian-template-library.md	Full set of note templates (SOP, prompt, meeting, decision, process, agent spec, …) with ready-to-copy skeletons.

Core principle: the vault is the curated core of RAG

The on-prem AI platform is only as good as what it retrieves. The company vault is the single curated corpus that feeds the RAG pipeline (../05-technical/rag-and-data-pipeline.md) — a deliberate garbage-in guardrail:

• Only notes that pass the quality bar (status: approved, valid frontmatter, owner assigned) are ingested.
• Everything else — drafts, raw meeting notes, stale SOPs — stays retrievable by humans in Obsidian but invisible to the assistant.
• The assistant cites vault notes back to users, closing the loop: bad answers point to bad or missing notes, which become documentation tasks.

This makes knowledge quality a measurable program KPI (see ../02-program/kpi-framework.md) rather than an afterthought.

Related

• Discovery outputs that seed the vault: ../03-discovery/requirement-analysis-framework.md, ../../02-Requirements/_index.md
• Rollout timing: ../02-program/roadmap-12-month.md (M3 design, M4 seed, M5+ department rollout)
• Commercial framing: Stage 4 in ../09-commercial/stage-offer-structure.md