Operations command

Platform control surface

Enterprise workspace for runtime health, customer provisioning, and estimator reliability.

Checking API
No session Platform owner

System posture

Health Center

Landing surface for runtime health, incident collection, provisioning availability, and later estimator pipeline alerts.

Platform owner only Render + API visibility

API heartbeat

Checking Waiting for /api/health

Session

Checking Verifying platform-owner access

Runtime config

Pending Waiting for provisioning bootstrap

Log intake

Pending Connect Render logs or Sentry before trusting this as a true incident center

Alert inbox

What belongs here now

Render warning and error ingestion is not wired yet.

Health Center should eventually ingest Render logs, queue failures, webhook retries, native slicer timeouts, and auth anomalies.

API heartbeat is the first live signal.

Until structured incidents exist, treat this page as a runtime posture view rather than a complete incident feed.

Keep this surface operational, not analytical.

Estimator accuracy charts belong in Estimator Lab. Health Center should stay focused on system state and failure visibility.

Service map

Current live checks

Render API Waiting for /api/health
Checking
Operator session Checking platform-owner session
Checking
Provisioning runtime Waiting for runtime-config bootstrap
Pending
Provisioning route /provisioning
Ready

Module scope

Keep the nav lean for now

  • Health Center for runtime status, incidents, and operational posture
  • Provisioning for customer workspaces and owner account recovery
  • Estimator Lab for shadow-slice quality and release validation

Next after this

Jobs & Activity

Once background slicing and alert pipelines exist, add one more internal surface for queue depth, retries, release actions, and operator audit trails.