Control Plane Overview

The operator console home is a set of seven overview cards backed by real engine calls. Track A replaces thin placeholder text with live data and a strict runtime-truth contract so you can tell at a glance whether quoting and execution are actually available in this environment.

Overview cards

• Service status — engine health, latency, environment badge.
• Limits — vault exposure, daily volume, circuit-breaker percent.
• Pricing health — feed age vs staleness threshold.
• Market hours — market-closure override and Ondo issuance hours.
• Recent failures — last N failed quotes.
• Circuit breaker — current state + most recent trip.
• Docs links — cross-links to these guides.

Runtime visibility contract

The home page renders from /api/v1/runtime/capabilities and /api/v1/limits calls issued from the console's server side; Bearer tokens never hit the browser. When any of those calls fails, the page renders a diagnostic banner in place of the affected card rather than falling back to stale or misleading data.

Dead-page / unreachable banner UX contract

If the engine is unreachable, the console renders a banner that contains:

• The literal phrase Engine unreachable.
• The resolved environment label (Preview / Staging / Production).
• A concrete Next step pointer — typically "check the engine Railway service" or a runbook link.

See Failure Modes for the full diagnostic banner format and runbook references.