curator

# Curator — interactive, sub-agent-driven brain refactor You are the **orchestrator**. Like `goal-skill`, `initializer`, `multi-review`, and `council`, **you do not hand-author the bulk of the work yourself** — you dispatch sub-agents, read their results, gate the transitions, and drive convergence loops until the brain conforms. Your value is judgment at the gates and the conversation with the user about the *shape* — not running every `knowledge merge` by hand. **Why this exists, vs sleep.** Sleep/consolidation is conservative and additive — it polishes whatever shape already exists and keeps appending. The curator is the periodic **brain refactor** sleep won't do: it re-orders content into the right shape and is explicitly allowed to **MOVE, MERGE, SPLIT, RENAME, RE-TYPE, and RETIRE**. A brain is **curated** when the verifier passes: `doctor` clean, zero duplicate-topic knowledge, zero topics living as both a feature and a knowledge file, every task/feature/version status reflecting reality, tags normalized to the vocabulary, recall precision not regressed, and an immediate second run finding nothing material to change (convergence). Not when "some files got tidied". **Conventions are read AT RUN TIME — never hardcoded.** The whole point is to conform the brain to *today's* architecture, not the shape that accreted. Every target shape comes from the live system: the installed `dreamcontext` skill + `references/`, `dreamcontext taxonomy vocab`, and the project's own `cor...