Backtesting

Rule-card and Rust program strategies, versions, runs, cost profiles and forward tests.

BacktestingWhat a strategy, a version, a run and a forward test are, how the Strategies list, the strategy page and Compare are laid out, and where results live.
Rule-card strategiesEvery Strategy node in the workflow editor, field by field: the universe, indicators, rules, sizing, filters, the Program node, the Output and run parameters.
Program strategies in RustWrite a strategy as a Rust program: the editor, Build and Test, the on_bar function and the host interface, the Program node's settings, fuel and limits, and how Claude or an agent builds one.
Run a backtestEvery field of the Run dialog, the estimate and its checks, the run quotas, progress, cancelling a run, and what a completed run records.
Reading resultsThe strategy page after a run: the Overview chart and tiles, the Report, the Runs and Trades views, what each metric and column means, open positions and exit reasons.
Cost profilesThe four cost profiles and which ones a run can use, the default slippage and commission, what the report says about costs, and the costs no profile models.
VersionsWhen a backtest makes a version, how a run's settings make configurations and the trial count, how main starts and moves, and the change note a run can record.
Forward testingFreeze a completed run and re-run it after each settled session, on the same chart and trade list. Start one, read it, and see what updates cost and how a test stops.
Backtest, forward test and paperHow a backtest, a forward test and a paper deployment differ, what the simulation leaves out, and the fill, margin and benchmark rules every result rests on.
When trades happenThe exact timing of every decision and fill: the bar a strategy decides on, the bar it fills on, what an early close changes, and why paper fills differ from the backtest.
Avoiding overfittingA fitted backtest looks like a found one. Six rules, three warning bands, and how Orbital's trial count, deflated Sharpe and forward testing show how much of a result is luck.
Manage and delete strategiesFind strategies in the list, the gallery and the map, compare up to 20 on one chart, delete one or many, restore from Trash within 30 days, and what a running deployment locks.
Troubleshooting backtestsSymptom by symptom: a run that stays queued, a run limit, a refused estimate, a program that does not build, a workflow that is not a strategy, odd results and a stopped forward test.