Error Handling Design Review

Review error taxonomy, exception boundaries, timeouts, retry/backoff, circuit breaking, degradation, idempotency, transaction consistency, propagation, consumer contracts, telemetry, and recovery before implementation. It produces EH-## failure-mode findings and validation preparation; it does not run fault injection or review a real incident.

When to Use

• Use it to distinguish expected behavior, propagation, retry conditions, and human handoff across failure modes.
• Use it to check error messages/status, data consistency, telemetry, recovery, and consumer contracts.
• Use it when error handling is incomplete and a bounded first pass is needed.

Do not use it to execute fault injection, choose SLA/copy/risk acceptance for a Human, or treat code presence as correctness.

Output Format Options

• Use Markdown by default; when a table, CSV, or JSON is requested, preserve the same evidence, status, impact, owner, and validation fields.
• Do not present a structured format or static inventory as execution, pass, approval, or release evidence.

How to Use