Skip to main content

Orders / positions

Orders and positions are execution-layer objects. A strategy proposes an orderPlan; the runtime and connector decide what can actually happen.

Order Plan​

An entry decision should provide:

  • direction
  • qty
  • stopLossPrice
  • one or more take-profit prices

The shared runtime resolves execution fields such as timestamp, current price, and signal metadata from runtime context.

Position Lifecycle​

A position can close through:

  • take-profit
  • stop-loss
  • strategy exit
  • runtime hook
  • connector or exchange-side status

Backtest fills are approximations. Live fills depend on exchange liquidity, latency, order type, and connector behavior.

Automation Safety​

Before enabling order placement:

  • verify config and position sizing
  • account for fees and slippage
  • use small scope first
  • monitor connector errors
  • keep a rollback path

See Pre-Live Strategy Checklist.