ContractTouch + no hover-only
- Job
- Operable on phone
- Requirement
- must specify
- States / rules
- 44×44; no hover-only action (already universal in the standard — point at it)
- Specified means
- Point at standard + product exceptions if any
- Hardest context
- Overlay item at 375
Example
44px hit
Counter-example
Hover-only delete
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: Overlay item at 375.
On-spec signal
44px hit
Failure signal
Hover-only delete
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.