Component Library Governance
Define how a design-system component library is owned, extended, reviewed, versioned, and retired. Sets the ownership model and decision rights, an intake and triage path for requests, component status levels with entry and exit criteria, a definition of done covering design, accessibility, code, and documentation, a scored review rubric, versioning and deprecation rules, exception handling, and health metrics with formulas. Use when someone asks for design system governance, contribution rules, component status levels, a review checklist for new components, how to deprecate a component, or why teams keep forking or detaching components. Do not use for auditing screens for inconsistency (use design-audit), choosing colors and fonts (use color-font-pairing), testing built components for accessibility (use accessibility-qa), or app-surface patterns like tables (use steel-design).