---
title: "Governance for a team of two"
url: /cases/governance-for-two
description: "A B2B car-loan platform front end built by two people with no designer. Vendored shadcn/ui, one skin file, and numbered decisions that each name a lint or a test."
---

## §0 · problem

# 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.

## §1 · built

### What was built

Vendored shadcn/ui as owned code, one skin file that reads tokens only, and 46 numbered decisions [claim case6-decisions: Own project; source: author's project, internal; confirmed]. Each decision has Rule, Why, Rejected and Evidence. Every rule names its mechanism: a lint or a test.

The prototype from a generation tool is evidence, never authority.

## §2 · taught

### What it taught

Two people run governance that used to need a design-system team, because the agent does the reading and CI does the policing.

## §3 · open

### What is still open

Accessibility is stated as a direction, not as a claim, because nothing measures it yet.
