cTrader cBot Boundary Proof — 22/22 Tests by Arnold HolmcTrader cBot Boundary Proof — 22/22 Tests by Arnold Holm

cTrader cBot Boundary Proof — 22/22 Tests

Arnold Holm

Arnold Holm

Claim-bounded cTrader engineering proof
A read-only cBot that evaluates one hypothetical order against the current symbol and account environment. This page shows what has been verified and what still blocks a public runtime claim.
Spotware cTrader CLI 5.9.10 rebuilt the four-source package without warnings and classifies it as Type=cBot with AccessRights=None.
Official cTrader Desktop 5.9.10 is installed and imported the owned package into its Robots tree.
Twenty-two automated tests pass, including source guards against order, modify, cancel, close and reverse APIs.
Pure policy tests cover strategy ownership, session boundaries, N-bar expiry, restart determinism and fail-closed daily-risk baseline reconciliation.
A fail-closed evidence verifier passes three synthetic A/B/C workflow tests and rejects a mismatched case.
The production build completes with zero errors; two disclosed workstation LIB-path warnings remain.
The cBot is not offered as a public download or finished product while those gates remain open.
Bid, ask, pip size and spread ceiling
Requested stop-loss and take-profit distances
Non-pip broker distance units as an explicit warning
Account environment and broker context in deterministic logs
Half-open and overnight session boundaries
Exact N-bar pending expiry and foreign/manual ownership protection
Interactive specification preview

Order lifecycle boundary lab

Freeze the ownership and session rules before implementation. This browser-local preview applies the same action priority as the tested policy source; it does not connect to cTrader or send account data.
PENDING_ACTIVE
The owned pending order is inside session and has not reached its expiry boundary.
Runtime evidence contract

Three demo cases, one fail-closed verifier

The verifier accepts only cTrader logs that explicitly state NO_TRADE=true and ACCOUNT_ENV=DEMO. It then checks the case-specific result, unchanged redacted position/order/history counts and an optional restart severity/code signature.
The bundled fixtures test the verification workflow only. They are not native cTrader, broker or demo-account runtime evidence.
What the result means

Preflight evidence, not execution assurance

A later PASS will mean only that the checked preconditions passed for that symbol and instant. Broker state can change before a real request, and the utility does not test strategy quality, fills, slippage or returns.
Like this project

Posted Aug 12, 2026

Built a read-only cBot preflight and state-boundary suite: 22/22 tests, 3/3 synthetic verifier cases and AccessRights.None. Native demo runtime remains open.