- Shipped
- 26 Agosti 2026, 18:18 UTC
- Author
- Kamo
- Commit
- dca3e34
The vertical is built end to end — charts, scheduling, notes, orders, results, claims, FHIR and bulk export, C-CDA, TEFCA exchange, quality measures and the patient portal. PLANNING was a lie, and the person it was told to is the operator deciding whether to offer the app: "the work has not started" is the one reading that guarantees they never turn it on. It stops short of COMPLETED deliberately, and that is unchanged. COMPLETED is not a statement about how built something is — AppCatalogService derives availability from it, PLATFORM_APP_CATALOG is empty in production, and the auto-provision loop would write an ACTIVE row for every org on the next Settings load, which entitlement fail-open would not stop. For a retail app that is an unwanted menu item; for this one it is PHI capability in tenants that never signed a BAA. The existing guard asserts != COMPLETED and still passes, which is the point: its invariant was never "the EHR is unfinished", it was "nobody gets a clinical app by accident". A second test pins the stage off PLANNING so the two readings cannot drift back together.