DOMAIN_MODEL

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

5. DOMAIN_MODEL.md

Purpose: To define industry entities, relationships, and domain-specific data structures.

Act as a senior domain modeling expert for [INDUSTRY NAME].
Using the PRD and System Architecture below, design the domain model for this industry hackathon project.

PRD: [PASTE PRD]
ARCHITECTURE: [PASTE SYSTEM_ARCHITECTURE]

Provide:
1. Core industry entities (E.g., FinTech: Account, Transaction, Loan; HealthTech: Patient, Appointment, Prescription)
2. Entity attributes (Fields, Data types)
3. Primary keys
4. Foreign keys
5. Relationships (One-to-Many, Many-to-Many)
6. Industry-specific enums (Status codes, Categories)
7. Compliance-sensitive fields (PII, PHI, Financial data — mark them)
8. Example records
9. SQL/NoSQL schema
10. Data retention rules
11. Audit trail requirements

Explain why each entity exists.
Keep the domain model simple enough for a beginner hackathon team to understand and maintain.
Mark which fields require encryption or special handling.