Trading Contour
Start, Pause And Stop
What each command means and why a button click is not a completed action.
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.
Start, Pause and Stop send a request to the trading contour. Until the contour accepts and confirms the action, Dashboard shows a transition state.
Pause and Stop cancel active orders in the verified legacy implementation. What happens to an existing position on Stop must not be promised without separate Trading approval.
Commands
| Command | User Meaning |
|---|---|
| Start | Request launch of a confirmed configuration. |
| Pause | Pause new actions and cancel active orders in the current implementation. |
| Stop | Stop the contour and cancel active orders; existing-position behavior needs separate confirmation. |
Why A Request May Fail
- Configuration is not ready or has changed.
- A previous action is still being processed.
- Fresh contour confirmation is unavailable.
- The service returned an error that must be shown to the user.
Risk Confirmation
A new or changed configuration requires a separate risk confirmation. Restarting the same accepted configuration after Pause or Stop should not ask again.
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.