ContractDark theme
- Job
- Character, not invert
- Requirement
- must specify
- States / rules
- Semantic swap; surfaces stay lit; brand re-specified
- Specified means
- Dark tokens, not filter: invert
- Hardest context
- Dark chrome, light canvas
Example
Warm dark stone
Counter-example
Invert the document
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: Dark chrome, light canvas.
On-spec signal
Warm dark stone
Failure signal
Invert the document
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.