Project-owner checklist

Prepare the road so students can build the vehicle.

These resources remove infrastructure, data, design, and deployment blockers without taking ownership of the sixteen student features.

6 required resourcesFixture-firstNo production patient data
Inputs

Resources and environments

01

Implementation repository

TypeScript monorepo with React applications, Node backend, PostgreSQL, migrations, shared contracts, tests, CI, environment examples, and pull-request template.

Ready when

A clean clone installs, seeds, starts all three role experiences, and passes CI.

Prepare first
02

Approved MediDispatch UI package

Reviewed tokens and components extracted from the supplied Hebrew product-design artifact. Students receive approved output, not responsibility for recreating the design system.

Ready when

Core controls have tablet, desktop, portrait, RTL, loading, empty, error, and disabled examples.

Review design
03

Scenario and fixture pack

Synthetic institutions, users, patients, tags, companies, ambulances, devices, drivers, locations, routes, prices, offers, rides, forms, and signatures.

Ready when

Every acceptance scenario names fixture IDs and no real patient or employee data is present.

Prepare first
04

Default policies and field dictionary

Default price amounts, distance mode, counteroffer timeout, transport-record fields, required/optional rules, status wording, and synthetic form content.

Ready when

Weeks 1–2 can freeze contracts without students inventing medical, pricing, or compliance facts.

Week 1
05

Frontend deployment

One public fixture-backed site with role selectors or seeded login and automatic deployment from the repository.

Ready when

Concierge, dispatcher, and driver fixture routes load and deployment results are visible.

Before integration
06

Backend and database deployment

Protected Node service, PostgreSQL, migrations, seeds, safe document storage, CORS, logs, health, and readiness.

Ready when

The public frontend reaches seeded APIs without exposing credentials or sensitive fixture data.

Before integration
Bonus work stays optional: live maps/GPS, pricing surcharges, passenger tracking, and system administration begin only after all sixteen required features are complete, tested, and documented.