brain-save

name	brain-save
description	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".
allowed-tools	mcp__governed-brain__brain_search, mcp__governed-brain__brain_capture, mcp__governed-brain__brain_govern, mcp__governed-brain__brain_transition, mcp__governed-brain__brain_status, mcp__governed-brain__brain_audit_verify
version	1.0.0
author	Jeremy Longshore <[e-mail]>
license	Apache-2.0
compatibility	Designed for Claude Code; ships with the governed-second-brain plugin. Single-user local — you own the brain. Requires qmd on PATH for the index refresh after govern.
tags	["brain","governance","save","capture","local-first"]
argument-hint	[save <fact> | retire <memory-id>]
disable-model-invocation	true

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.