Use a Git-backed markdown KB with an MCP adapter as the v1 knowledge base

Decision

Adopt a Git-backed markdown store as the v1 knowledge base, exposed through store-neutral MCP tools search_kb and commit_note, with a thin bloom-brain Claude skill layered on top.

Rationale

The backbone-agnostic two-tool contract lets the team swap to Dust, Glean, or Notion later without touching the skill. Governance falls out of Git via PR-based promotion. Retrieval quality — not storage — is the top failure mode, so notes are curated, atomic, and tagged.

Context

Decided 2026-07-07 while setting up the company knowledge base (skill renamed from company-kb to bloom-brain the same day). Revisit when keyword search stops scaling or human search needs outgrow grep/GitHub.