- Job
- Information vs air
- Requirement
- may defer
- States / rules
- One density or two (list vs editor)
- Specified means
- If deferred: name the job not needed
- Hardest context
- Data-heavy table on sm
List compact, editor comfortable
“Comfortable if data-heavy” with no pick
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: Data-heavy table on sm.
On-spec signal
List compact, editor comfortable
Failure signal
“Comfortable if data-heavy” with no pick
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.