ContractBreakpoints
- Job
- Same product, three contexts
- Requirement
- must specify
- States / rules
- Inherit B&Co sm 0–599 / md 600–1023 / lg 1024+ unless overridden
- Specified means
- Strategy declared; every component has sm/md/lg
- Hardest context
- md written even if Soft PIN is sm+lg
Example
Standard three
Counter-example
“It’ll scale”
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: md written even if Soft PIN is sm+lg.
On-spec signal
Standard three
Failure signal
“It’ll scale”
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.