Trading Contour
Trading Contour
What trading contour means and why it is separate from Labs, portfolio and strategy.
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.
The trading contour is the runtime layer that accepts prepared configuration, writes heartbeat/status and handles Start, Pause and Stop commands. This is a beta area: the public docs describe only verified control-plane and status snapshots.
The contour is not Labs and not the portfolio. Labs shows research/live artifacts, portfolio shows a safe account snapshot, and the contour handles runtime commands.
What Users See
- Current contour status.
- Start, Pause and Stop buttons when the state allows the action.
- Latest heartbeat, position, orders and events when sources are available.
How It Works
- The cabinet creates a runtime control request.
- A worker claims the request, applies the command and writes heartbeat.
- Dashboard resolves the resulting status from request, heartbeat, run status and exchange evidence.
Risks
Do not treat a button click as the final state. Final state is confirmed by heartbeat or other safe evidence.