> ## Documentation Index
> Fetch the complete documentation index at: https://anvil.servicetitan.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Governance

> Governance defines how Anvil2 is managed, how decisions are made, and how teams work together to maintain the consistency, quality, and long-term health of the system.

## Usage Guidance

Anvil2’s governance model guides how updates are reviewed, how contributions are evaluated, and how the system evolves. Use this section to understand how decisions are made, what to expect when submitting changes, and how the Anvil and Product teams collaborate.

### How governance works

Governance ensures that changes to Anvil2 support product-wide consistency, accessibility, and maintainability. This includes:

* Reviewing new component or pattern proposals
* Evaluating updates to foundations
* Assessing requests against system principles
* Aligning changes across design, engineering, and product teams
* Maintaining documentation, tokens, and code in sync
* Overseeing versioning, deprecations, and migration guidance

## Design System Scope

* Shared foundations (tokens, color, type, spacing, motion, accessibility)
* Core UI components and supported variants
* Reusable interaction patterns and workflows
* Content guidance (with Product Copy)
* Design & engineering tooling for the system
* Documentation, release notes, and support communications

If you aren't sure if a request is within Anvil's scope, reach out! If it benefits multiple teams or recurs, we’ll consider it for the system; if not, we’ll advise on next steps.

## Roles within governance

### Design System Team (Core Owners)

* Maintains foundations, components, tokens, patterns, and documentation
* Reviews and guides contributions
* Ensures accessibility standards are met within Anvil2
* Leads cross-team alignment on decisions
* Manages versioning, releases, and deprecations

### Product Designers & Engineers (Contributors)

* [Propose and contribute](https://calendly.com/anvil-servicetitan/office-hours) new components, patterns, or enhancements
* Identify system gaps for real product work
* Partner with the system team during testing and ideation
* Follow established guidance and standards
* Guide evolution through active conversation

### Cross-Functional Partners (Research, PMs)

* Provide input during reviews
* Help validate proposed changes against user needs
* Ensure solutions support customer-facing and internal workflows
* Guide evolution through surfacing user needs

## Contribution

We welcome and encourage contributions to Anvil2. The system grows stronger when teams share their needs, ideas, and improvements. Any team can propose improvements to Anvil2, and we’re here to support you through the process.
Anyone can [submit a feature request](https://slack.com/shortcuts/Ft07EXNJSPS7/f598de9eda7177f477aaddbbc5701e15), reviewed weekly, as new needs and features arise.

We also have detailed guidance for Design and Engineering contributors:

* [Code contribution](https://github.com/servicetitan/hammer/blob/main/README.md#contributing)
* [Design contribution](https://servicetitan.atlassian.net/wiki/spaces/ADS/pages/2054129026)

## Related

* [Anvil Blog: Engineering Support and Contribution](/blog/posts/2025-04-15-dev-feedback)