One writer
Broker callbacks, worker outcomes, scheduled ticks and operator commands feed a single engine thread. State mutation and aggregate capital admission are serialized, preventing two entries from spending the same remaining allowance.
Research ranks candidates within a saved operating envelope. The session orchestrator admits entries under aggregate limits; each position follows independent entry, protection, automatic exit and reconciliation rules.
Core path illustrated. No-trade, partial-fill and error states are also explicit parts of the engine.
Given its recorded state and inputs, the engine applies the same execution rules. That makes the decision process inspectable. It does not make market outcomes predictable.
Broker callbacks, worker outcomes, scheduled ticks and operator commands feed a single engine thread. State mutation and aggregate capital admission are serialized, preventing two entries from spending the same remaining allowance.
The state machine defines legal transitions. Every lifecycle has its own state, identity and order references. A transition and its audit record are committed together.
Order intent is persisted before the broker submission. After a crash, the engine reconciles potential orders instead of blindly re-sending.
Actual executions and positions come from broker events and snapshots. Execution identifiers are de-duplicated; corrections update earlier records.
Research saves a constrained, ranked pool with supporting evidence. The engine revalidates a candidate before sizing and submitting its entry. A position’s monitoring, stop updates and configured exits require no further model calls.
Reconnecting is more than opening a socket. The engine gathers positions, open and completed orders, executions and account values before deciding how to proceed.
Broker IDs, permanent IDs and application order references associate broker events with local intent across restarts.
Actual position quantity is compared with recorded state. Unexpected changes can block entries and activate recovery.
ADT initiates configured exits automatically, and each exit remains pending until the broker confirms flat. Rejections and retries are recorded; unresolved exposure remains a warning.
Explore order reconciliation after a disconnect and how data quality affects automated orders.
Profit-protection activation raises a protective threshold. It does not impose a fixed take-profit ceiling. Actual fills depend on broker acceptance, liquidity and the available price.
Broker fills establish the quantity and average entry.
The configured downside stop protects confirmed exposure.
Each position records its own high-water mark.
The threshold advances protection; the position can keep running.
A higher peak can raise the stop. A pullback does not lower the recorded high or loosen the threshold.
A reversal through protection, the session deadline or an enabled observed-loss condition initiates the exit.
ADT reconciles fills, position quantity and remaining orders before marking the lifecycle complete.
Mechanics, not a performance example. The recommended preset is provisional and retains existing thresholds after synthetic scenario evaluation. Read the values, evidence and limitations.
Explore the package, review your requirements and request guided access to ADT.