🏥 Project Health Report
Project: SplitDee
Role: Lead AI Engineer & CTO
Date: 2026-07-15
📈 1. Overall Project Health Status
- Overall Status: 🟢 Healthy (Design Phase)
- Status Details: There is currently no production codebase written (both backend and frontend are skeletons), meaning there is no code technical debt. The system architecture, API specifications, and database schemas are fully defined and documented.
- Architecture Integrity: 100%. Follows Clean Architecture in both FastAPI and Flutter. Boundary layers are cleanly separated.
❓ 2. Open Questions & Assumptions
During our audit and design review, we identified several questions that must be resolved before/during implementation:
- AI Slip Verification Service Cost & Vendor:
- Question: Which bank confirmation API/vendor will be used for validating the Mini-QR data from slips? (e.g., EasySlip, SlipOK, or direct bank partner APIs).
- Impact: Affects operational costs and infrastructure setup.
- Firebase Cloud Messaging (FCM) vs In-App Local WebSockets:
- Question: Should we use FCM exclusively for chat message notifications, or build WebSockets/SSE for real-time messaging and FCM only for background push alerts?
- Impact: WebSockets are faster for active chats, FCM is better for background.
- Mochi Pet HP/Happiness Deduction Cron Schedule:
- Question: What are the exact thresholds for Mochi’s HP deduction? (e.g., -10 HP for every 24 hours of delay per user, or group-wide status).
- Impact: Direct influence on the gamification balance and user engagement.
🛠️ 3. Technical Debt List
Although no code has been written, we identified documentation and design technical debt:
| Tech Debt ID | Category | Description | Severity | Action Plan |
|---|---|---|---|---|
| TD-DOC-001 | Documentation | Duplicate files and overlapping principles (AI_MEMORY.md, PRINCIPLES.md, TEAM_AGREEMENT.md, etc.). | Medium | Consolidation and cleanup during this session. |
| TD-DOC-002 | Naming | Legacy Obsidian links and naming formats in Dashboard.md and README.md. | Low | Update quick links and Obsidian bracket paths. |
| TD-SCH-001 | Database Design | No database indexes specified on bills.group_id and expense_shares.user_id in the initial draft schema. | Medium | Added index strategy to Database_Design.md. |
| TD-SEC-001 | Security | Missing JWT token rotation and blacklisting specifications for logged-out/compromised accounts. | High | Specify JWT blacklist/refresh token pattern in API Design. |