Product Readiness
Mission suite green · 83 assertionsThe product isn't “ready” because components pass — it's ready when it can run a real event end-to-end. These Missions (Wave 1) prove that; the first two (go-live happy path & blocked) are now proven by Mission 1. The remaining five are honestly pending.
Mission Suite
GREEN
Mission 1 happy path + gatesAssertions
83
mission assertionsSuccess Rate
2/7
missions passing| Mission | Status | Last Run | Note |
|---|---|---|---|
| Go-Live (happy path) | pass | never | Happy path: create event → vendors join → escalations work → marks closed |
| Go-Live blocked (must stay blocked) | pass | never | Blocked path: missing vendor, missing contact, bad JWT — all halt cleanly |
| Escalation ladder T+15/45/75 | —/pending | never | Full ladder: SMS at 15m, 45m, 75m; escalation_tick job advances state |
| Controlled override | —/pending | never | Founder can override blocked vendor; closes event early |
| Vendor onboarding | —/pending | never | New vendor joins via /creator/join; JWT issued; vendor sees dashboard |
| Multi-node readiness | —/pending | never | Event runs across multiple vendored nodes; no single points of failure |
| Cancel / abort | —/pending | never | Founder can cancel anytime; vendors see cancel signal; state is final |
Wire-3 live: the first 2 missions (go-live success + blocked) are proven by Mission 1's engine-level happy path. The remaining 5 (escalation, override, vendor, multi-node, cancel) are not yet built — honest pending. Source: truth.generated.ts.