Does your second condition do anything?
"Add a confirmation" is the most common advice in strategy building and the least often checked. A second condition can do exactly one of three things, and which one is measurable in two runs of the Strategy Tester.
The test
- Build the strategy with both conditions. Note the trade count — call it B.
- Remove the second condition. Note the trade count — call it A.
- Compare.
| Result | What it means | What to do |
|---|---|---|
| B = A | the second condition never excluded a single trade | delete it — it is decoration |
| B is slightly below A | it filters a minority of trades | keep it if the remaining trades are better |
| B is far below A | the two conditions rarely agree | you have two strategies fighting, not a confluence |
| B = 0 | they never agree | one of them is probably mis-specified |
The first row is far more common than people expect, and it has a specific cause: two conditions derived from the same series are the same condition. A MACD line crossing its signal and a MACD histogram turning positive are one event, which is the double-count. A Bollinger middle band and a moving average of the same period are the same series.
Why "far below A" is not a success
It feels like rigour — only the very best setups get through — and it is usually a sample-size problem. Cutting your trade count from 300 to 20 does not give you a more selective strategy; it gives you a strategy you can no longer evaluate, because twenty trades cannot distinguish an edge from luck.
The evidence list in what to hold before risking money puts the threshold at about a hundred trades. A filter that takes you below that has cost you the ability to test, which is a worse trade than whatever it improved.
Building the stochastic and moving-average version
The honest confluence here is oscillator plus trend, because the two genuinely can disagree — one measures position within a recent range, the other measures direction over a longer window:
| Field | Value | Role |
|---|---|---|
| %K length / smoothing | 14 / 3 | the timing signal |
| %D smoothing | 3 | |
| Entry trigger | %K crosses above %D below 20 | |
| Trend filter | price above a 50-period MA | the second condition |
| Exit | %K crosses below %D, or an ATR stop |
Now run the count test on the trend filter specifically. On a trending instrument it should remove a meaningful minority of trades — the ones that were counter-trend oscillator signals, which is exactly the failure the stochastic alone suffers from: why the stochastic pins in trends.
One more thing worth counting
Each condition you add is a parameter set you chose, and choosing among alternatives biases the winner. So record how many confluence combinations you tried before settling on this one — the reasoning is in testing ten variations, and it applies to structural choices just as much as to threshold values.
Tactix AI — Studio vs Guide
Tactix AI is AlfaTactix’s product assistant brand (open Tactix AI).
- Tactix Studio turns a one-sentence strategy description into a draft across Timeframe, Signals, Filters, and Risk in the visual Strategy Builder. You review and edit every field before Code Generator writes MQL5 or Pine Script.
- Tactix Guide explains the step you are on — what to fill, what a control means, or how to phrase a rule — without dumping untested source code.
That is form-first automation: the LLM never replaces Code Generator, and you keep plan limits and real-time validation.