Execution habits that keep the desk stable
The terminal should support these decisions, but the operator still owns them.
- Do not promote directly from a promising backtest into full-size live flow.
- Do not ignore terminal health because short-term PnL looks fine.
- Do not let one bot silently consume more attention than the desk can support.
Before enabling live flow
- Verify symbol mapping and account context.
- Confirm the capital budget matches the strategy's tested assumptions.
- Check that pause, stop, and escalation actions are understood.
While the bot is running
- Watch status and health indicators, not just PnL.
- Track whether the live trade pattern still resembles tested behavior.
- Treat repeated warnings as operational data, not noise.
Reasons to intervene
- Execution quality changes materially from expectations.
- Capital usage breaches the intended budget or cluster risk.
- The strategy behaves in a regime it was never designed to handle.