Stage 4: FORGE — FirstDate Architecture

One app. Two experiences. One host, many applicants, episodic content, real money tracking. **Core principle:** The deal IS the episode. A restaurant sponsorship deal produces one episode. An episode fulfills one deal. They share a lifecycle. ### Host Tabs (Mohamed) 1. **Inbox** — Application review (approve/pass/shortlist) 2. **Pipeline** — Deal CRM (Lead → Pitched → Confirmed → Filmed → Published → Invoiced) 3. **Schedule** — 10-week calendar grid (deal + talent + budget per week) 4. **Ledger** — P&L with expense/revenue categorization 5. **Studio** — Consent manager + pre-shoot checklist + episode content links ### Public Tabs (Women / Audience) 1. **Series** — Published episodes (poster cards, content links, restaurant featured) 2. **Apply** — Application form (photo, bio, Instagram, why-me, consent acknowledgment) 3. **Spots** — Restaurant catalog with "Featured in Episode X" badges 4. **Status** — Application status tracker (pending → reviewing → selected/not selected) 5. **Chat** — DMs with Mohamed (unlocked after selection) | Service | Responsibility | |---------|---------------| | **ApplicationManager** | Fetch/filter/approve/reject/shortlist applications | | **EpisodeManager** | Full episode lifecycle: plan → cast → schedule → film → edit → publish. Also handles deal pipeline stages. | | **ConsentManager** | Generate consent form, capture signature (PencilKit canvas), upload to Storage, create record | | **LedgerManager** | Income/expense CRUD, per-episode P&L, series P&L, category breakdown | | **WardrobeManager** | Wardrobe item CRUD, outfit assembly per episode | | **ScheduleManager** | 10-week plan computation from episodes, budget allocation per week | | **ChecklistManager** | Pre-shoot validation: consent signed? Reservation confirmed? Phone charged? Outfit logged? |