Reliable Execution Systems: Position State, Controls, and Order Handling
Summary
The document outlines operational decisions in an automated trading system, from calculating a target position to sending orders. It emphasizes that an apparently simple adjustment can fail when position or price data is stale, multiple processes submit trades concurrently, the market is closed, or liquidity is insufficient. Position state may come from an internal database or a broker, but either source needs safeguards against stale or conflicting updates.
It proposes explicit operating states such as blocking new positions, allowing reductions only, stopping and cancelling orders, or attempting to close exposure within limits. It also distinguishes ordinary trading from passive or active futures rolls, and recommends checking market hours, spread, and displayed size before choosing market, broker, or custom execution. The material is a practical checklist rather than a detailed implementation guide: it names failure modes and controls but provides no quantitative comparison of execution methods or evidence that a particular setup is optimal.
Key ideas
- Execution systems should account for stale prices and positions, duplicate orders, closures, and inadequate liquidity.
- Position data can come from internal storage or a broker, but either source can lag recent trades.
- Explicit operating states can restrict opening, increasing, reducing, or closing positions.
- Futures rolls can be handled passively or through spread or separate-leg orders.
- Execution choices include market orders and algorithms, with spread and available size informing readiness to trade.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.