A brand book you can’t drift off
Most design systems decay the moment teams stop looking. This one is machine-enforced: the rules ship as gates, so an app built by a different team — or a different Claude Code instance — still can’t go off-system.
A ratchet, not a snapshot
audit:system is a ratchet, not a snapshot. Every consuming app starts at zero bespoke debt; any new violation — a raw hex, an off-scale spacing util, a hand-rolled panel — fails CI. The number can only go down. This is the difference between guidelines and enforcement.
Production-ready. Semver-protected; breaking changes are a major bump with a migration note.
Usable, API may change. Section blocks and new primitives start here.
Scheduled for removal. Replacement named; a date is set.
Semver
Token or component breaking changes are a major bump with a migration note. The lockfile pins consumers to a commit; updates are deliberate.
Change flow
Propose → build to the rules → self-audit (the same gates) → the registry rebuilds → consumers pull. New patterns get a decision-log entry.
Brand book taken to enterprise grade: full foundations, voice, and Wave 1 (tokens-as-contract, adopt guide, accessibility with a live contrast matrix, this governance surface). Ultra-platinum audit published.
Brand-book site live at design.webzenia.com. A Next app that dogfoods the system and serves the registry from /r/.
@webzenia/design-governance: portable .claude corpus + audit scripts + rule-gate hook + CI, so any app inherits the same gates.
@webzenia/tokens (token + base-CSS layer) and @webzenia/ui shadcn registry (19 items). Install-verified end to end.