Governance

It walks you through SemVer classification (major vs. minor vs. patch), enforces a quality bar before promoting components from product to core, and makes sure deprecations get a proper runway with migration maps instead of breaking everyone's builds overnight. You'll want it when deciding whether renaming a token is a breaking change, setting up contribution workflows, or figuring out how to retire that button variant three teams still depend on. The verification step is solid: changelog entries, contrast checks, and a Python validator to catch broken token references before they ship.