write-designlisted

# Design stage: requirements → architecture and executable boundaries <HARD-GATE>`Requirement.md` must exist and have independent-critic plus primary-orchestrator review. Otherwise return to `write-requirement`. If design work exposes changed upstream meaning, route to the WhitePaper, ROADMAP, Goal, or Requirement authority instead of redefining it in Design.</HARD-GATE> ## Language and contract Before writing, load the registered `gmgn` Skill through normal discovery and follow its local writing contract. Use the Requirement locale for artifact prose. `Design.md` uses `type: design`; an independently needed `Contract.md` uses `type: contract`; both are normative. The Design-stage candidate is: - `Design.md` alone when there is no cross-unit interface; or - one Design Bundle—`Design.md` plus required `Contract.md` at the same Git commit—when current work crosses independently developed module, task, or team boundaries. The contract itself is mandatory for every such boundary; only the separate file is conditional on that boundary existing. Do not create an empty `Contract.md`. Do not split a normal in-process module into services merely to justify a contract artifact. Design acceptance makes the bundle an `approved` working baseline for implementation, not the final frozen contract. Controlled coding evidence may produce a newly reviewed working commit; `close-milestone` freezes the final implementation-matching Contract as `closed`. ## Design content - Derive Desig