Golden Gate 1.0.1: freezing a design system AI can't break

24 locked contracts, a 29-gate slop test, and why versioning your design system is what keeps AI output on-brand at scale.

Behind the scenes drop. This one is for the builders.

The problem nobody warns you about

Give an AI your brand colors and it does great work… the first time. The tenth time, it drifts. A slightly different radius here, an invented button style there, a hero that’s 90 percent right. Multiply by every page, email, and asset AI touches and you get slow-motion brand erosion. Each output looks fine alone. Together they look like slop.

Design systems solved this for software teams decades ago. The fix carries over cleanly: treat your brand like a versioned contract, then make every generator build against the contract.

What we froze

On June 12 we cut the first release and gave it a bridge name: Golden Gate v1.0.0. The 1.0.1 patch followed on July 8. Inside the freeze:

• 24 block contracts. 20 leaf blocks and 4 containers, every field, fallback, token, and composition rule filled in. The complete vocabulary a page is allowed to speak.
• A surface enum. Sections declare paper, brand, dark, or stage. They never declare a color. Unknown value falls back to paper, so nothing breaks loudly.
• system.json. One machine-readable file carries the whole registry. The renderer reads it, the AI author reads it, the lint reads it, the docs build reads it. One source, zero drift.
• Reserved names. Future motion and imagery recipes are named and parked NOW, so they can activate later without breaking anything.

The compatibility promise

Four rules hold for the life of the bridge: names are forever, fields are additive, fallbacks are stable, reserved names are honored. As long as a collaborator sees “Golden Gate,” those four hold. Breaking changes earn a new bridge name and a migration map, announced before they ship.

Humans read the bridge name. Machines read the semver underneath. Both always know exactly what they’re building against.

The 29-gate slop test

A frozen system needs a bouncer. Every page we ship runs a 29-gate check against the contract… tokens only, no invented components, surfaces declared, widths from the scale, motion from the named recipes. Pass the gates or go back to the bench. AI output gets ZERO exceptions, which is precisely why we can let AI generate so much.

Why this matters for your brand

You don’t need 24 block contracts to steal the principle. Write your rules down once, in a form your AI reads every session: exact hex codes, one typeface, the phrases you never say, the layout moves you always make. Name the version. When you change it, say so.

Simple systems that help you build your brand at the speed of AI. The freeze IS the feature.