Governance for a team of two
Level 4 · 2026 · a B2B car-loan platform
Two people build the front end. There is no designer, no design-file library and no component workshop. Governance used to need a design-system team.
What was built
VendoredCopied into your repository and owned there, not installed as a package. shadcn/uiA set of open-source components that you copy into your code. Agents know it well. as owned code, one skin file that reads tokensA named design value, for example a color or a spacing step, kept as data. DTCG 2025.10 gives the file format. only, and 46 numbered decisionsA written choice of the team, with an id, a reason and the check that enforces it. On this site, a row of the register.. Each decision has Rule, Why, Rejected and Evidence. Every rule names its mechanism: a lintA script that finds where code or content breaks a rule. or a test.
The prototype from a generation tool is evidence, never authority.
What it taught
Two people run governance that used to need a design-system team, because the agentAn AI program that writes and changes code, for example Claude Code or Cursor. On this site, "agent" means a coding agent. does the reading and CIContinuous integration: the checks that run on each change of the code. does the policing.
What is still open
Accessibility is stated as a direction, not as a claim, because nothing measures it yet.