spec-system-map

Create or amend spec/system-map.md, the high-level map of how the project is shaped. This is narrower than a generic ARCHITECTURE.md: it names project-wide structure, boundaries, flows, storage/external systems, invariants, and pointers to deeper docs.

Use this when

• scoping or documenting architecture: system shape, runtime boundaries, core flows, invariants, or storage/external systems
• spec/system-map.md is absent and the project wants a first system map
• spec/system-map.md exists but its shape, boundaries, flows, invariants, or pointers have drifted from the repo
• deciding whether a change belongs here versus spec/charter.md (why/direction) or spec/capabilities.md (capability contracts)

Execution contract

Mode router

• create: use when spec/system-map.md is absent or the user asks for a first system map.
• amend: use when the file exists and the user asks to update architecture shape, boundaries, flows, invariants, or links.

When no mode is specified, route by file state. Create spec/ if needed.