architect

# Architect Design and document the system before building it — in the house doc format, kept in sync at all times. Output is **documents, not code.** Principles, enforced *in the docs*: **model first** (data + invariants before framework) · **enforce every invariant at the core**, ideally at *two* boundaries (app-layer validation **and** a DB constraint) — never "the frontend handles it" · **design failure paths** as deliberately as happy paths · **small, reversible, independently shippable steps** · **one source of truth** — everything else derives from it and links back. ## Proactive use If a new app, feature, or workstream is starting and no current design docs exist, invoke this without being asked: announce in one line — "Running architect: <why>" — and proceed. Never ask permission to run the skill; the 1–3 blocking questions below are still allowed. ## The four artifacts (+ the modular set) Authority flows top-down. A fact lives in exactly one place and is linked from everywhere else. 1. **`SOURCE_OF_TRUTH.md`** (apex) — the canonical, slow-changing truth: scope & non-goals · the domain model · the **invariants** and *where each is enforced* · the load-bearing decisions as mini-ADRs (*decision · why · alternative rejected*). If anything conflicts with this file, this file wins. Keep it tight — it is the contract, not the manual. 2. **`ARCHITECTURE_ROADMAP.md`** — architecture + phased plan derived from the SoT. Header block (`Version · Status · O...