prototypelisted

# Prototype A prototype is **throwaway code that answers a question**. The question decides the shape; the verdict outlives the code. ## Pick the branch Identify the question from the prompt and the surrounding code. If genuinely ambiguous, ask when the user is present; otherwise match the surrounding code (backend module → logic; page or component → UI) and state the assumption at the top of the prototype. Getting the branch wrong wastes the whole prototype. - **"Does this logic / state model feel right?"** → [LOGIC.md](LOGIC.md): a tiny interactive terminal app that pushes the state model through cases that are hard to reason about on paper. - **"What should this look like?"** → [UI.md](UI.md): several structurally different variants on one route, switchable via `?variant=` and a floating bottom bar. Single round by default; UI.md's converge mode runs repeated rounds down the visual design tree when the user (or a Decision Map entry) asks for it. Converge still only chooses a direction, at finer grain — it never becomes the production build. ## Rules (both branches) 1. **Throwaway from day one, clearly marked.** Locate it next to the module or page it prototypes so context is obvious; name it so a casual reader sees prototype, not production. Obey the project's existing routing and task conventions — invent no new top-level structure. 2. **One command to run**, via the project's existing task runner. The user starts it without thinking. 3. **