What has current evidence, and what does not.
Each capability is operational only on current evidence; old evidence reads as stale and silence as unknown. No uptime, SLA, or unobserved-health claims.
What was checked, what is old, and what nothing watches.
StateCapability and evidenceCheck and boundary
OperationalPublic applicationChecked Oct 18, 2026, 3:57 AM UTC.This deployment served the status request.One successful request is not an availability percentage or a latency target.
Not monitoredPrimary datastoreNo evidence.A bounded read-only query, and whether the schema this build expects has been applied.Checked only where the deployment enables it. Reachability is not a durability or backup guarantee.
UnknownAuthentication boundaryChecked Oct 18, 2026, 3:57 AM UTC.The session-signing secret signs and verifies, refuses a forged signature, and the datastore that sessions live in is operational.No real sign-in is attempted. Identity-provider sign-in is not checked.
OperationalDeterministic readiness engineChecked Oct 18, 2026, 3:57 AM UTC.The deployed readiness engine returns the expected READY, NOT READY and CANNOT ESTABLISH verdicts on three synthetic cases.Synthetic records only. This is not a governed answer on anyone’s records.
Not monitoredBackground processingNo evidence.Whether a worker has reported recently, and whether queued work is being processed rather than waiting.A worker that reports is alive; only processed work shows it is useful. A worker that never reported reads as unknown, not as healthy.
Not monitoredIncident recordNo evidence.Whether the incident record could be read for this page.An unreadable record is unknown, never "no incidents".
Not monitoredGoverned-answer retrievalNo evidence.Nothing. The answer path writes records, so no synthetic probe exercises it.Repository tests do not establish live availability.
Not monitoredObject storageNo evidence.Nothing. No read or write canary exists.Storage health is not inferred from application availability.
Deployment metadataRunning build4422fbe30ac3Built Oct 17, 2026, 5:56 AM UTC, by the build's own clock.Build time, not deploy time: promoting or redeploying an existing build keeps the time it was compiled. Knowing the commit says nothing about whether the deployment is configured correctly.
Not connectedIncidentsNo history claimed.No incident record is connected in this deployment, so no incident history is claimed.Only incidents an operator recorded appear here. An outage nobody recorded is not visible on this page.
Checks run when this page or /api/status is read, at most once a minute per instance, and the worker reports itself. Nothing observes the site between reads, so this is not an independent uptime monitor, an availability history or a service-level commitment. Alert ownership and a published response policy are not connected to it.