# Interface review playbook

Use this playbook only when the review orchestrator explicitly selects it.

## Modes

- `quick`: identify the few highest-impact issues and state what was not inspected.
- `full`: review hierarchy, composition, interaction, content, accessibility, component quality, and implementation risk.
- `focused`: inspect only the named dimension and preserve out-of-scope findings as notes.
- `publish-tickets`: convert approved findings into bounded tickets through the protected publisher.

## Finding contract

Each finding includes evidence, impact, severity, confidence, affected scope, recommendation, and a verification method. Separate observed facts from interpretation. Do not create tickets until findings are approved for publication.

## Quality gates

- Prefer a smaller evidence-backed set over a long generic checklist.
- Identify systemic causes separately from local symptoms.
- Check copy and accessibility in context, not as detached compliance lists.
- A recommendation must be specific enough to verify after the change.