prototypelisted

# Prototype a decision Build the smallest experiment that answers the question, in a representative environment. A prototype produces evidence for a decision, not a production feature. ## 1. Resume and bound the experiment 1. Read the request, project instructions, and existing issue or interview record, including accepted choices, prerequisites, and evidence. Reuse settled framing. 2. Follow project conventions to consult relevant domain definitions, pending accepted changes, and system contracts. Resolve consequential conflicts; distinguish experimental assumptions from accepted meanings and implemented behavior. Missing conventions call for targeted clarification, not automatic project setup. 3. Establish question, scope/exclusions, scenarios, constraints, decision owner, stopping evidence, and where the interview resumes. Distinguish a measured fact from a preference requiring the owner's judgment. 4. Verify execution authorization, access, and representative inputs. A prepared brief or a ready label alone does not authorize building or external writes. | Request | Action | | --- | --- | | Choice requires observing behavior | Prepare/run the bounded experiment within authorization | | Only source evidence is missing | Return a research prerequisite rather than build a demonstration | | Behavior already settled | Propose implementation; do not reopen design for ceremony | | Preparation only, read-only mode, or unmet prerequisite | Retain the experi