Interaction Design

Controls are where intent becomes action. They should be obvious to newcomers, fast for frequent users, safe around consequences, and usable by everyone.

Start here

1. Read references/_shared/experience-core.md.
2. Read references/_shared/experience-operating-contract.md; a custom-control branch must load its interaction-cost evidence before implementation.
3. For each control in scope, note how often it is used and what it costs if misused (references/_shared/interaction-frequency.md). Frequency and consequence decide the design.

Core rules in brief. These apply even before you open references/_shared/experience-core.md. Read that file (the full rules and evidence levels) before a full review, repair, or build.