Writing Conditions the AI Understands

How to describe your rules so the Backtrex AI writes them as testable conditions: indicators, SMC/ICT, sessions, sequences, stop and target. With examples.

No catalogue, your words

Backtrex has no indicator list to pick from. You describe the rule, the AI writes it as a custom condition. RSI, Bollinger, Ichimoku, order blocks, fair value gaps, sessions: anything that can be measured on prices can become a condition.

The quality of the block depends on how precise your sentence is. This guide shows how to write it.

The five ingredients of a good rule

  1. What: the indicator or structure, with its settings (RSI 14, 200 EMA, FVG)
  2. Compared with what: a threshold, another line, a level
  3. When: on the closed candle, on the cross, within the last N candles
  4. On which timeframe: M15, H1, D1...
  5. Which side: buy, sell, or both mirrored

Whatever you leave out, the AI assumes and flags as an assumption. Fewer assumptions, fewer surprises.

Indicator examples

Too vagueTestable
RSI oversoldRSI 14 below 30 on the closed candle, on M15
The averages crossThe 20 EMA crosses above the 50 EMA, on H1
UptrendClose above the 200 EMA on D1
Tight BollingerBollinger (20, 2) band width at its lowest of the last 50 candles
Decent volatilityATR 14 above its 20-candle average
Bullish MACDMACD line (12, 26, 9) crosses above its signal line

One detail matters: crosses is true on a single candle, above stays true for the whole trend. The cross triggers, the comparison filters.

SMC / ICT examples

Too vagueTestable
Order block entryPrice returns into a bullish M15 order block formed within the last 30 candles
FVG filledPrice touches the midpoint of a still-open bullish H1 fair value gap
Liquidity grabThe previous day's low is swept, then the candle closes back above it
CHoCHBullish change of character on M15: close above the last swing high
London kill zoneBetween 07:00 and 10:00 UTC
Premium / discountPrice is below the midpoint of the last H4 swing (discount zone)

Always give the time zone of your hours. Without it, the AI assumes one and flags it.

Writing a sequence

When order matters, say so, with a delay:

First, price sweeps the Asian session high.
Then, within the next 20 M15 candles, a bearish change of character.
Then I sell on the return into the fair value gap it created.
Cancelled if price closes above the swept high.

The AI turns this into steps linked by THEN, each with its maximum delay in candles, editable later without the AI.

Writing the risk

  • Stop: a distance ("20 pips") or a level ("below the order block", "on the other side of the range")
  • Target: a multiple of risk ("2R", "2 times the risk") or a level
  • Management: break-even, trailing stop, exit after N candles, number of trades per day

A stop or target placed on a level shows as Level in the builder: hover it to see which one.

What cannot be tested

Some sentences stay non-testable, with their reason:

  • Real volume and the order book: they are not in the data
  • News: it is not in the data
  • Feelings ("when the market looks clean"): no measurable rule

Click Make precise and replace them with what you really look at: "when ATR 14 is above its average" rather than "when the market moves".

What is refused

A condition that reads the future cannot be added. Examples:

  • "the day's high" used before the day is over
  • a pivot confirmed N candles later, used on the candle itself
  • "if the trade goes the right way"

The AI explains why. Rephrase with what is known at decision time: "the previous day's high", "the last confirmed pivot".

Tips

  • One rule per sentence: easier to review, tick and untick
  • Start simple: two or three conditions, then add filters one at a time
  • Review the assumptions before the first backtest