A brand system is not a PDF. It is the set of decisions an engineer can act on without asking a designer.
Most identity work arrives as a document: a wordmark, a palette, a grid, and forty pages explaining them. Then the build starts, and every page raises a question the document never answered. What is the hover state? What happens at 390px? Which grey is the disabled grey? The team guesses, and a year later the product and the brand no longer look related.
We treat the system as production work from the second week. Colour, type, spacing and radius are written as tokens with the names the engineers will use in their own panel, not as swatches in a deck. Components are drawn against real content — the longest client name, the shortest headline — and reviewed in the browser rather than in a mockup.
If a rule cannot be written as a token or a component, it is not a rule yet — it is a preference.
What ends up documented is narrow on purpose: the decisions that repeat. Everything else stays in the components, where it cannot drift. The handover is a library and a short README, not a manual, and the studio stays on the file for the first weeks in market so the first exceptions get answered by the people who set the rules.
A year after launch, the test is simple: can their team ship a new page without calling us, and does it still read as the same brand? On Halcyon, three markets went live in one week and nothing was redrawn after handover. That is the only measure of a system we trust.
.svg)
