write-decisionlisted

# Decision authority <HARD-GATE>Creation requires an approved WhitePaper commit. Revision requires the current approved Decision authority. The human owner decides both whether a candidate belongs here and which option is accepted. Pause only downstream work whose result could change while a material candidate is unresolved. If the candidate changes the WhitePaper problem, goal, scope, harm order, or invariant, return it to `gmgn` for upstream revision first.</HARD-GATE> ## Language and artifacts Load the registered `gmgn` Skill and follow its writing rules. Use the WhitePaper locale. Maintain these project-root artifacts: - `Decision.md`: `type: decision`, `nature: normative`; current accepted rulings only. - `DecisionLog.md`: `type: decision`, `nature: descriptive`; accepted change history only. They form one controlled change batch. Normal downstream stages read `Decision.md`, not `DecisionLog.md`. Read the Log only to preserve ID history or investigate a change. ## Place a ruling in Decision Decision may own any current ruling needed by planning or active work, including a ruling limited to one Milestone, requirement, module, interface, implementation, or Task. Scope is not a jurisdiction filter. Keep a candidate only when it is an explicit choice among material alternatives and one or more downstream artifacts must obey or link it. Do not turn derived content, document state, execution status, evidence, commands, or history into a ruling. Once recorded: - `Deci