Reading a strategy page
Everything a run produced, from the hypothesis to the analyst's last decision.
Header and stage
The top of the page shows the strategy name, its venue and instrument, the current stage badge and the owner's controls: pause, resume, stop, promote to paper, promote to live and share a track record. Platform strategies show the same information without the controls.
Metrics and the equity curve
The metrics block reports net return, Sharpe ratio, maximum drawdown, profit factor, win rate, trade count and the average return per trade as a percentage of notional. The equity curve is marked to market on every bar and includes funding and market impact, so it matches the drawdown figure.
Trades and positions
The trade list shows each entry and exit with side, size, duration, commissions and profit. Open positions at the end of the test are reported separately so unrealised results are never mixed into realised ones.
Verification and QA
The verification block lists each layer with a pass or fail, the sandbox trade count and the failure text when a layer failed. QA findings that changed the code are visible in the run's iteration history.
Optimisation results
After optimisation the page shows the parameter search ranges, the chosen parameters, the walk-forward in-sample and out-of-sample results per window, the holdout result, the sensitivity plateaus, parameter stability and the significance statistics the analyst used.
Forecast quality
The forecast quality card measures the strategy's signal as a forecast: how well it predicts the next period's return, how often it changes, and the edge left after trading costs. It is a diagnostic only and never changes the backtest; a signal that depends on the open position can score low while its trades are profitable.
Library refinements
When a strategy is iterated, the Library Refiner's cited suggestions are listed here with the document and page each one came from. The owner can also request a refinement at any time.
Decisions and history
Every analyst verdict, gate result, waiver and risk review is stored with its reasoning and timestamp. Reading this history explains why a strategy was iterated 3 times, or why a promising backtest was abandoned after optimisation.
Public research pages
Strategies and hypotheses from the platform's own research, and strategies listed on the marketplace, are also published as public research articles that anyone can read without signing in, in many languages. They include rejected strategies with the findings that ended them, so a reader can see why a positive headline return was not enough. Strategies in your workspace stay private unless you list them.
Source code
The strategy's code is shown with a copy button. Marketplace subscribers see code only when the listing offers it and their subscription is active; owners always do. The code is the exact artifact that was verified, backtested and, if promoted, is running in paper or live trading. The Export section ports it to other platforms.