A White-Label Design System — One Token Source, Every Surface

The problem

A design system that lives in a document is a design system that drifts. The moment two surfaces — a website and a printed resume, say — each keep their own copy of “the brand,” they diverge, and someone spends an afternoon a month reconciling hex codes by hand.

We wanted one source of truth for color, type, and spacing that compiles to every surface, so that consistency is a property of the build rather than something people have to remember.

The architecture

The system is a three-tier DTCG token model — primitive, then semantic, then component — built with Style Dictionary v4. The build is pure Node, which matters here: it runs cleanly on a locked-down Windows machine where compiled toolchains do not.

Only the bottom tier is per-brand. A new brand is one file defining the base color slots and fonts; the semantic and component tiers above it are byte-identical across every brand, because they are generated from the same source rather than copied and kept in sync by hand. That constancy is what turns white-label from an aspiration into a guarantee. The same tokens compile out to web CSS variables and to print LaTeX. A cap-lint step enforces the palette’s surface-area discipline so the accent color stays scarce — six of six checks green.

What we measured

The strongest proof is the page you are reading. This website vendors those tokens, and its build fails if they drift from the source — the design system is not documentation the site is meant to follow; it is a dependency the site cannot compile without.

And when the lab changed its own identity, the whole site changed its palette, type, and geometry by swapping a single brand file and rebuilding — one session, one file, every surface. Four brands now compile from the one source.

What transferred to the lab's method

The token pipeline is the reason a rebrand is an afternoon rather than a quarter. It also set a pattern the lab reuses everywhere: put the source of truth in one place, make the build enforce it, and let consistency be mechanical instead of remembered.

It is the same instinct behind the client portal’s write-pinning and the health OS’s model-first sequencing — make the correct path the only path the system can take. Discipline that depends on vigilance eventually fails; discipline the build enforces does not.