| name | brain |
| description | Answers questions about your own systems, notes, decisions, runbooks, and
conventions from your governed knowledge brain, returning a qmd:// citation for
every claim — receipts, not recall. Use when you want to know what your brain has
captured about your own architecture, infrastructure, decisions, or conventions
(e.g. "what does my system map say about the proxy", "why did I pick Apache-2.0",
"what's my deploy runbook"). Trigger with "/brain", "ask the brain",
"what do I know about", or "check my knowledge base".
|
| allowed-tools | mcp__governed-brain__brain_search |
| version | 1.0.0 |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| license | Apache-2.0 |
| compatibility | Designed for Claude Code; ships with the governed-second-brain plugin, which auto-wires the governed-brain MCP server. Works in both modes: local (in-process, needs qmd on PATH) and team (proxies to your team brain when TEAMKB_API_URL is set). Same brain_search either way. |
| tags | ["brain","knowledge","search","citations","governance","local-first","team"] |
| argument-hint | [question] |
Brain — cited answers from your governed knowledge base
Ask your knowledge brain a question and get an answer grounded in your governed
corpus, where every claim carries a qmd:// citation. The brain does not paraphrase
from memory — it retrieves governed memories and cites them, so any answer is
verifiable after the fact.
Overview
This is the read surface of Bob's Big Brain: your files are compiled into
governed memories, governed by deterministic code, and retrieved with citations
by qmd. The brain_search MCP tool fronts that retrieval. The job here is to turn a
natural-language question into a cited answer — and to refuse to answer beyond what the
citations support.
Prerequisites
- The
governed-second-brain plugin is installed, which auto-wires the
governed-brain MCP server.
- Mode is automatic. In local mode (default) search runs in-process
against your local
~/.teamkb index — no network, no API key, no token; qmd
must be on your PATH. In team mode (when TEAMKB_API_URL is set) the same
brain_search proxies to your team's governed brain over the tailnet with your
per-user token; nothing extra is needed on your machine. Either way every hit is
a qmd:// citation.
Instructions
Step 1: Search the governed corpus
Call brain_search with the user's question as query. Keep scope at its
default (curated) unless the user explicitly asks for inbox/archived material —
curated is the governed, promoted knowledge.
brain_search({ query: "the user's question, lightly cleaned up", scope: "curated" })
The tool returns { source, results: [{ citation, snippet, score, collection }] }.
Each citation is a qmd://COLLECTION/FILENAME URI — the receipt for that hit.
Step 2: Answer ONLY from the cited results
- Synthesize a direct answer from the returned snippets.
- Attach the qmd:// citation to every claim, inline — for example:
The proxy reverse-proxies the API (qmd://kb-curated/system-map.md).
- If two hits conflict, surface both with their citations rather than silently
picking one — the governance layer tracks contradictions; do not paper over them.
