ContractContainment model
- Job
- How surfaces sit
- Requirement
- must specify
- States / rules
- Elevation vs hairline border vs mixed — lock one
- Specified means
- One rule for cards/panels
- Hardest context
- White card on warm stone
Example
Flat + border
Counter-example
Mix of shadows and borders with no rule
How this lives in Building Blocks
Representation: Shared guidance + product-local policy.
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: White card on warm stone.
On-spec signal
Flat + border
Failure signal
Mix of shadows and borders with no rule
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.