Design system archaeology
Reading a system you didn't build, and why the first 90 days look nothing like building
Reading a system you didn't build, and why the first 90 days look nothing like building
The most useful feedback your system has ever produced is on a thirty-day timer
Why every layer name, variant, and token reference is an architectural decision
How your design system vocabulary becomes AI context
The gap between what your system says and what it does used to be a minor annoyance. Now it's a structural fault.
Lessons from Baldurs Gate 3 on contracts, governance, and judgment at the edges