Live Trading / Terminal

Order acceptance, latency, session context, and account state all affect live behavior even when the strategy logic is unchanged.

A bot that technically runs but cannot be supervised clearly is operationally weak. The terminal should compress health, capital, and status into one view.

You should already know what spread, slippage, drawdown, or engine behavior would justify a pause or shutdown.

Use the same workflow and monitoring habits before live capital is on the line. This validates the operator process as much as the strategy.

Confirm session behavior, symbol availability, bot state, and capital controls in the exact environment the strategy will run in.

Do not change strategy logic, capital sizing, and broker environment all at once. You want attribution when something breaks.

Write down what performance drift, technical failure, or market condition will force a pause. Then respect it when the moment arrives.

• 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.

• 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.

• 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.