The vehicles do not see the world the way people do, so the visual system was derived from machine perception rather than chosen — and every layer above it, from token names to a control-room map, inherits that decision instead of restating it.
Two lanes on the same guideway, classified differently — one green, one violet, each carrying its own telemetry. That is the vehicle's view of the world, and the palette comes out of it.
Proves: the color argument is an observation, not taste. Everything downstream is defensible because this is where it starts. If this lands, nothing later sounds arbitrary.
Color carries state. Light carries priority. Material carries surface. Depth carries position. Every token on the page resolves to one of the four.
Proves: the system has a shape, not a style. Say channel assignments, never principles — a principle is a preference, an assignment is a constraint.
Family from the HSL hue, step from the lightness. --lum-blue-52 states its own value, so two designers naming the same swatch independently arrive at the same token.
Proves: it survives other people. This is the moment the page stops being a portfolio — run the CSS and JSON export on screen and let it download. Do not narrate over it.
The same arrival runs in the Dynamic Island, on the Lock Screen, and in StandBy. Three things never drop — the track, the position on it, and the time.
Proves: the system was tested against a hostile brief it did not write. Apple set that size. Directly relevant to a company shipping the same product to a wall display and a phone.
This control-room map came from the earlier Metro palette. Moving it onto Lumasis changed thirty-three bindings — blocked to status-bg-critical, delayed to status-bg-warning, guideway to lum-azure-22, ground to bg-canvas.
Proves: the semantic tier works rather than exists. Say the chain once, slowly — Component to Semantic to Applied to value — then stop. And volunteer the gap: state and ground are bound, ink is not, and the form is still Metro.
Metro governs what stays still. Lumasis governs what moves.
Opening turn — place it in the first two minutesThe test is whether the value identifies the component, or is supplied to it.
The component turn — earned from a mistake, not theoryRenaming broke the live site four times for zero reader-visible gain, so the vocabulary governs writing, not selectors.
The governance turn — restraint as a decisionOpacity fails to visible. A clip fails to nothing.
The resilience turn — if motion or failure states come upThey jump ahead to components.
Go to the scar immediately — hex identified the component, so a set-level property collapsed eighteen variants to one default. Then walk backward to why the tokens are shaped that way. The argument runs in either direction.
They question adoption.
A signage fabricator, a wrap vendor, one front-end engineer. Not designers pulling instances. That is why the contract is code and written rules rather than a published library — and it is the honest reason the component work is recent.
They press on production readiness.
Semantic lives in Figma and in the anatomy; the site ships primitives. Aliasing is additive, not a rename — value-derived primitives alias cleanly, so nothing has to be renamed to adopt it.
The room goes quiet.
Ask what they are deciding between. Silence is usually a scoping question they have not asked yet — whether you build systems or apply them. The answer is the map: you did both, on the same surface.
Close on what you would flag before they find it. Four things, named plainly, then stop talking. Volunteering debt at the end reads as confidence; being caught on it at minute twenty reads as an oversight.
The close