ArdenAlgo · Concepts · Breaker block

Breaker block

Not in the engine · A popular concept this engine does not trade

Published 24 Jul 2026 · every rule box checked against mechanization v1 (frozen 16 Jul 2026) · parameter changes land in the changelog first

In three sentences
  • A breaker is a failed order block: price violates the zone, then returns to it from the other side.
  • Mechanization v1 does not detect or trade breakers — the engine discards a zone once it is violated.
  • Breaker and mitigation blocks are recorded as a v2 idea, not a hidden feature.
Not in mechanization v1 This page exists so the answer is findable. The engine does not detect, draw or trade breaker blocks. It appears in our internal notes under "v2 ideas — not built", together with mitigation blocks.

What the concept says

A breaker starts life as an order block that fails. Price pushes through the zone instead of respecting it, then later comes back to the same area from the opposite side. The claim is that the broken zone flips polarity: former support becomes resistance, with the original absorption now trapped on the wrong side.

What this engine does instead

When a zone is violated, this engine deletes it. A consumed zone cannot arm a setup again, and there is no bookkeeping that tracks it as a flipped level. The chain stays deliberately short: bias, zone, sweep, structure shift, retest. Breakers would add a second life to objects the current design treats as spent.

Why the narrow scope is the point

A wider pattern library reads as sophistication and behaves as flexibility — and flexibility is precisely what makes a strategy unfalsifiable. The pre-registered evaluation only means something because the rule set was frozen before the data arrived. If breakers earn their place, they earn it in a version of their own, with their own record.

Common questions

Does the indicator draw breakers?

No. If you see a zone on our TradingView showcase, it is an order block or a fair value gap. Nothing on the chart represents a breaker.

Why not just add it?

Because every added pattern multiplies the ways a result can be fitted after the fact. Mechanization v1 was frozen deliberately narrow so that its evaluation means something; new patterns belong to a new, separately evaluated version.

Will it be added later?

It is on the recorded v2 list along with mitigation blocks, a lower-timeframe entry layer and session conditioning. If any of them ships, it ships as a version with a dated changelog entry, not as a silent update.

No chart example — on purposeThere is no screenshot of this concept anywhere on this site, because the indicator never draws it. Publishing an illustration of something the engine does not compute is exactly the kind of decorative proof this project exists to avoid.

Related

Order block · Market structure shift · Full methodology