Project Status Dashboard
Where we are, what's next, and what's blocking us. Updated as phases are completed.
Last updated: 2026-03-06
Phase Progress
Completed
| Phase | Name | What Was Built |
|---|---|---|
| 1 | Foundation | Go scaffold, chi router, PostgreSQL + Redis, migrations, health check, middleware stack, all 3 frontend app scaffolds (Next.js 16), shared UI/API client packages, domain-based org routing with custom domains, DNS verification, Redis caching |
In Progress
| Phase | Name | Status |
|---|---|---|
| 2 | Auth & Multi-Tenancy | Code complete — validating. E2E blocked on Clerk API keys. |
E2E Validation Pending
Phase 2 (Auth & Multi-Tenancy) is code-complete but E2E testing is blocked on Clerk API keys. See Blockers.
Up Next
| Phase | Name | What to Build |
|---|---|---|
| 3 | Core Domain Models | Specialties, Specialists, Patients, Services — the data layer everything depends on |
Planned
| Phase | Name | Notes |
|---|---|---|
| 4 | Scheduling & Appointments | Depends on Phase 3. Most complex feature. |
| 5 | Forms & Custom Fields | Can parallel with Phase 4 |
| 6 | Documents & PDF Generation | Depends on Phase 5 |
| 7 | Treatment Plans & Exercise Library | Regulatory boundary starts here |
| 8 | Automations & Webhooks | Depends on Phase 4, 5 |
| 9 | Telemetry Service | Can parallel with Phases 4-8 |
| 10 | Compliance & Security Hardening | Ongoing concern |
| 11 | Dashboard & Stats | Depends on Phases 4, 5, 9 |
| 12 | Testing (dedicated) | Ongoing |
| 13 | Frontend Integration Contract | Depends on Phases 4, 5 |
Current Focus: Phase 2 Validation → Phase 3
Phase 2 — Remaining validation
| Task | Status |
|---|---|
| First login, user auto-provisioned in Core API database | Blocked (Clerk keys) |
Sign in, Clerk token, GET /v1/me returns correct user + org context | Blocked (Clerk keys) |
| Org switching from Clinic app, subsequent API calls return scoped data | Blocked (Clerk keys) |
Superadmin endpoint (POST /v1/organizations), 403 for non-superadmin roles | Blocked (Clerk keys) |
| Blocked user with valid Clerk token, 403 from Core API | Blocked (Clerk keys) |
Phase 3 — Core Domain Models (next)
The data layer for the primary entities that appointments, forms, and scheduling depend on.
| Task | Feature | Status |
|---|---|---|
specialties table + RLS + CRUD API | Specialties | Not started |
specialists table + RLS + CRUD API | Specialists | Not started |
| Weekly availability + date overrides + timezone | Specialists | Not started |
patients table + patient_org_profiles + RLS | Patients | Not started |
| Patient onboarding + guest registration | Patients | Not started |
services table + billing models + CRUD API | Services | Not started |
products table for physical products | Services | Not started |
Exit criteria: All core entities have working CRUD APIs, RLS policies, and pass integration tests.
Blockers
| Blocker | Impact | Action Needed |
|---|---|---|
| Clerk API keys not configured | E2E validation of Phase 2 cannot run | Set up Clerk project and add keys to .env |
Pending Decisions
These decisions need to be made before or during the relevant phase.
| Decision | Needed Before | Options | Status |
|---|---|---|---|
| PDF rendering engine | Phase 6 | ChromeDP, wkhtmltopdf, Gotenberg | Open |
| i18n scope | Phase 7 | See Translations | Open |
| Email/SMS provider | Phase 8 | AWS SES, SendGrid, Postmark / Twilio, AWS SNS | Open |
| Payment integration | Phase 11 | Stripe, local Romanian provider, deferred | Open |
| Mobile app approach | Phase 13 | React Native, Flutter, responsive web only | Open |
Known Documentation Gaps
Tracked from the gap analysis. These should be addressed as the relevant phases are built.
Pre-Launch (Critical)
- Testing Strategy & Guidelines
- CI/CD Pipeline & Deployment
- Frontend Integration Contract
- Data Migration Plan
- Developer Onboarding Guide
Pre-Scale (Important)
- Error Handling Standards
- API Versioning Strategy
- Caching Strategy
- Rate Limiting Details
- Email & SMS Templates
See full gap list for the complete inventory (25 items across 3 priority tiers).
Build Timeline
Phase: 1 2 3 4 5 6 7 8 9 10 11 12 13
|--1--| Done (Foundation)
|--2--| Validating (Auth & Multi-Tenancy)
|-----3-----| <-- NEXT
|--------4--------|
|-----5-----|
|--6--|
|------7------|
|-----8-----|
|------9 (parallel)-------------|
|10|
|11|
|---12 (ongoing)--------------------------------------|
|--13--|