Risk controls
Circuit breakers, caps, and kill switches live here for a reason.
Operator ownership
Risk controls are operator-owned. The framework exposes hooks; you wire budgets and stops to venue reality:
Latency and partial fills can breach static notional caps.
Oracle drift and corrections can move fair value faster than your UI suggests.
Revisit limits after material venue or kit upgrades.
Practical wiring
Define hard stops (daily loss, max position, max orders per window) before first live session.
Test kill switch paths in dry-run or a sandbox venue if available.
Log when limits trip; correlate with Replay and audit trails.
Related
Shell pages under Shells in the navigation for product-specific guardrails
Last updated