System status.
Which components are monitored, how an incident is published, and what an error screen hands you. Live readings and the incident history are read inside the application itself.
Availability objective
A chart-load objective is published and measured in production per component. Components below the objective surface in the clinic’s daily check.
Incident history
Every incident is written to an immutable incident log with start, end, affected components, root cause and remediation, and published on the application’s own status surface.
Support reference
Every error screen in the application carries a unique reference, the time of failure and the assurance that the incident has been recorded.
Read-only fallback
When a dependency fails, the last-synced chart stays accessible in a labelled read-only mode. An automated test proves that path every month.