Map · everything in the tree
Every page, and what it proves.
Nothing below names a product or a client. Every count is read from the data it describes — the token set, the dictionary, the stylesheet — so this page cannot claim a number the tree does not have. This map is the only page it does not list.
The pages
Each one proves one thing.
Index
The opening argument: three voices, one token set, and the workflow that turns a positioning doc into a scored page.
01Elements
Every token, type role, control, surface, state and piece of furniture rendered live, each with the per-component contract underneath it — anatomy, the voice each modifier carries, states, tokens consumed, accessibility, finish behaviour.
02Palettes
The colour layer on its own: both shipped palettes in both modes, every contrast rule measured, and the two earlier sets kept under renamed tokens.
03Heroes
Every OVERTURE the system owns, rendered live at full width with the content precondition that earns it — four of them ports of heroes that shipped on real sites.
04Codas
Every CODA the system owns, chosen by what the page is actually asking for — a described task, a climax, a summary in numbers, the next page, or nothing at all.
05Finishes
Satin and matte rendered from identical markup: what a finish moves, what it leaves alone, and which material each one is for.
06Textures
Nine quiet fields and ten treatments, each derived from ink, accent or warm, shown on ground, band and gate.
07Atelier blocks
The editorial voice: heroes, spines, specimens, marked gaps — one plate per instrument with its aesthetic notes.
08Chrome blocks
The SaaS marketing furniture: heroes, feature canons, pricing, FAQ, forms, codas.
09Product blocks
The evidence register: browser frames, product previews, rate cards, stat rails, tech stacks.
10Compose
The reference performance: nine movements, three voices, every seam annotated with its compatibility score.
11Bold
The system at maximum volume — giant display type, a mesh plane, gradient and blurred light, without breaking a single law.
12Sleek
The system at minimum volume — precision fields, a browser frame, a rate card and a stat rail, everything on the hairline.
13Not found
The 404 as a real movement rather than an apology: the map, offered as the primary control.
14Baseline
Every block stacked on one page, noindex, so the measurement tools have a single stable target to crawl and shoot.
Counted, not claimed
What the tree actually holds.
- live tokens
- 161
- plus 22 ramp steps and two kept palettes
- instruments
- 49
- blocks and inline patterns, three voices
- contracts
- 34
- per-component, with every modifier mapped
- pages
- 16
- this one included; all placeholders, delete or keep as a styleguide
The documents
Read them in this order.
The pages above are specimens; these are the contract. A layout agent composing a new site reads them top to bottom, then writes the score before any markup.
- design/DESIGN.mdWhat exists: the voices, the two finishes, the token names, the component layer and its voice-is-a-modifier map, the block catalog.
- design/TOKENS.mdGenerated. Every token value in both finishes and both modes, each token’s use/never, and every contrast rule measured.
- design/PALETTE.mdHow colour is decided: the four rules, the solver, the one-file swap.
- design/COMPOSITION.mdThe score grammar: voices, ten movements, planes, textures, cadence, seams. Written before any markup.
- design/ATLAS.mdEvery instrument judged in use: character, precondition, seam, supercharge; the seam index; the finishes.
- design/SPEC.mdEngineering depth from the donor build — routing rules, verification caveats.
Start here