Scope → feasibility → design → build → test → demo → handover → next. Customers get a project code; the lab gets a shared state.
Opaque prototypes create anxiety. We publish the phase model on purpose: you always know whether we are still shaping the problem or already cutting metal and flashing boards.
Each phase has an exit condition. Scope ends with objectives and out-of-scope. Feasibility ends with go / no-go. Build ends when the unit runs the brief on the bench. Demo is evidence, not theatre.
The track page on this site is the customer-facing slice of that line. Same code the lab uses. Same timestamps. No status theatre in email threads.