write-requirementlisted

# Requirement.md: single milestone requirement authority <HARD-GATE>`Goal.md` must exist for an initiated milestone; otherwise return to `write-goal`. If requirement work exposes a changed WhitePaper, ROADMAP, or Goal premise, route to its authority before editing Requirement. Do not prescribe implementation structures in requirements or redefine upstream meaning here.</HARD-GATE> ## Language and contract Before writing, load the registered `gmgn` Skill through normal discovery and follow its local writing contract. Use the Goal locale for artifact prose. Keep filename `Requirement.md`, `type: requirement`, and `nature: normative`. ## Requirement content - Derive Requirement from the approved Goal. Carry ROADMAP acceptance scenarios only through their mapped Goal slices. Design, Task, implementation, tests, or evidence may trigger a controlled revision but cannot silently define or redefine Requirement. - Translate each in-scope Goal slice 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 slice or externally imposed invariant. - Give each R decidable ACs `R1-AC1`, ... using enough observable precondition, action or inspection, and result to determine pass or fail. Given/When/Then is optional syntax, not a mandatory format. Numeric and static constraints may state their decision rule directly. Use unambiguous observable language; terms s