SYSTEM_ARCHITECTURE

Category: 11. Domain / Industry Hackathons
Section: Phase 2: Technical Blueprint

4. SYSTEM_ARCHITECTURE.md

Purpose: To design a realistic industry-specific system architecture with clear data flow and compliance.

Act as a senior architect specializing in [INDUSTRY NAME] solutions.
Using the following PRD and TRD, design a realistic hackathon architecture for this industry.

PRD: [PASTE PRD]
TRD: [PASTE TRD]

Provide:
1. Recommended tech stack (Frontend, Backend, Database, Integrations)
2. Complete system architecture diagram (Text-based, showing Users → Frontend → Backend → Industry APIs → Database)
3. Frontend architecture
4. Backend architecture
5. Database architecture (Industry-specific data model)
6. Integration architecture (Banking, EHR, Government, POS, etc.)
7. Authentication and compliance architecture
8. Data flow (How user actions trigger industry-specific processes)
9. Security and compliance considerations
10. Folder structure
11. Major components
12. Simplifications that can be made for a hackathon

Explain every technical decision in beginner-friendly language.
Do not introduce unnecessary tools.
Highlight compliance considerations at each layer.