Strategy testing and trading software · Germanycontact@stratcorealpha.com · DE
Free Strategy Rule Check

Claim-bounded cTrader engineering proof

cTrader Order Preflight

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.

Scope a cTrader build Inspect the tested C# sourceDownload proof PDF View the cTrader profile

Verified now

  • 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.

Still open

  • No authenticated owned demo runtime has been completed yet.
  • Open-market, invalid-volume and spread/session failure cases still require native runtime evidence.
  • Restart determinism plus independent positions and history checks remain open.
  • The cBot is not offered as a public download or finished product while those gates remain open.

Diagnostic checks

  • Minimum, maximum and step-aligned volume
  • Current symbol session and trading mode
  • 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
  • Persisted-versus-history restart baseline reconciliation

Safety boundary

  • AccessRights.None
  • No order placement, modification or cancellation call
  • No network, file-system or clipboard access
  • No broker credential or live-account requirement
  • No profitability or execution-quality promise

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.

Expected policy result

KEEP

PENDING_ACTIVE

The owned pending order is inside session and has not reached its expiry boundary.

No broker login, source code, trade command or form submission is used.

A funded QA scope freezes the exact owner key, timezone, session inclusivity, bar-count rule, restart procedure and expected evidence before any product is tested.

Request the boundary scope

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.

Case A

Valid hypothetical order

Expected: PASS or documented WARN, with no FAIL checks

Case B

Invalid volume step

Expected: FAIL with VOLUME_STEP

Case C

Market or spread failure

Expected: FAIL with MARKET_HOURS or SPREAD

Inspect the boundary policyInspect the 15 public testsOpen a public scope request

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.

Need a defined cBot?

Freeze ownership, timing, restart and failure rules before implementation.

Request a written fit decision

Trading risk disclosure

Futures and forex trading contains substantial risk and is not for every investor. An investor could potentially lose all or more than the initial investment. Risk capital is money that can be lost without jeopardizing one's financial security or lifestyle. Only risk capital should be used for trading, and only those with sufficient risk capital should consider trading. Past performance is not necessarily indicative of future results.

Hypothetical performance disclosure

Hypothetical performance results have many inherent limitations. No representation is being made that any account will or is likely to achieve profits or losses similar to those shown. There are frequently sharp differences between hypothetical performance results and the actual results subsequently achieved by any particular trading program. Hypothetical results are generally prepared with the benefit of hindsight, do not involve financial risk, and cannot completely account for the impact of financial risk in actual trading. Market conditions, the ability to withstand losses, and adherence to a trading program can all materially affect actual results.

NinjaTrader trademark disclosure

NinjaTrader® is a registered trademark of NinjaTrader Group, LLC. No NinjaTrader company has any affiliation with the owner, developer, or provider of the products or services described herein, or any interest, ownership or otherwise, in any such product or service, or endorses, recommends or approves any such product or service.

Testimonials, when shown, may not represent the experience of other clients and are not a guarantee of future performance or success. Virtual-currency trading carries additional risks. See the CFTC customer advisories. Read the full financial risk disclaimer.