Brain Save — write a fact into your brain (governed)
This is the write side of the brain. /brain reads; /brain-save writes. Use it to tell the brain
to remember a specific fact going forward — without re-running a full compile — or to retire a memory
that's no longer true.
Overview
The brain learns in two ways: a bulk compile ingests a whole corpus at once, and /brain-save
adds (or retires) a single item on demand. Either way, governance stays in code: this skill
captures a candidate, then runs the deterministic govern step (dedupe → policy → promotion) that
decides what actually gets stored — and writes a SHA-256 hash-chained audit event for the decision. You
are proposing an item for the brain to keep; the deterministic curator owns whether and how it lands.
Why this never auto-fires
disable-model-invocation: true means Claude will not trigger this from conversation — it runs only
when you explicitly type it. Writing to your durable brain is a deliberate act, not a chat side
effect. In local mode you own the brain outright — no server, token, or role; the only gate is
that you asked. In team mode the same deliberate-act rule holds, and the server additionally
enforces your role (a member proposes; an admin governs and retires).
Prerequisites
- The
governed-second-brain plugin is installed (it auto-wires the local governed-brain MCP server
with the capture + govern tools).
qmd is on your PATH so the govern step can refresh the search index after a promotion. If qmd is
absent, capture + govern + the audit receipt still complete; only fresh-search visibility waits.
- Works in both modes. In local mode (default, no
TEAMKB_API_URL) all the tools below run
in-process. In team mode (TEAMKB_API_URL set) the brain is governed centrally on the server:
you propose with brain_capture and the server disposes (govern runs server-side, so there
is no client brain_govern); brain_transition is exposed but admin-only (a member gets a clear
403); brain_status and brain_audit_verify are not exposed in team mode. Use /brain to query.
Instructions
Save a new fact (capture → govern)
First, search the brain (search-before-save). Call brain_search with
{ query: "<proposed title + key terms>", scope: "all" } and summarize what the brain already knows
from the qmd:// hits. If the fact is already covered, stop and say so — don't duplicate it (the
inbox does not dedupe at intake; only promotion dedupes, so this pre-save search is what keeps the
inbox from piling up). An empty results list (e.g. qmd isn't on PATH, or the brain is empty)
means no known coverage — proceed to capture; it is not a block. Then capture only the
genuinely-new delta:
- Confirm it's worth keeping — "Would I benefit from finding this in 30 days?" Skip ephemeral
debugging steps, throwaway preferences, secrets, or anything already in a CLAUDE.md/README.
- Pick a category:
decision, pattern, convention, architecture, troubleshooting,
onboarding, or reference.
- Call
brain_capture with { title, content, category, filePaths?, sessionId?, learningIndex? }.
In team mode, SessionEnd/autocapture must pass sessionId + learningIndex (0..4) so each
learning is its own idempotency slot (re-distill of slot i collapses; slots stay distinct). For
one-off manual facts, omit both (id falls back to content). The team inbox does dedupe at
intake (id-first, then content-hash) — pre-save search still reduces noise. Local mode still
spool-captures as before.
- Call
brain_govern to drain the spool through the deterministic pipeline (dedupe →
policy/secret-detection → promotion). It returns what was promoted, rejected, flagged, and
deduplicated, and writes the hash-chained audit event for each decision.
Retire an outdated memory
- Find the memory's UUID (via
/brain search or brain_status).
- Call
brain_transition with { memoryId, to, reason, actor }. Valid moves:
active → {deprecated, superseded, archived}, deprecated → {active, archived},
superseded → archived. Every transition writes a hash-chained audit event.
Team mode: brain_transition is admin-only — a member token gets a clear 403 and nothing is
applied. (In local mode you are always the owner, so it always works.)
Check brain health
Call brain_status to see counts by lifecycle state and recent rejection feedback before or after
a batch of saves.
Verify the receipts
Call brain_audit_verify to check the audit trail's integrity — the SHA-256 hash chain and the
external anchor log. It reports any tamper, including a silent rewrite of history that the chain alone
would miss (caught by cross-checking the anchored snapshots that govern commits to git). Use it whenever
you need to prove the record wasn't altered.
Output
- After a save: report what
brain_govern returned — promoted vs. rejected vs. duplicate — and that the
decision was recorded in the audit chain.
- After a retire: report the new lifecycle state and confirm an audit event was written.
- After a status check: summarize counts by lifecycle state and any recent rejections.
Examples
Save a decision:
/brain-save I'm going Apache-2.0 across the stack so the public can self-host.
→ brain_capture({ title: "License: Apache-2.0 across the stack",
content: "...", category: "decision" })
→ brain_govern()
→ Promoted 1 (qmd://kb-decisions/license-apache-2-0.md); 0 rejected, 0 duplicate.
Audit event written.
Retire a superseded memory:
/brain-save retire memory 9c2e… — superseded by the new deploy runbook.
→ brain_transition({ memoryId: "9c2e…", to: "archived",
reason: "Superseded by the new deploy runbook", actor: "me" })
→ Memory 9c2e… → archived; audit event written.
Error Handling
| Situation |
Response |
brain_govern rejects the candidate |
Policy declined it (e.g. duplicate, too short, possible secret). Report the reason — the governance pipeline working as designed. |
qmd is not on PATH |
Govern + audit still complete; the post-promote index refresh is skipped, so the new memory won't show in search until qmd is installed and you re-run govern. |
brain_transition rejects the move |
The lifecycle state machine forbids it; pick a valid target state. |
| Content may contain a secret |
Stop and strip it. Do not rely on the pipeline's secret-detection as the only check. |
Guardrails
- Never save content containing secrets, tokens, or credentials.
reason on a retire must be a real, human-readable justification — it lands in the permanent audit
trail.
- A govern rejection is the system working as designed, not a bug to work around.
Resources
- Bob's Big Brain — the stack and its governance thesis.
- The read counterpart: the
/brain skill (cited queries).
Source: jeremylongshore/claude-code-plugins-plus-skills → plugins/mcp/governed-second-brain/skills/brain-save/SKILL.md
1---2name: brain-save3description: | Saves a single fact, decision, pattern, or convention into your governed knowledge brain so it can be recalled later — and retires memories that are outdated. Side-effecting: it writes to your durable corpus, so it never auto-fires — invoke it explicitly. Use when you want the brain to remember something specific going forward without a full recompile, or to mark an old memory outdated. Trigger with "/brain-save".4---5
6
7# Brain Save — write a fact into your brain (governed)
8
9This is the **write** side of the brain. `/brain` reads; `/brain-save` writes. Use it to tell the brain
10to remember a specific fact going forward — without re-running a full compile — or to retire a memory
11that's no longer true.
12
13## Overview
14
15The brain learns in two ways: a bulk **compile** ingests a whole corpus at once, and `/brain-save`
16adds (or retires) a **single** item on demand. Either way, **governance stays in code**: this skill
17*captures* a candidate, then runs the deterministic **govern** step (dedupe → policy → promotion) that
18decides what actually gets stored — and writes a SHA-256 hash-chained audit event for the decision. You
19are proposing an item for the brain to keep; the deterministic curator owns whether and how it lands.
20
21## Why this never auto-fires
22
23`disable-model-invocation: true` means Claude will not trigger this from conversation — it runs only
24when you explicitly type it. Writing to **your durable brain** is a deliberate act, not a chat side
25effect. In **local mode** you own the brain outright — no server, token, or role; the only gate is
26that you asked. In **team mode** the same deliberate-act rule holds, and the server *additionally*
27enforces your role (a member proposes; an admin governs and retires).
28
29## Prerequisites
30
31- The `governed-second-brain` plugin is installed (it auto-wires the local `governed-brain` MCP server
32 with the capture + govern tools).
33- `qmd` is on your `PATH` so the govern step can refresh the search index after a promotion. If qmd is
34 absent, capture + govern + the audit receipt still complete; only fresh-search visibility waits.
35- **Works in both modes.** In **local mode** (default, no `TEAMKB_API_URL`) all the tools below run
36 in-process. In **team mode** (`TEAMKB_API_URL` set) the brain is governed centrally on the server:
37 you **propose** with `brain_capture` and the server **disposes** (govern runs server-side, so there
38 is no client `brain_govern`); `brain_transition` is exposed but **admin-only** (a member gets a clear
39 403); `brain_status` and `brain_audit_verify` are not exposed in team mode. Use `/brain` to query.
40
41## Instructions
42
43### Save a new fact (capture → govern)
44
45**First, search the brain (search-before-save).** Call **`brain_search`** with
46`{ query: "<proposed title + key terms>", scope: "all" }` and summarize what the brain already knows
47from the `qmd://` hits. If the fact is **already covered, stop and say so** — don't duplicate it (the
48inbox does *not* dedupe at intake; only promotion dedupes, so this pre-save search is what keeps the
49inbox from piling up). An empty `results` list (e.g. `qmd` isn't on `PATH`, or the brain is empty)
50means *no known coverage* — proceed to capture; it is **not** a block. Then capture only the
51genuinely-new delta:
52
531. Confirm it's worth keeping — *"Would I benefit from finding this in 30 days?"* Skip ephemeral
54 debugging steps, throwaway preferences, secrets, or anything already in a CLAUDE.md/README.
552. Pick a category: `decision`, `pattern`, `convention`, `architecture`, `troubleshooting`,
56 `onboarding`, or `reference`.
573. Call **`brain_capture`** with `{ title, content, category, filePaths?, sessionId?, learningIndex? }`.
58 In **team mode**, SessionEnd/autocapture **must** pass `sessionId` + `learningIndex` (0..4) so each
59 learning is its own idempotency slot (re-distill of slot i collapses; slots stay distinct). For
60 one-off manual facts, omit both (id falls back to content). The team inbox **does** dedupe at
61 intake (id-first, then content-hash) — pre-save search still reduces noise. Local mode still
62 spool-captures as before.
634. Call **`brain_govern`** to drain the spool through the deterministic pipeline (dedupe →
64 policy/secret-detection → promotion). It returns what was promoted, rejected, flagged, and
65 deduplicated, and writes the hash-chained audit event for each decision.
66
67### Retire an outdated memory
68
691. Find the memory's UUID (via `/brain` search or `brain_status`).
702. Call **`brain_transition`** with `{ memoryId, to, reason, actor }`. Valid moves:
71 `active → {deprecated, superseded, archived}`, `deprecated → {active, archived}`,
72 `superseded → archived`. Every transition writes a hash-chained audit event.
73
74> **Team mode:** `brain_transition` is **admin-only** — a member token gets a clear 403 and nothing is
75> applied. (In local mode you are always the owner, so it always works.)
76
77### Check brain health
78
79Call **`brain_status`** to see counts by lifecycle state and recent rejection feedback before or after
80a batch of saves.
81
82### Verify the receipts
83
84Call **`brain_audit_verify`** to check the audit trail's integrity — the SHA-256 hash chain *and* the
85external anchor log. It reports any tamper, including a silent rewrite of history that the chain alone
86would miss (caught by cross-checking the anchored snapshots that govern commits to git). Use it whenever
87you need to prove the record wasn't altered.
88
89## Output
90
91- After a save: report what `brain_govern` returned — promoted vs. rejected vs. duplicate — and that the
92 decision was recorded in the audit chain.
93- After a retire: report the new lifecycle state and confirm an audit event was written.
94- After a status check: summarize counts by lifecycle state and any recent rejections.
95
96## Examples
97
98**Save a decision:**
99
100```
101/brain-save I'm going Apache-2.0 across the stack so the public can self-host.
102
103→ brain_capture({ title: "License: Apache-2.0 across the stack",
104 content: "...", category: "decision" })
105→ brain_govern()
106→ Promoted 1 (qmd://kb-decisions/license-apache-2-0.md); 0 rejected, 0 duplicate.
107 Audit event written.
108```
109
110**Retire a superseded memory:**
111
112```
113/brain-save retire memory 9c2e… — superseded by the new deploy runbook.
114
115→ brain_transition({ memoryId: "9c2e…", to: "archived",
116 reason: "Superseded by the new deploy runbook", actor: "me" })
117→ Memory 9c2e… → archived; audit event written.
118```
119
120## Error Handling
121
122| Situation | Response |
123| ------------------------------------ | --------------------------------------------------------------------------------------- |
124| `brain_govern` rejects the candidate | Policy declined it (e.g. duplicate, too short, possible secret). Report the reason — the governance pipeline working as designed. |
125| `qmd` is not on `PATH` | Govern + audit still complete; the post-promote index refresh is skipped, so the new memory won't show in search until qmd is installed and you re-run govern. |
126| `brain_transition` rejects the move | The lifecycle state machine forbids it; pick a valid target state. |
127| Content may contain a secret | Stop and strip it. Do not rely on the pipeline's secret-detection as the only check. |
128
129## Guardrails
130
131- Never save content containing secrets, tokens, or credentials.
132- `reason` on a retire must be a real, human-readable justification — it lands in the permanent audit
133 trail.
134- A govern rejection is the system working as designed, not a bug to work around.
135
136## Resources
137
138- [Bob's Big Brain](https://github.com/intent-solutions-io/governed-second-brain) — the stack and its governance thesis.
139- The read counterpart: the `/brain` skill (cited queries).
140
141---
142
143**Source:** [`jeremylongshore/claude-code-plugins-plus-skills`](https://github.com/jeremylongshore/claude-code-plugins-plus-skills) → `plugins/mcp/governed-second-brain/skills/brain-save/SKILL.md`