| name | manage-a-knowledge-base |
| description | Run a personal knowledge base or second brain as a system, not a junk drawer. Use for any stage of a notes collection: "process my inbox / triage my captures", "find contradictions across my notes", "synthesize / weave these notes together", "prune / clean up my ideas list", "archive stale notes / decay scan", "check my notes for broken links or missing metadata", "manage my vault / zettelkasten / second brain". Produces filed notes, collision logs, synthesis notes, a pruned idea list, archive decisions, and an integrity report, depending on the phase invoked. |
Manage a Knowledge Base
A notes collection has a lifecycle. Captures come in raw, get sorted, get connected, get synthesized, and eventually decay, and the whole thing drifts into broken links and duplicates unless something maintains it. This kit is the six maintenance moves, each a self-contained workflow in reference/.
Pick the phase that matches what the collection needs right now. You don't run all six every time.
The lifecycle
CAPTURE → TRIAGE → CONNECT → SYNTHESIZE → CURATE → DECAY
↑
INTEGRITY (periodic cross-check)
- Triage: turn a pile of raw captures into filed, structured notes. →
reference/triage-captures.md
- Connect: find where notes contradict, reinforce, or unexpectedly bridge. →
reference/find-collisions.md
- Synthesize: knit several notes into one integrated piece aimed at a question. →
reference/synthesize-notes.md
- Curate: prune the idea backlog; graduate the clusters that earned it. →
reference/curate-ideas.md
- Decay: score notes by use and age; archive the cold, promote the proven. →
reference/decay-and-archive.md
- : audit metadata, links, and contradictions across the whole base. →
