- Job
- Readable hierarchy
- Requirement
- must specify
- States / rules
- Locked pairing; scale steps; leading/tracking per step; 14px floor; sm behavior of the scale
- Specified means
- Faces, weights, steps, and sm rule are written
- Hardest context
- 14px-equivalent on sm dark
Inter body + Instrument Serif titles, 14px min
Type roles named with no 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.
Specify hierarchy as a system, not a font sample.
Lock body/display roles and where each is allowed.
Write the steps, weights, leading, and tracking rather than “use a type scale.”
Respect the 14px-equivalent floor from the source contract.
Document what compresses or changes at sm rather than scaling everything proportionally.
Exercise long labels, numbers, headings, and dense UI—not only marketing copy.
- 14px-equivalent on sm dark
- Long navigation labels
- Dense form help and error text
Do not specify the easy case only.
The source checklist’s hardest-context test is part of what “specified” means: 14px-equivalent on sm dark.
On-spec signal
Inter body + Instrument Serif titles, 14px min
Failure signal
Type roles named with no 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.