# Review and Approval Process

Review is independent verification against the original assignment. Approval cannot be created by lowering criteria after the output is produced.

[Team README](README.md) · [Roles](Team%20Roles.md) · [Workflow](Team%20Workflow.md) · [Master Team Prompt](Master%20Team%20Prompt.md) · [Quality Checklist](Team%20Quality%20Checklist.md)

## Review Stages

1. **Producer self-review:** confirm scope, output format, evidence, permissions, and handoff.
2. **Specialist review:** an agent with relevant expertise inspects correctness and domain standards.
3. **Quality control:** tests requirements, edge cases, failures, security, accessibility/usability, and recovery as applicable.
4. **Revision:** producer fixes root causes and documents the change.
5. **Retest:** reviewer reruns failed and adjacent checks.
6. **Orchestrator acceptance:** confirms traceability, risks, approvals, and completion report.
7. **Human approval:** required for identified strategic, costly, sensitive, destructive, public, or production actions.

## Review Record

| Requirement | Artifact | Method | Result | Evidence | Owner |
| --- | --- | --- | --- | --- | --- |
| communicate the offer within ten seconds | [OUTPUT] | [TEST/INSPECTION] | [Pass/Fail/Blocked] | [REFERENCE] | Website Strategist |
| reach primary content in two navigation decisions | [OUTPUT] | [TEST/INSPECTION] | [Pass/Fail/Blocked] | [REFERENCE] | UI UX Designer |
| submit a contact request with verified confirmation | [OUTPUT] | [TEST/INSPECTION] | [Pass/Fail/Blocked] | [REFERENCE] | Frontend Developer |
| pass responsive, accessibility, SEO, and performance gates | [OUTPUT] | [TEST/INSPECTION] | [Pass/Fail/Blocked] | [REFERENCE] | Backend Developer |

## Approval Rules

- [ ] All critical acceptance criteria pass.
- [ ] No critical defect or unauthorized action remains.
- [ ] Reviewer is independent from the original producer where practical.
- [ ] Unrun and blocked checks are explicit.
- [ ] Human approvals are recorded for applicable checkpoints.
- [ ] Remaining lower risks have owner, mitigation, and review date.
- [ ] The completion report matches actual files, actions, and test evidence.

For this team, approval is blocked by unresolved unclear positioning, broken mobile navigation, silent form failure, oversized assets, missing semantic and search metadata when they can affect a critical outcome.