White paper · Design · July 2026

The Design System That Can Say No

When your design decisions become governed contracts. A paper for designers.

Inside this paper

  • Nobody standardized the decisionsValues were shared. Meaning never was.
  • The ideaTokens with usage rules, components as contracts.
  • Canon, not FigmaMoving authority ends the sync war.

The industry standardized how to write values down. Nobody standardized the decisions.

Nobody standardized the decisions

Design systems standardized the values — colors, spacing, type. They never standardized the decisions: which color means what, where a component may and may not be used, what accessibility floor is non-negotiable. Then AI made the gap acute. In a published May 2026 audit, a generation tool asked to generate a design system and then build a dashboard from it introduced twelve undeclared colors, swapped to system fonts, and hardcoded off-scale spacing in one session. The auditors' conclusion: traditional drift accumulates over months; AI drift happens in a single session.

The idea in one paragraph

Make the design system — values and decisions — the governed source of truth: versioned, structured documents that humans read as documentation and machines read as contracts. Tokens carry their usage rules, not just their values. Components are contracts: variants, states, prop signatures, and accessibility requirements expressed as explicit requires and forbids. Every document has an owner, a version, a review cycle, and a dependency graph. And everyone queries the same canon — designers, developers, and agents — instead of designers reading Figma, developers reading the code, and agents reading neither.

Every canon document carries

01

An owner

02

A version

03

A review cycle

04

A dependency graph

Canon is the source of truth, not Figma

In the standard model Figma is the source of truth and code is a translation of it, which is why every unsolved problem in the field is a sync problem. Two sources of truth guarantee a sync war with no end, because neither side concedes authority. We resolved it by moving authority: the canon is the source of truth, the coded library is its reference implementation, and every surface is built from it. You can keep a drawing tool. What changes is its status — sketchpad, not system of record.

The standard model

Two sources of truth

Code is a translation of the drawing. Neither side concedes authority, so every unsolved problem is a sync problem.

The canon model

One source of truth

The coded library is the reference implementation. A drawing tool stays, as a sketchpad rather than the system of record.

This is not a proposal. It is how we run our design practice at Career Highways today.

Read the full paper

The complete paper: why decisions were never standardized, tokens and components as contracts, and how authority moved to the canon.

Related

Explainer

Design

Tokens and component contracts govern the generated screen, so the design system stops being a suggestion.