Selling what we practise
The studio's site is built with the architecture it sells. That is a constraint, not a turn of phrase.
1 min read
Yorro sells agent-native architecture advisory. Doing so from a site whose business logic lived inside interface components seemed hard to defend.
The rule we set ourselves is simple: every capability of the site carries a name,
parameters and a one-line description. setTheme, setLocale, filterLabs,
openService. Anything that cannot be described that way is not a capability, it is
interface state — and it stays in the component.
What it changes immediately
A command palette becomes a listing of the registry rather than a feature to build. Tests are written against Actions rather than against clicks. And the day an agent has to drive the site, there is nothing to extract: the layer is already there.
What it costs
Discipline while writing. A button that “just does a thing” suddenly demands a decision about whether it deserves a name.