Trading Contour
How To Read Contour State
Why Dashboard separates a request, a transition and a confirmed result.
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.
State does not change merely because a button was clicked. Dashboard matches the user request with the latest contour confirmation and shows whether the transition completed.
When fresh confirmation is missing, the correct answer is no current data or a transition state. Dashboard must not present an old mark as current.
User States
| State | Meaning |
|---|---|
| Preparing | Configuration or launch preparation is still in progress. |
| Starting | The request was accepted; final status is not confirmed. |
| Active | The contour confirmed operation. |
| Paused | The contour confirmed pause. |
| Stopping | Stop was accepted and completion is pending. |
| Stopped | The contour confirmed stop. |
| Error | The contour reported a problem requiring attention. |
| No current data | The latest confirmation is missing or stale. |
Why Status May Be Delayed
- The request is still being processed.
- The latest confirmation is stale.
- The contour is stopped or temporarily unavailable.
- Exchange and local states are not reconciled yet.
Page Boundary
Labels remain under Trading/Frontend review until user wording and internal states are fully mapped.
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.