Daily Operating Cockpit

What it shows

The cockpit composes read-only summaries from the other modules into one operator view. Nothing here is a separate source of truth — it is a lens over the operating record.

• Readiness gate — a single ready / not-ready / blocked state derived from data readiness, signal governance, and pre-trade risk checks.
• Pending approvals — the human gate inbox where every propose/mutate output waits for sign-off before it can affect the live path.
• Staged deployment controls — switch a strategy between Stage 1 (human approval required), Stage 2 (conditional auto-routing when all gates pass), and Stage 3 (governed auto-flow with exception routing). Every stage change is logged.
• End-of-day report — PnL, exposures, exceptions, and the day's governance events in one regenerable summary.

Readiness gate

Before any orders are generated, the gate aggregates upstream checks into one verdict. A blocked gate names the specific failing check (stale data, an unapproved signal version, a breached pre-trade limit) and links to the module that owns it.

The gate is honest about missing inputs: an empty checklist shows 'No data yet' rather than a misleading 100% pass.

Staged deployment

Autonomy is expressed as deployment stages, not a single on/off switch. Stage 1 requires explicit human approval for every order set. Stage 2 auto-routes only when all deterministic gates pass and otherwise falls back to the approval inbox. Stage 3 runs the governed auto-flow with exceptions routed to owners. Stage transitions are admin-gated and append a governance event.