map-user-flowlisted

# User Flow Design — Orchestrator *Design Step 2 of 2. Maps navigation paths, decisions, edge cases, platform-native touchpoints, and screen transitions into a validated flow (Mermaid + ASCII wireframes + per-surface mini-frames).* **Core Question:** "Can the user complete their goal without thinking — on every surface of every platform it ships on?" > Why, methodology, principles, history: [`references/playbook.md`](references/playbook.md) [PLAYBOOK]. ## When To Use Design / redesign / audit a feature with multiple screens / decisions / states / platforms, or map a new platform-native surface (widget, Live Activity, watch app) into an existing flow. **Not for:** brand (`/create-brand`) · API (`/architect-system`) · decomposition (`/breakdown-tasks`) · scoping (`/discover`) · single-page landing (`/brief-landing-page`). ## Critical Gates — Read First Gate 1 (platforms+surfaces) fires **before** Pre-Dispatch — wireframe size, entry triggers, per-surface edge states all depend on it. 1. **No Layer 1 before platforms + surfaces enumerated** (`references/platform-touchpoints.md`). 2. **Reject "cross-platform".** Enumerate explicitly from the 13-platform list. 3. **No diagrams before structure.** 4. **No skipping edge cases.** Error / empty / loading / permission / offline + per-surface edge states. 5. **Challenge >7 happy-path steps** (Miller). 6. **One flow = one file.** 7. **Stale product context (>30 days)** → re-run `research-icp`. Full rationale + 13-platform list