# Requirements Sync

## Purpose

Propagate major shared behavior, access, navigation, interaction, and delivery decisions into
canonical requirements.

## Run when

Run whenever a prompt introduces common behavior or a reusable functional contract.

## Procedure

1. Separate behavioral requirements from visual identity decisions.
2. Update the canonical requirements with implementation-aligned language.
3. Add the corresponding requirements changelog entry.
4. Cross-check affected routes and components for contradictions.
5. Link to the Brandbook or Developer Hub reference instead of copying their full content.

## Required outputs

- Requirements update
- Requirements changelog entry
- Cross-reference corrections
