Skip to system research
Build A Trading SystemRules / Evidence / Replay

Trading-system risk controls: positions, orders and recovery

Define risk reservation, exposure ownership, stressed exits and recovery reconciliation without treating planned stops as guaranteed limits.

Editorial revision and linked-document check: 10 October 2026. Document-based analysis; no paid-account test or independently reproduced provider return.

The control boundary is the account state

Risk belongs to positions and to orders that can create positions, not only to rows visible in a strategy dashboard. Establish which authoritative account view owns quantities, resting orders and acknowledgements. A process stopping locally does not establish that any broker-side object was cancelled.

Define risk units and currencies explicitly. Stop-distance exposure, margin usage, notional and account equity are different measures. A system should preserve their meanings rather than compare a percentage from one measure with a dollar limit from another. Portfolio exposure also needs a rule for overlapping and potentially correlated ideas.

Read order mechanics at the actual venue

Investor.gov explains that market, limit and stop orders have different execution properties. Its explanation concerns securities orders, so it is background rather than a specification for every derivative venue. Use the broker or exchange's current rules for your actual order types and triggers.

A planned stop is not proof of a fill at its level. Document gaps, rejected orders, insufficient liquidity and any stop-limit behaviour separately. If your risk model assumes a particular executable price, label that convention and test adverse alternatives rather than naming it a hard maximum account loss.

A fictional reservation calculation

Assume an illustrative portfolio budget of 120 risk units, a current position reserving 40 and a pending order reserving 30. Under this declared additive reservation policy, only 50 units remain. A new instruction requiring 60 is rejected even though it has not yet filled.

If two independent workers each see the same 50-unit availability and accept orders without a common owner, the total can exceed the intended limit. The exercise points to atomic acceptance and reconciliation needs. It does not estimate portfolio loss, assert that risks truly add linearly or recommend those budgets for an account.

Name what a halt actually stops

Separate refusing new entries, cancelling resting instructions, closing current exposure and disabling credentials. A global halt can prevent new activity while old positions still require management. Record the acknowledgement and final account state for every action intended to remove exposure. A button label is insufficient evidence.

Give the system an operational owner and an explicit failure-reporting path. If the authoritative account view is stale, define which actions are permitted and which are refused. Do not silently continue with a guessed flat position merely because the strategy process has restarted successfully.

Recover without replaying the opportunity

Keep the last accepted event, acknowledgement identifiers and unresolved orders durably available. After interruption, reconcile them against current account state before processing later messages. A timeout can mean an order was never accepted or that it was accepted but the reply was lost; these possibilities need different actions.

An expired entry should not be made fresh by recovery. Recheck its original validity window under the frozen policy. If production is deployed, scheduling, state and failure reporting must remain available with operator computers off. A local test harness is not the production recovery owner.

Stress and test the implementation honestly

Use invented fixtures for an adverse gap, a duplicate acknowledgement, simultaneous budget requests and an unavailable account endpoint. Declare expected state transitions before running them. These scenarios reveal defects and incomplete policies without measuring their real-world frequency or calibrating a loss probability.

The acceptance record should name remaining positions, reserved orders, source freshness and the exact halt or recovery state. Passing the fixtures establishes those cases, not strategy profitability or complete operational certification. If a control depends on an unimplemented account-state source, keep that missing dependency visible before any promotion decision.

Build a Trading System evidence objects
Keep the publication's evidence objects separate when assembling your review.

Evidence handoff

Three checks to retain with this assessment
CheckRecordBoundary
ReservePositions plus accepted pending ordersNo double acceptance of one budget
HaltNamed action and acknowledgementStopping a worker is not closing exposure
RecoverCurrent account reconciliationNo blind stale-entry replay
Blank evidence CSV

Column definitions: account_alias, state_observed_at, risk_unit, portfolio_budget, position_reservation, pending_reservation, available_budget, event_id, acceptance_owner, order_ack, halt_action, remaining_quantity, recovery_state, failure_route.

No example trade or user record is stored in the download. Keep credentials and personal account identifiers out of shared copies.

A bounded fixture is not an account loss policy

The teaching run uses one whole long unit at a time and enough synthetic cash for its small invented prices. It supplies no personal allocation, leverage, nonlinear contract or guaranteed stop cap. The only exit is a predeclared time rule; native minute policy and maximum-hold ownership in an actual system remain separate. Real risk reservation must include pending orders, partial fills and authoritative holdings. The packet's negative cash and software checks cannot populate those missing account records. Preserve the original risk-control material rather than treating a successful replay as a complete operational risk audit.