Engineering is organized as one sequential track: 14 development phases. Read the three intro documents once, then live in the phases, each is a self-contained work order with an objective, goals, what to build, an Achievements list (the definition of done), and a demo. Finish Phase 14 and the MVP is pilot-ready.
| Document | Why |
|---|---|
| Clinical Primer for Engineers | The medicine translated into engineering, plus what you decide alone vs. what always needs clinical sign-off. |
| MVP Build Strategy | What we build fully, build lean, script, buy, or defer, and the deferral register that keeps scope honest. |
| System Overview | The 10-minute picture: the five hard rules, how an episode flows day 0–30, the stack in one paragraph. |
Sequential and gated by definition of done, not calendar, a phase ends when its DoD is green. Every phase page carries a live status badge (Pending → In Progress → Complete); the dots below and the home-page progress board follow automatically, and every flip is recorded in the members change log with name and date.
| Phase | Focus |
|---|---|
| Phase 01 | Environment & Skeleton |
| Phase 02 | Audit Ledger & Config |
| Phase 03 | Identity & Activation |
| Phase 04 | Episode Engine |
| Phase 05 | Patient Today (PWA) |
| Phase 06 | Notifications & Suppression |
| Phase 07 | Ingestion & FakeEHR |
| Phase 08 | Extraction Pipeline |
| Phase 09 | Seven Gates & Review Queue |
| Phase 10 | Medication Truth |
| Phase 11 | Scheduling & Caregivers |
| Phase 12 | Escalation, Agents & Kill Switches |
| Phase 13 | Clinician Brief & Post-Visit |
| Phase 14 | Analytics, Hardening & Pilot Readiness |
Open the phase → flip its badge to In Progress → build to the Achievements list → run the Demo with Amir (the clinical founder) → flip Complete and open the next. Each phase ends with a Deep reference line linking the module contracts, reference chapters, and ADRs that govern that slice of the system, they are the encyclopedia behind the track; the phases are the only to-do list. For AI-assisted coding, paste the phase page plus its deep-reference links into your agent's context, with the System Overview's five hard rules pinned.
| Action | Who | How |
|---|---|---|
| See progress | Anyone with hub access | Badges on every phase page; roll-up on the home page. |
| Change a status | Approved members | Click a badge → pick the new status; recorded with your name and date. |
| Review history | Approved members | Members → Change log. |
| Join / approve members | Anyone / Admin | Members → Request membership; admins see a pending-approvals panel. |
Three things come from Amir directly on day one: repository access, the shared founders channel, and environment secrets. If any of the three is missing, that is the first blocker to raise, before writing code. Progress badges on these pages persist for every signed-in member (the backend is live); anything clinical routes to Amir per the primer's decision boundaries.