spec-constitutionlisted

# Spec Constitution **Stage 1 of 6 — Constitution.** Before doing anything else, print this banner so the user can see where they are in the chain, filled in for this run: ```markdown > **The spec chain — stage 1 of 6 · Constitution** > > **▶ 1 constitution** · `2 spec` · `3 tasks` · `4 implement` · `5 drift` · `6 refactor` > > **Behind you:** nothing — this is the start of the chain. > **After this:** `/spec-architect` writes the spec that inherits this document. ``` Skip straight to `/spec-architect` if the repo's conventions are already settled. Then begin the workflow below, naming each phase as you enter it. A user who cannot tell which step they are on cannot tell whether to interrupt. A constitution answers one question: *what is true about this repository regardless of what we are building this week?* That is a narrow question, and keeping it narrow is the whole job. The moment a constitution starts describing features, it becomes a spec that nobody updates. The moment it lists aspirations nobody enforces, it becomes decoration — and a document readers have learned to ignore is worse than no document, because the next reader still trusts it. ## The one rule **A rule earns its place only if you can name what breaks when it's violated.** - *"Write clean code"* — nothing breaks, because nothing is specified. Delete it. - *"`domain/` imports no framework"* — business logic dissolves into controllers and becomes untestable. Keep it. - *"Prefer functional style"* —