# Pulsepath UX flow

1. **Title shell** — Play, level selector, How to Play, muted procedural sound toggle.
2. **FTUE** — three steps: goal, drag-and-release-to-route with click/keyboard fallback, then gate success/failure feedback.
3. **Board** — source, receiver, walls, phase gates, route, beat counter, Clear, Hint; release commits the pulse.
4. **Failure** — route remains visible; the failed gate is named and the player can revise.
5. **Success** — pulse trail completes, board number advances, Replay and Next appear.
6. **Level selector** — 50 deterministic buttons with completion state.

First-run completion is persisted only after the first valid route extension, never merely by opening
or dismissing the FTUE.