Reference
Action Journal
A clear history of user requests, commands, states and errors.
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 journal collects events that explain what happened: an access request, contour command, confirmed state transition or error. It gives the user and Support one shared context.
API keys, full private exchange responses and internal infrastructure details do not belong in the journal. An unconfirmed event must not look completed.
What May Appear
- Access request and status change.
- Start, Pause or Stop request.
- Confirmation of a new contour state.
- An error with a clear next action.
- A position, order or execution event linked to the current session.
What Stays Hidden
- Secrets and API keys.
- Full private exchange responses.
- Internal paths, tokens and service data.
- Unconfirmed assumptions about an action result.
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.