⚠ INTERNAL — Operator UX mock · Design preview of V2 development path · demo-wired ≠ production-live · back to dev guide
Operations/Ops Dashboard
Polygon · pUSD 10
📓 Developer Guide 📋 Reason Codes 📈 Shadow Mode
JD John Doe · Admin
OperatorOperator-first landing — pipeline health, rollout ladder for all 109 bots, incident board, and 8 plumbing tiles. Answers “is t…When: At session open, when an incident fires, or before promoting bots between rollout rungs.
Details
What this page is forOperator-first landing — pipeline health, rollout ladder for all 109 bots, incident board, and 8 plumbing tiles. Answers “is the platform healthy and where is every bot in the ladder?”
When to use itAt session open, when an incident fires, or before promoting bots between rollout rungs.

Ops Dashboard — pipeline, rollout ladder, and incident board

Operating-loop health, where each bot sits on the rollout ladder, and live incidents. Switch to Trader Home for PnL, edge, and blotter.

Operating Loop Discover → Ingest → State → Signals → Fair value → Execution → Risk → Place → Reconcile · all stages live demo-wired
1

Discover

28 markets · 3 new today

2

Ingest

9 feeds · 0 gaps/min

3

State

28 books · 0 stale

4

Signals

142 features/s

5

Fair value

2 suppressed (low conf)

6

Execution

q_exec err 3.1 bps

7

Risk

1 cluster 96% of cap

8

Place

1,284 env · 4.2% reject

9

Reconcile

0 unmatched

Rollout Ladder 109 bots · promotion gated by section coverage + replay parity

Replay

81

historical only

Shadow

19

live read, no orders

Paper

0

simulated fills

Canary

9

demo-wired

Broader live

0

production-live

Bots advance one rung at a time. Every promotion requires 27/27 sections + green replay parity. 0 are in production-live — demo-wired ≠ production-live.

Incident Board 3 open
  • Feed gap on Polymarket WS · BBO_UPDATED dropped 2s

    14:38 · RISK_FEED_GAP · reconnect in 4s

    auto-paused
  • Book stale on ai-frontier-model-2026 · 22s without update

    14:32 · RISK_BOOK_STALE_15S · threshold 15s

    resync queued
  • Calibration drift on fair-value-v1.4 · Brier +0.08 vs baseline

    14:18 · GOV_CALIBRATION_DRIFT · auto-rollback armed

    rollback pending
  • New market discovered · uk-snap-election-2026

    14:05 · DISC_NEW_MARKET · awaiting onboarding

    operator review

Stale books

0 / 28

threshold 15s

Fill ratio (1h)

94.2%

target ≥ 92%

Slippage err

3.1 bps

predicted vs actual

Heartbeats

9 / 9

all wired bots live

Envelopes

1,284

today · peak 18.4/min

Reject rate

4.2%

down from 5.1%

RPC latency

182 ms

p95 last 5m

Hash parity

100%

live vs replay

Why this view exists

Ops Dashboard answers “is the machine healthy?”. The operating-loop strip up top maps to the 9-stage pipeline from the explainer (PDF pp 1–2). The rollout ladder (PDF pg 14) shows how many bots are at each rung — promotion requires 27/27 sections + green replay parity. The incident board surfaces auto-paused feeds, stale books, and calibration drift with their reason codes. Monitoring tiles cover the plumbing: stale books, fill ratio, slippage error, heartbeats, envelope throughput, reject rate. All numbers synthetic — not a forecast.
Polytraders Operator UX Mock · INTERNAL · demo-wired ≠ production-live · the plan · reason codes · shadow-mode pipeline
⚙ Page Configuration
Current page settings
Loading configuration…