write-requirementlisted

# Requirement.md: single milestone requirement authority <HARD-GATE>An approved, commit-bound `Goal.md` and the current approved Decision must exist for an initiated milestone. If either authority is missing or requirement work exposes a changed WhitePaper, Decision, ROADMAP, or Goal premise, stop and return the issue to `gmgn` for routing. Do not prescribe implementation structures in requirements or redefine upstream meaning here.</HARD-GATE> ## Language and writing rules Before writing, load the registered `gmgn` Skill through normal discovery and follow its local writing rules. Use the Goal locale for artifact prose. Keep filename `Requirement.md`, `type: requirement`, and `nature: normative`. ## Requirement content - Derive Requirement within the boundaries of the approved Goal, applicable D-IDs, explicitly sourced external constraints, and confirmed Owner answers obtained through the clarification process below. Translate a D-ID into R/AC only when it creates observable behavior or a Requirement-owned constraint; an architecture-only ruling remains linked input for Design. Later documents, implementation, tests, or evidence may expose a needed revision but cannot silently define or redefine Requirement. - Translate every Goal Close outcome into the smallest necessary set of numbered requirements `R1`, `R2`, ... . Each R states one coherent required behavior, capability, or constraint and names its owning Goal Close outcome or external constraint. Goal