research-brainstormlisted

# Research brainstorm ## Objective Turn one vague idea, including one broad research direction, into one continuously revised, state-governed Brainstorm document. It remains outside Package and Scope authority until the user asks to materialize it as a Draft. ## Definition - A Brainstorm is a standalone pre-Package aggregate with a governed document. - It is not a Package, Direction, or Experiment and cannot authorize a Run. - One broad research direction maps to one Brainstorm by default. - Reproduction, task migration, causal audit, ablation, risk, and similar work remain Sections or Stages when they share one core research question. - Refine the same Brainstorm in place. Do not create a sibling record for each iteration, concern, or stage. - Materialize only after discussion has made the document coherent and the user has asked to continue into Package design. - Keep the body free-form. Do not turn optional research content into mandatory fields. - Present the Brainstorm to the user as a complete document-style HTML page, not an expanded data card. The authority flow is: ```text standalone Brainstorm + iterative refinement -> agent materializes the exact revision on user request -> DRAFT_MATERIALIZE records Brainstorm provenance and the Draft Package -> research-package owns Draft refinement and finalization ``` The Brainstorm CLI writes events and content-addressed NoteRefs through the research-op gateway. The Dashboard renderer owns HTML projection