Setup and domain model

Stage contract

• Stage: 0. Setup (once per repo) + cross-cutting upkeep · Kind: method
• Inputs: the repo; whatever domain terms and decisions surface as the flow runs.
• Outputs: CONTEXT.md (glossary) and docs/adr/ (decision records), created lazily and kept live.
• Entry gate: first time through the flow in this repo (no CONTEXT.md / conventions recorded), or a term/decision needs pinning down mid-flow.
• Done when: conventions are recorded; every term the flow relies on has one canonical definition; every hard-to-reverse decision is an ADR.
• Next: the stage you were routed to — usually the designing-with-7w3 skill.
• Maintains: it owns CONTEXT.md and docs/adr/; every other stage keeps them live.

Why this exists

The whole flow rests on the invariant the document is the source of truth — design, spec, and decisions are the record; code realizes them. That invariant needs a concrete home, or it stays a slogan. These two artifacts are that home: