Trading Contour
How The Trading Contour Works
The personal layer for configuration, state and explicit Start, Pause and Stop commands.
English localization is preserved as a draft. It uses the same claim IDs and status model as the Russian source, but remains noindex until editorial review.
This page describes the separate private v4.4.4 contour. It does not confirm DRYRUN or LIVE readiness for the new deterministic engine line.
The trading contour receives a prepared configuration and processes Start, Pause and Stop. A button creates a request; the final state appears only after contour confirmation.
Labs helps study scenarios, Portfolio keeps capital truth, and the trading contour performs an action in an available environment. These roles do not replace one another.
What Users See
- Selected configuration and readiness.
- Current confirmed contour state.
- Available commands and transition status after an action.
- Positions, orders and events available for the current session.
How A Command Proceeds
- Dashboard sends the user request.
- The contour accepts the request and applies the action.
- Dashboard receives confirmation and updates the state.
Important Boundary
The button expresses user intent, not a completed result. During a mismatch, Dashboard must show a transition or unknown state instead of guessing the outcome.
Source and authority
This page describes the separate legacy contour. Its rows and controls do not prove readiness of the new engine. Public trading launch is not yet open. Request, decision, result and state transition are distinct; no visible order does not prove absence of obligations or budget release.