architecture-baselinelisted

# Architecture Baseline Turn what the product promises its users into what the system guarantees, and write it down so every feature built afterwards is built the same way. **Read `../../CONVENTIONS.md` first.** It carries the shared rules — stages, where work is saved, the tree, markers, interview rules, precedence, gates, decision records and the baseline status footer. This skill does not repeat them. This is **stage 5 of 5**, and the last before building starts — though the revision beat described in `../../CONVENTIONS.md` may bring any of these documents back. ## What this prevents The constitution stops eleven specs using eleven vocabularies. This stops eleven implementations inventing eleven patterns — eleven models of the same entity, eleven error conventions, eleven answers to what happens when the network dies. That is the test for every section: **name the divergence it prevents.** A section that cannot is decoration and should be cut. ## What your job is Not to design features. **To make every decision that eleven parallel implementations would otherwise each make separately — once, here, in a form that can be checked.** Stage 3 deliberately deferred all design to you. Sections 1–3 below are unambiguously design work and are yours to do. ## Before starting Establish the project root as `../../CONVENTIONS.md` describes. Read, in this order: 1. `.specify/memory/architecture.md` — the constraints from stage 3, and the **Deferred to the baseline** list,