Axiom Strategy Lab Pro

What this is

Most trading ideas die untested. The thesis lives in your head — a crossover filtered by volume, a mean reversion entry gated on volatility, an exit ladder that scales out in thirds — and it stays there because the distance between having the idea and running an honest test against history is too wide. You either learn Pine Script, trust someone else's opaque strategy you cannot inspect, or backtest manually on a chart, scrolling bar by bar while pretending hindsight is not doing half the work.

Axiom Strategy Lab Pro is a low-code strategy builder for TradingView that closes that gap. You write your trading rules in structured YAML instead of Pine Script, and the engine tests them against historical data inside the strategy tester. It parses your rules, evaluates them bar by bar, manages order execution, and reports the results.

Nothing is pre-built. The YAML inputs start empty. You define the setups, the entries, and the exits in YAML, then set direction, sizing, slippage, commission, and risk controls through the settings and Properties tabs. If you do not bring a thesis, the tool has nothing to test. The core job is hypothesis testing — giving you a controlled environment to find out whether your rules hold up under honest conditions before you commit real money to them.

Who this is for

Traders who have enough experience to hold a thesis about entries, exits, and risk — but who have been stuck. Stuck trusting opaque strategies they cannot inspect. Stuck manually backtesting on charts, bar by bar. Stuck waiting to learn Pine Script before they can test the idea they had three months ago.

If you want to own your strategy — understand every rule, adapt every parameter, explain why it works when it works and why it fails when it fails — this tool was built for that kind of work.

Who this is not for

If you are looking for a ready-made strategy that works out of the box, this is not it. There are no built-in setups, no default signals, no pre-configured entries. The tool is the apparatus. You are the researcher.

If you are not willing to learn the YAML schema and expression syntax, the learning curve will be frustrating. This is low-code, not no-effort. The structure replaces Pine Script, but it still requires careful attention to how rules are defined and how they interact.

If you plan to optimize until the equity curve looks good and then automate without further validation — stop here and read Backtesting & Realism and Optimization before going further.

The honesty boundary you need to know

Every result this tool produces is a simulation. The strategy tester fills orders using assumptions about slippage, commission, and price sequence that may not match your actual broker, your actual asset, or your actual market conditions. A profitable backtest is a hypothesis, not a conclusion. The distance between simulated results and live performance is real, and this manual will keep reminding you of that — not because the tool is broken, but because the gap is where most trading losses actually start.

Where to start

If you are new to the tool, start with Quick Start. It walks through the shortest honest setup path — from adding the script to your chart through the first checkpoint where you can verify the engine is reading your rules correctly.

If you want to understand how setups gate entries, how exits are sized against the position, and how the YAML hierarchy controls evaluation order, go to Rules & Risk.

If you want to understand what the strategy tester actually assumes about your fills — and where those assumptions break down — go to Backtesting & Realism. If you only read one page beyond the quick start, that should be the one.

If you want the reference material for building your YAML:

• Default Tokens - every named value the engine makes available to your expressions

• Expression Reference - operators, functions, and the full expression syntax

• YAML Reference - every field in every YAML section, with defaults and usage guidance

• Diagnostics & Error Codes - how to read validation errors, warnings, and expression/runtime diagnostics

If you want guided examples you can paste, inspect, and learn from, Teaching Examples walks through four strategies from beginner to extreme.

If something is not working the way you expected, go to Troubleshooting. If the diagnostics table is showing a specific code, use Diagnostics & Error Codes as the field guide.

If you want to understand the engine's deeper mechanics - the setup state machine, the expression pipeline, state tokens, OCA behavior, and how independent exit units work against the shared position - For the Geeks is there when you are ready for it.