brainstormlisted

# Brainstorm → WhitePaper <HARD-GATE>In creation mode, do not enter `roadmap`, create execution documents, or write implementation code before the WhitePaper candidate is committed locally, an independent Critic reviews that commit, and the owner approves it. In revision mode, pause only dependent work whose premise changed until the owner approves the semantic delta at a new commit. “The project is simple” is not a bypass.</HARD-GATE> ## Language and contract Before writing, load the registered `gmgn` Skill through normal discovery and follow its local writing contract. Use the active project/user locale for artifact prose. The WhitePaper uses `type: whitepaper`, `nature: normative`, and stable English frontmatter tokens. ## Working rhythm The primary orchestrator stays in the owner dialogue, asks one question at a time, records rulings, and challenges premature implementation or solutions disguised as requirements. Before writing, it selects and records the actual WhitePaper writer. Prefer the primary session because it already holds the complete Brainstorm context; delegate to an Author only when a bounded context package and a concrete isolation, specialization, or parallelism benefit outweigh the handoff cost. A delegated Author or Researcher receives a complete brief before creation and is single-use. Dispatch an independent fresh Critic only after committing the complete candidate locally. Use as needed: - repository and user evidence; - primary-source research