Who is behind this
This hub is one practitioner's vetted path through the shift from documentation a human read to infrastructure an agent executes against. Curated, annotated, and argued, not aggregated. The point of view is the product.
The named curator
The site's whole claim to authority is one named person: the curator. Here's who's behind it, the byline and the stance, in brief.
I run an enterprise design system, and I ship production software built by AI agents. At a Fortune 250 utility I have designed products used by 4.6 million electric customers and built an agentic platform used by about 8,000 people internally. That combination is still rare, and it puts me on both ends of a shift most teams are only seeing one side of.
So this is not an aggregator. Every source here was read before it was linked, and carries one line on why it matters and where it sits in the chain. The annotation is the work. The honest soft spots stay in, because the people closest to this keep them in too.
The argument is simple and specific. A design system used to be documentation a human read and interpreted. Now it is infrastructure an agent reads and executes against. The architects who get there first are the ones treating their design system as infrastructure today, not documentation. That is the bet I am making, and the one I am building on.
The medium is the message
A site about token-driven, machine-readable design that runs on exactly that.
This page, and every page, runs on the tokens it argues for. No raw values, no accent color, emphasis by inversion only.
Set in N27 for the human voice and JetBrains Mono for the machine voice. Built on DTCG design tokens, compiled to CSS custom properties, consumed only as variables.
Open the reference