Phase 7 + Deployment

Operate market data, decisions, execution, and safety controls from one console.

The UI keeps configuration, execution gates, service state, and reports in one surface. Every operator-facing control includes a short note so mode changes and risk thresholds stay explicit.

Execution Gate

Primary runtime switches for `dry-run`, `paper-trade`, `live`, scanner, and executor.

Execution Entry

Preset buttons for common operating states. They all write through the same runtime-control API.

Safe Idle
Keep the stack online but stop scanning and execution. Suitable right after deployment or when validating feeds.
Dry-Run Scan
Release kill switch, start scanner, keep executor off. Use this to confirm books, balances, and scanner output before simulating fills.
Paper Trade
Scanner and executor both on. Decision worker will emit `approved_paper_trade`, and execution will simulate partial fills, cancels, and repair paths.
Live Arm
Requests live mode with scanner and executor enabled. Backend still rejects it unless `.env` sets `RISK__ALLOW_LIVE_MODE=true` and exchange credentials are present.

Opportunity Thresholds

Safe runtime config patches for symbol list and economic filters.

Exchange Wiring

Read-only connectivity and fee profile pulled from backend settings.

loading...

Risk And Execution Profiles

Static guardrails and simulator/live execution settings currently loaded from `.env`.

loading...

System Snapshot

Current backend state returned by the FastAPI control-plane endpoints.

loading...

Phase 1 Feed Health

Published by the market data and balance workers through Redis.

loading...

Latest Books

Top-of-book snapshots visible to the rest of the system.

loading...

Latest Opportunities

Phase 2 scanner output after fee, slippage, balance and notional filtering.

loading...

Risk Decisions

Phase 3 decision output with explicit approval state and rejection reasons.

loading...

Dry-Run Hedge Groups

Phase 4 execution coordinator output for approved dry-run decisions.

loading...

Order Intents

Pre-submission execution intents derived from approved decisions and hedge-group planning.

loading...

Unified Orders

Unified order lifecycle records across dry-run, paper-trade, and live execution.

loading...

Trade Fills

Execution fills from dry-run and paper-trade simulated order processing.

loading...

Daily Summary

Phase 7 aggregated report from persisted database records.

loading...

Reconciliation

Balance and unresolved hedge-group reconciliation status.

loading...

Operational Notes

What the current control plane includes, and how to operate it safely.

Binance and OKX now load markets, normalize symbols, stream order books with CCXT Pro when available, and fall back to REST polling otherwise.
Balance workers publish non-zero balances into Redis for the API control plane to consume without sharing process memory.
Scanner worker publishes only opportunities that clear net edge, expected profit, and notional bounds. Decision worker then applies kill switch, runtime mode, health dependency, cooldown and reserve checks.
Execution worker consumes `approved_dry_run`, `approved_paper_trade` and `approved_live` decisions, re-checks shared runtime control, and advances hedge groups plus orders through the unified state machine.
Reconcile worker persists execution state into PostgreSQL, computes reconciliation against current Redis balances, and exposes summarized reporting through the API.
Recommended operator sequence: `Safe Idle` -> `Dry-Run Scan` -> confirm market data, balances, and opportunities -> `Paper Trade` -> verify fills and reconciliation -> only then consider enabling backend live mode plus credentials.