A design system that remembers why
As Design Lead at an enterprise AI platform company, I rebuilt the product's frontend language with the frontend team: a token-governed component system, an institutional memory read by humans and AI agents alike, and a prototyping pipeline where anyone in the company builds with the production components by typing plain English.
The same dashboard, two years of debt apart
We didn't rip Ant Design out — the system replaced its surface token by token, wrapping it in OI-prefixed components, so users never met a cliff-edge release. Drag the line.
| Workload | GPU | Util% | Status |
|---|---|---|---|
| llama-70b-ft | 16 | 91 | ok |
| embed-batch-cron | 4 | 64 | OK! |
| asr-eval-suite | 8 | null | wait |
| vision-preproc | 1 | NaN | ERR |
| Workload | GPU | Util% | Status |
|---|---|---|---|
| llama-70b-ft | 16 | 91 | ok |
| embed-batch-cron | 4 | 64 | ok |
| asr-eval-suite | 8 | — | waiting |
| vision-preproc | 1 | — | error |
No hex above this line
Every visual value resolves through a three-layer chain, and a component may never touch a raw value. That one prohibition is the whole trick:
Above the tokens sits the six-layer atomic hierarchy — and skipping a layer fails the build, not the review. The rest of the foundation is deliberately small: 24/12 brick spacing, one chrome accent, Inter for UI and Plex Mono for data, two motion curves.
A system that remembers why
Institutional memory, treated as a product: written once, rendered twice — prose for people, structured rules for machines — so a new engineer and an AI agent read the same canon before touching a component.
The vault itself is the one artifact this site does not serve: it holds the team roster, the full decisions log and the roadmap, and its own security note bars it from public deploys. That refusal is part of the design.
91 rules, numbered like case law
Two rules were retired and their numbers stay vacant — the sequence carries its own history. Change ships as numbered waves, W11 past W110; there has never been a big-bang release.
We built our own tool, then killed it in a day
We built our own prototyping tool, shipped two phases, and killed it in a day when the evidence said no. DECISION W110 — THE FULL ENTRY, REASONING AND ALL, IS IN THE LOG
A browser sandbox can't import the production component library, so every prototype degraded into a CSS imitation of the system. The post-mortem went into the log like any other entry — and the replacement renders from the library itself:
None of this hands taste to a model. The AI builds under the same constraints as any engineer — the rules, the tiers, the cold-eyed verifier — and when it refuses a request because a component doesn't exist, that refusal routes back to design as a demand signal. The last piece was teaching: an interactive atomic-design class for the whole company, public below as Everyone Builds.
Nothing below is a screenshot
These are the actual artifacts — the story site in its own tokens, the deck of UX problems that produced the rules, the class that taught the company to build — served from this domain, running live inside this page.
Nobody waits for a designer any more
The measure of the system is who uses it. Nobody waits for a designer to try an idea any more — a PM with a sentence of plain English gets a working prototype in the product's own components — and the design conversation moved from pixels to rules: when we disagree now, we cite a number, look up why it exists, and either follow it or retire it in the log.
Source notes
- Token count (3,491) taken from the system's own token page.
- Brain figures (378 documents, 6,683 cross-links, 17 sections) computed from the vault manifest.
- Wave and rule numbers (W11–W110+, 91 rules with two retired) from the append-only decisions log.
- Company and product anonymised; the artifacts are served in full on this domain — the story site, the deck and the class, embedded above. The DS-Brain vault itself stays internal, deliberately.