# Design system working brief

## Product context

- Audience:
- Product promise:
- Surfaces in scope:
- Constraints:

## Qualities to protect

Name the characteristics that must survive every component, mode, breakpoint, and implementation handoff.

1. Distinction:
2. Behavior:
3. Accessibility:

## Sources of truth

- Foundations: `tokens.json`
- Components: production code
- Behavior and states: Storybook
- Rationale and governance: this document

## Governance

Every change records an owner, rationale, affected tokens or components, migration notes, and validation evidence. AI may propose and compare; a person approves what enters the system.

## Definition of done

- Token aliases resolve in every supported mode.
- Component states are documented and keyboard-testable.
- Responsive behavior is verified at representative viewports.
- Figma, Storybook, and production code describe the same contract.