ContractMotion
- Job
- Feedback without theater
- Requirement
- must specify
- States / rules
- Function (feedback vs orientation vs decoration); duration ceiling; reduced-motion
- Specified means
- Personality + ceiling + prefers-reduced-motion
- Hardest context
- Reduced-motion publish confirm
Example
Ghost-fast 150–200ms
Counter-example
Expressive morph on every nav
How this lives in Building Blocks
Representation: Shared foundation / token / behavior guidance.
Building Blocks should provide shared guidance, semantic roles, examples, and reusable implementation hooks where appropriate. Each product maps those roles to its own theme and documents any justified exceptions.
Do not specify the easy case only.
The source checklist’s hardest-context test is part of what “specified” means: Reduced-motion publish confirm.
On-spec signal
Ghost-fast 150–200ms
Failure signal
Expressive morph on every nav
Catalog connection
The product-local Catalog should show this row’s actual state for that product using the Catalog contract. Building Blocks documentation can define the baseline, but it does not make a product’s row Specified, Designed, or In code by itself.