Public web surface
This deployment served the status request successfully.
Responding
- Verification
- Verified by the current server response.
- Boundary
- A successful request is not an uptime percentage or latency SLO.
Status, without theater.
This page reports what this deployment can verify now, names what remains private, and refuses to turn missing telemetry into a green uptime claim.
Verified signals, separated from assumptions.
Each row states the check, its limit, and the reason a private component is not presented as healthy without evidence.
Primary datastore
The public status route does not query the datastore in this deployment.
Not publicly probed
- Verification
- No request-time database probe is enabled.
- Boundary
- Availability must be verified through private deployment telemetry.
Governed-answer retrieval
The authenticated retrieval path is not exercised by this public request.
Private / unmonitored
- Verification
- No public synthetic transaction is configured.
- Boundary
- Repository tests do not establish live production availability.
Ingestion worker
Background ingestion is not exposed as a public availability check.
Private / unmonitored
- Verification
- No independent worker heartbeat is published.
- Boundary
- Queue depth, retry health, and processing latency remain private signals.
Object storage
Storage health depends on the active deployment configuration.
Deployment-dependent
- Verification
- No public read/write canary is configured.
- Boundary
- This page does not infer storage health from application availability.
This is not an external uptime monitor.
This is a request-time transparency surface, not an independent uptime monitor, SLA report, or historical availability record.
A genuine uptime record requires a monitor outside the deployment, durable incident events, alert ownership, and a published response policy. Those controls are not implied by this page.
No invented clean history.
History not published
No durable public incident ledger is connected yet, so this page does not claim a clean incident history.
Required before this becomes an uptime service
- 01Independent probes
Check the public application and critical workflows from outside the hosting boundary.
- 02Durable incident ledger
Publish opened, identified, monitored, and resolved transitions from a real source of record.
- 03Owned response policy
Define alert thresholds, accountable responders, update cadence, and only then publish service objectives.