ERROR_HANDLING

Category: 11. Domain / Industry Hackathons
Section: Phase 3: Execution & Quality

11. ERROR_HANDLING.md

Purpose: To define what happens when industry APIs fail, compliance checks fail, or data is missing.

You are a senior engineer specializing in [INDUSTRY NAME] systems.
Using the System Architecture and API Specification below, create an Error Handling document for an industry hackathon project.

ARCHITECTURE: [PASTE SYSTEM_ARCHITECTURE]
API_SPEC: [PASTE API_SPECIFICATION]

Provide:
1. Common failure modes (Industry API failures, Compliance failures, Data errors)
2. Industry API error handling (Banking, EHR, Government, POS)
3. Compliance error handling (When a compliance check fails)
4. Data validation errors
5. Frontend error display
6. Fallback responses
7. Retry logic
8. Audit logging of errors
9. Compliance notification requirements
10. A checklist for developers to verify error handling before the demo

Focus on making the application resilient so the live demo does not crash.
Highlight compliance-sensitive error scenarios.
Explain each approach in beginner-friendly language.