Motion Frequency Budget
constraint · created
Evidence record
- What is verified
- Uses in published workflows: 0
- Revision
- Version 0.1.1
- Validation status
- Public-sanitized publication; no independent validation is claimed.
What this is and why
Binds the admissibility of a motion to how often the reader will see it. A transition that is pleasant once is an obstruction on the hundredth repetition, so the frequency of an interaction is declared before the motion is designed. The tier decides whether the motion is admissible at all — not how long it runs, because the style guide permits exactly one duration and a fraction of a single permitted value is a forbidden value. At the highest tier no motion is permitted; one tier below it, motion is permitted only as feedback on the reader's own action. Keyboard-initiated actions carry an absolute prohibition rather than a budget: they are dispatched faster than any animation can complete, so animating them makes the interface feel disconnected from the key that was pressed. The declared frequency tier is part of the component's contract and is checkable, which is what separates this from the advice it derives from.
Where it was applied and what it helped deliver
No published workflow records this capability yet — the count includes only ledger mentions that resolve.
Metadata and provenance
- id
- tal-constraint-motion-frequency-budget
- type
- constraint
- version
- 0.1.1
- origin
- created in Talomnia
- lifecycle
- public_sanitized
- tags
- design, motion, accessibility, frequency, talo-0163
The source is the private knowledge repository; only the sanitized public projection reaches this site.
verified · tal-constraint-motion-frequency-budget · v0.1.1