roadmaplisted

# ROADMAP: project-level allocation authority <HARD-GATE>Approved, commit-bound WhitePaper and Decision authorities must exist. If either is missing, or ROADMAP work changes a current D-ID or selects a new ruling for Decision, stop and return the issue to `gmgn` for routing. ROADMAP stays at project-allocation level. It does not contain detailed Close conditions, R-AC IDs, behavior or performance thresholds, technical design, task breakdown, executable tests, evidence, or an end-to-end path.</HARD-GATE> ## Language and writing rules Before writing, load the registered `gmgn` Skill through normal discovery and follow its local writing rules. Use the active locale for artifact prose. Use `ROADMAP.md`, `type: roadmap`, `nature: normative`, and `status: draft` until approved. ## Working rhythm The primary orchestrator reads the approved Decision and its WhitePaper authority plus current project facts, then forms a recommended Milestone map and a list of unresolved allocation decisions. It resolves only material blockers with the Owner, then prepares one Author brief. The independent Author writes one complete recommended candidate without asking the Owner to approve fields or allocations separately. Ask before the candidate only when an unresolved choice is irreversible or creates a material external commitment and cannot be safely recommended or deferred. Combine related blockers into the smallest useful question. Do not ask for facts already decided by WhitePaper, Decisio