Every design system begins as a garden and ends as a homeowners' association. The first tokens are planted with genuine love — a spacing scale, a color ramp, a type ramp with names like “display-lg” that someone chose in a moment of hope. Five years later there is a committee, a wiki, a deprecation policy, and a designer crying in a Figma comment thread because she moved a button four pixels off the sacred grid.^[1]

The pitch for a design system is consistency, and consistency is genuinely good. So is mowing your lawn. The trouble starts when consistency stops being the floor and becomes the ceiling — when “can we build this?” is answered not by judgment but by a search of the component library.

The covenant

An HOA does not forbid beauty. It forbids variance, and beauty is a variance that survived. Design systems forbid variance with better tooling: lint rules for tokens, visual regression tests that flag a one-pixel deviation with the urgency of a smoke alarm, contribution processes with the warmth of a building permit office.^[2]

The result is the great flattening: a thousand products that all look like the same product wearing different logo. Not because designers lack taste, but because taste is a variance and variance fails CI.

A system that cannot produce a surprise cannot produce a classic.— RAW SIGNAL, ISSUE № 143

Break the grid you can see

This site runs on a grid. You can see it — that is the point of the borders. A grid is a tool; a covenant is a grid that has started billing you. The difference is governance: a tool answers to the person holding it, a covenant answers to itself.

So keep your tokens. Keep your spacing scale. But budget for violations the way you budget for tech debt, and treat the designer who breaks the grid on purpose — and can tell you why — as the most valuable person in the room. The HOA will survive one purple door. It might even deserve one.