brainstorm

# Knowledge brainstorm ## Contract | Field | Bound contract | |---|---| | Trigger | User begins nontrivial knowledge work with notes, a transcript, a brain dump, or a problem to think through (mode: dump); asks to brainstorm, asks what to build, or wants divergent ideas on a subject (mode: ideate); or faces a question genuinely clearer shown than told and approves a local browser view (mode: visual). | | Authority | Reversible local: writes only `plans/brainstorm-{descriptive-name}.md`, `docs/ideation/<slug>.md` plus `<slug>.html` when `format:html` is given, `.odin/brainstorm/session-<24-hex>` session data, and OS-temp visual probe files; rollback is deleting those files and stopping the named managed process. No remote mutation. | | Side effect | Reads prior knowledge in `docs/knowledge/`, `plans/`, and `docs/solutions/`; mode visual starts a local key-gated HTTP and WebSocket server with an idle timeout and retains its session directory. No other file, VCS, credential, paid, published, or remote change. | | Done | The active mode's done state holds: dump — the user's language is structurally captured, prior context or its honest absence is shown, tensions and gaps are identified, at most three load-bearing questions are resolved, a reasoned direction is offered, and the origin file is written before plan; ideate — the ideation document records grounded survivors and a reason for every rejection, each candidate cites its basis, one reviewer adjudicated the complete pool, ...