prototypelisted

# Prototype ## Purpose A prototype is disposable evidence that answers one design question. It should make uncertainty visible before production implementation starts. Use the smallest evidence that lets the user or agent learn something concrete. Delete it or absorb the validated decision when done. ## Pick The Branch First identify the question. - Logic prototype: use when the question is about business rules, data shape, state transitions, command flow, or API feel. - UI prototype: use when the question is about layout, interaction, hierarchy, density, or visual alternatives. If the question is ambiguous, inspect the surrounding code and state the assumption before writing anything. Read `references/logic-prototype.md` or `references/ui-prototype.md` after choosing the branch when implementation details matter. ## Rules For Both Branches 1. Mark every created artifact or code path as throwaway in its name, route, README, top comment, or handoff. 2. When the evidence is runnable code, keep it near the relevant module, reuse the project's runtime and task runner, and provide one command or URL that starts it. 3. Avoid persistence unless persistence is the exact question. When it is, use a disposable local file or scratch database whose name makes cleanup obvious. 4. Skip production polish, broad error handling, and abstractions. 5. Surface the state, variant, or decision being tested. 6. Capture the answer in an existing project artifact or the final summary; prese