# Error Handling Patterns

## Agent-Level Error Handling

Agents follow the retry circuit breaker pattern defined in `agents/lead.md`:

- After 3 coder rejections on the same task: revisit design, simplify, or consult SME
- After 5 total failures: escalate to user (Tier-3 escalation)

## Memory Write Errors

Agents with memory-only edit access should:
1. Write to `.memory/*` files for their recording duties
2. If write fails, report to lead for escalation
3. Never attempt to modify non-memory files as a workaround

## Quality Gate Failures

- Reviewer `CHANGES-REQUESTED` is a hard block — do not advance to tester
- Reviewer `REJECTED` requires redesign — do not retry same approach
- Tester `PARTIAL` is not a pass — either fix blocker or escalate to user