Console / Execution / Risk & Recovery
Controls that hold through interruptions.
Drawdown limits are enforced at the account level, and on restart each worker reconciles its record of positions against execution reports before it resumes.
The Console's controls are built for the moments a system is under strain: a session drops, a venue cycles, a process restarts mid-position. Limits are enforced by the system, state is reconciled against the venue, and uncertainty produces a stop.
Limits act at the account level
Per-day and total drawdown limits apply at the account level, so the boundary on loss holds across every strategy regardless of how any one of them behaves. When a limit is reached, the system acts on it.
Reconciled state on restart
After an interruption, a worker reconciles its own view of the book against execution reports and resumes against what it actually holds, which is what keeps orphaned and phantom positions out of a restart. The start posture is explicit: adopt the existing positions, or start flat.
- Account-level drawdown limits that apply across strategies.
- Position reconciliation on restart, so the system manages exactly what it holds.
- An explicit start posture: adopt existing positions, or start flat.
Fail-safe by default
When state is uncertain, the system stops trading and surfaces the condition. Trading resumes once state is confirmed.
Every live parameter has a source
A live configuration carries the run that produced it: source run, config hash, and seed. Any parameter trading today can be traced back to the validation that approved it.
For institutions
Controls that assume interruptions will happen.
Enforced limits, reconciled state, and a fail-safe default are the mechanisms an operational-risk framework names when it describes how a trading system behaves under stress. Each one operates in the system itself.
Next step
Risk & Recovery, live on your strategies and venues.
Response within two business days