Reading the parsed rules
The single most important habit in the whole platform: before you trust any result, read the rules the engine parsed from your sentence. This is what makes a backtest here reproducible instead of a black box.
Plain English is the source, the rules are the truth
Your sentence is the input, but the parsed rules are what actually run. Every condition (the indicator, the comparison, the timeframe, the direction) is spelled out explicitly. If the parse doesn't match what you meant, you edit the sentence, not some invisible setting.
Ambiguity resolves conservatively
Where a sentence could be read two ways, the engine tells you how it read it, and where it will not guess (a 'breakout', say) it stops and asks you to pick. Run this two condition example and check the parse: it should require RSI(14) below 35 AND price above the 200 day average, a dip inside an uptrend, not either one alone. The 14 is an assumption you never typed, and the parse says so.
Same input, same output, always
Because there's no randomness in the parse or the fill logic, the same sentence on the same data gives the same result every time. That determinism is what lets you compare two versions of an idea and trust the difference is your change, not noise.
Run it live
The strategy for this lesson, in plain English:
“Buy BTC when RSI is below 35 and the price is above the 200 day moving average; sell when RSI rises above 65, on 1D, last 3 years.”
It opens already parsed, so you can read the rules before you spend a run.
Key takeaway
If the result surprises you, read the parse first. Nine times out of ten the strategy did exactly what you wrote, just not what you meant.
Terms in this lesson
Check yourself