# Error Handling

Errors must be visible, reproducible, owned, and recoverable. Agents must distinguish a product defect, test defect, environment failure, ambiguous requirement, denied permission, and external dependency failure.

[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)

## Defect Report

~~~markdown
# Defect Report

## Defect ID
[ID]
## Severity
[Critical / High / Medium / Low / Informational]
## Summary
[ONE SENTENCE]
## Expected Behavior
[ORIGINAL CRITERION]
## Actual Behavior
[OBSERVED RESULT]
## Reproduction Steps
[ENVIRONMENT / INPUT / STEPS]
## Suspected Cause
[HYPOTHESIS, NOT FACT]
## Files Affected
[PATHS OR ARTIFACTS]
## Recommended Fix
[RESPONSIBLE LAYER/OUTCOME]
## Assigned Agent
[OWNER]
## Retest Requirements
[ORIGINAL + ADJACENT CHECKS]
## Status
[OPEN / FIXING / RETEST / CLOSED / ACCEPTED RISK]
~~~

## Severity Rules

- **Critical:** protected data, unauthorized action, destructive loss, core system unusable, or invalidates the final result. Blocks approval.
- **High:** major P0 behavior fails or has no safe recovery. Blocks ordinary release.
- **Medium:** important behavior fails with a practical workaround.
- **Low:** limited impact without core outcome failure.
- **Informational:** observation or improvement, not a defect.

## Recovery Rules

Reproduce before fixing when safe; preserve evidence; avoid repeating unknown side effects; retry only transient failures with a bound; protect completed work; fix the earliest responsible cause; retest. Specifically investigate unclear positioning, broken mobile navigation, silent form failure, oversized assets, missing semantic and search metadata when relevant.