/api/live/system-heartbeat
Central aggregate pulse for the unified dashboard.Healthy is not enough. Fast matters.
A read-only latency watch layer that defines when healthy provider routes are excellent, healthy, watch, warning, or critical before automatic alerting or persistence is attached.
Every TheoB pathway can move through Past, Present, and Future without losing context.
Read current signals, conditions, and live context.
Voice ready
A route can be alive and still be dragging the cockpit.
Provider Health Latency Watch Layer gives TheoB a clean way to classify route speed before persistent trend history or automatic alerting is attached. This keeps the cockpit fast, honest, and ready for scale.
Latency watch is ready as a read-only classification layer. Persistent latency history and automatic alerting are intentionally not attached yet.
/api/live/system-telemetry
Internal provider snapshot for live routes, safe mode, provider version, and secret exposure guard./api/live/dashboard-status
Panel status and route map for the unified dashboard./api/live/telemetry-status
Operational telemetry summaries for build, runtime, tokens, connectors, workflow cost, and alerts./api/live/signal-mesh-status
Signal source, routing, priority, correlation, and verification status./api/live/ingestion-status
Connector readiness, validation, schema health, freshness, and mesh handoff status./api/live/autonomy-status
Auto-allowed, review-required, blocked, escalated, and override-ready action status./api/live/command-center-status
Founder cockpit panels, decisions, alerts, workflows, approvals, and override state./api/live/safe-mode-status
Normal, degraded, paused, recovery, safe mode, and override visibility.A route can return HTTP 200 and still need attention if latency repeatedly crosses watch thresholds.
Do not wait for failure before noticing drag.Command Center, Safe Mode, Autonomy, and Heartbeat routes should be watched more aggressively.
Founder control surfaces must stay crisp.Latency watch stores route labels, timings, and classifications only.
Never store tokens, cookies, payloads, credentials, or private logs.Historical latency storage should be added later only after audit persistence and redaction are ready.
No database logging until governance says yes.Automatic alerting should be connected after latency patterns are validated.
Do not create noisy alerts before thresholds are proven.Latency watch may recommend optimization but cannot mutate routes or deploy changes.
Observation is not execution.