vibey-domain-modellisted

# vibey domain model Read `docs/plans/domain-model.md` before touching `domain/`. This skill is a compressed orientation; the full spec lives in that doc. ## Phases Six numbered phases plus optional visual interstitial: ``` INTAKE → ① DESIGN → [optional VISUAL_DESIGN] → ② BUILD ⇄ ③ REVIEW ▲──────────────────────────┘ │ │ ③ ── user declines deployment ──────────────────────→ DONE (local) │ user opts into deployment ▼ ④ DEPLOY_DESIGN → ⑤ DEPLOY_EXECUTE → ⑥ DEPLOY_REVIEW → DONE (deployed) ``` Interactive phases (talk to the user): ①, ③, ④, ⑥, VISUAL_DESIGN. Autonomous phases (unattended): ②, ⑤. **Loop-backs:** - `BUILD → DESIGN` when blocked on ambiguity (spec insufficient). - `REVIEW → DESIGN` (default) or `REVIEW → BUILD` (fast path when every finding is `unambiguous`). See ADR-0010. - `DEPLOY_REVIEW` can route to ④, ⑤, or back to ①/②/③ depending on the failure classification. **Opt-in gates:** - Visual design: after ① accepts a buildable spec, vibey asks whether to enter the visual-design interstitial. Declining takes the `DESIGN → BUILD` edge directly. - Deployment: after ③ has no open product findings, vibey asks whether to work on deployment. Declining records `completion_mode = "local"` and transitions to `DONE` without enqueueing any Azure job. See ADR-0014 (optional visual-design and deployment opt-in). ## Jobs Job kinds map to phases: - `design.interview`, `design.rese