Platform status and health
The health endpoints
Section titled “The health endpoints”curl -fsS https://entherium.duckdns.org:8443/healthzReturns {"status": "ok", "service": …, "version": …} — the version
field doubles as “which build is live”. /health is an alias.
| Signal | Meaning |
|---|---|
200 on /healthz | Platform up. Everything else on this page is about interpretation, not availability |
502 / connection refused | The platform instance is not serving — down or intentionally paused (maintenance windows exist; a paused instance is not an incident) |
200 but idle metrics | Normal between nightly runs — see below |
Idle is the default state
Section titled “Idle is the default state”Production runs on a nightly batch; between runs there is no orchestrator
process by design. The definitive interpretation table lives at
Interpreting platform status — read it
before reporting an outage based on orchestrator.present: false,
velocity: 0, or a quiet afternoon.
Deeper surfaces (authenticated)
Section titled “Deeper surfaces (authenticated)”| Surface | What it shows |
|---|---|
GET /api/v1/ops/overview | The live operational snapshot: orchestrator state, per-contract backlogs, alerts |
GET /api/v1/errors | The durable error sink (how to read it) |
The cycles domain | The actual execution funnel of the nightly runs |
Run records (pipeline_run / run_step) | Ground truth for any specific execution |
If you operate through MCP
Section titled “If you operate through MCP”A platform deploy kills live MCP sessions without restoring them — an
empty tools list right after a version bump is reconnect-time, not an
outage (details). After reconnecting,
start_here tells you if the capability surface changed while you were
away.