designlisted

# design — architecture before code Turn aligned intent into a concrete architecture the way a senior engineer does: deep modules, clear boundaries, decisions recorded with their *why*. Run this after `align` and before `build`. ## Steps 1. **Read the Spine.** Load the acceptance criteria from `journal.md` and the existing `context.md` / `conventions.md`. If there are no criteria yet, run `align` first. 2. **Detect the mode.** - *Greenfield* — `context.md` is thin/empty and there are no modules yet. Architect from scratch: include stack/scaffolding decisions. - *Existing codebase* — read the current architecture first (key modules, patterns) and the existing ADRs in `.spine/decisions/`. Design to fit; respect what's there. 3. **Map the decision space.** Identify the consequential choices — see [architecture-questions.md](architecture-questions.md). Typically: data model, module boundaries, key interfaces, external dependencies, data/state flow, and failure modes. 4. **Interview.** Ask one question at a time, multiple-choice where possible, only on decisions that matter. Don't ask what the Spine already answers. 5. **Propose options.** For each major decision, offer 2–3 approaches with trade-offs and a recommendation. Favor [deep modules](interface-design.md) — small interface, deep implementation — clear boundaries, and YAGNI. Don't over-engineer. 6. **Record the architecture in the Spine.** - Update `context.md`: the arch