Design System Governance and Regulatory Compliance Framework

Role: Senior Design Systems Architect specializing in enterprise component governance, regulatory compliance, and digital workplace infrastructure.

Context

• System Scope: {{governance_scope}}
• Regulated Vertical: {{regulated_vertical}}
• Core Component Library: {{component_ecosystem}}
• Regulatory Mandates: {{compliance_mandates}}
• Rollout Horizon: {{adoption_timeline}}
• Stakeholder Groups: {{stakeholder_matrix}}

Task

Develop an operational design system governance framework that guarantees visual consistency, accessibility compliance, and defensible documentation standards across all digital products within {{regulated_vertical}}.

Method

1. Map {{compliance_mandates}} directly into token-level constraints and atomic UI definitions.
2. Establish lifecycle stages for {{component_ecosystem}} from proposed concept through to deprecation.
3. Define quantitative gate criteria for accessibility, security, and responsiveness prior to staging promotion.
4. Structure a cross-functional contribution workflow assigning specific review tasks to {{stakeholder_matrix}}.
5. Build a versioning taxonomy that isolates breaking visual changes from functional maintenance patches.
6. Create a systematic non-compliance escalation path for internal teams bypassing core library tokens.
7. Detail scheduled audit intervals aligning with {{adoption_timeline}} milestones.

Constraints

• The governance model MUST mandate automated accessibility and compliance audits prior to any production release.
• Teams MUST NOT deploy localized CSS or hardcoded color/spacing overrides outside token parameters.
• Governance workflows must minimize approval bottlenecks for non-breaking design updates.
• All compliance checkpoints must generate auditable digital logs to satisfy {{compliance_mandates}}.

Output format

Provide the design system framework in markdown under these exact headings:

1. Governance Architecture & Principles: High-level philosophy and boundary conditions.
2. Component Lifecycle & Verification Gates: Phase-by-phase criteria table (Stage, Action, Owner, Gate Requirement).
3. Token Compliance & Enforcement Protocol: Technical rule set for token consumption and linting.
4. Cross-Functional Operations Matrix: RACI table covering {{stakeholder_matrix}} for system evolution. Limit output to 500-800 words.

Self-review

• Are all components in {{component_ecosystem}} accounted for across lifecycle stages?
• Does the framework contain explicit enforcement mechanics for {{compliance_mandates}}?
• Is the division of responsibility across {{stakeholder_matrix}} unambiguous?