ERROR_HANDLING

Category: 13. Social Impact / Civic
Section: Phase 3: Execution & Quality

11. ERROR_HANDLING.md

Purpose: To define what happens when government APIs fail, data is missing, or users have low connectivity.

You are a senior engineer specializing in civic tech.
Using the System Architecture and API Specification below, create an Error Handling document for a social impact hackathon project.

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

Provide:
1. Common failure modes (Government API failures, Data missing, Low connectivity)
2. Government/NGO API error handling
3. Data validation errors
4. Offline error handling (Queue, Retry, Sync)
5. Low-bandwidth error handling (Reduce payload, Fallback to SMS/USSD)
6. Frontend error display (Simple, multilingual, actionable)
7. Fallback responses
8. Retry logic
9. Recovery procedures
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.
Ensure errors are understandable to non-technical users.
Explain each approach in beginner-friendly language.