ArdenAlgo · Concepts · Inducement

Inducement

Not in the engine · The trap before the trap — and why v1 stays out of it

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
  • Inducement describes minor liquidity engineered to bait entries before the real sweep.
  • The engine has no inducement detection: it maps levels and reacts to sweeps of them, full stop.
  • Identifying inducement usually requires judgement about intent, which mechanization cannot supply.
Not in mechanization v1 The engine does not detect, label or reason about inducement. There is no such object in the code and no such mark on the chart.

What the concept says

Inducement is the idea that some liquidity exists to be taken deliberately: a small, obvious pool placed before the real target, designed to pull traders in early so that the later move has something to run against. In this telling, the first sweep is the bait and the second is the business.

Why it is absent here

The concept is about intent, and intent is not in the bar data. Every mechanical version of it we could write reduces to "the smaller swing before the bigger one", which is a labelling choice rather than a discovery. Worse, that choice is easy to make in hindsight, and hindsight is the one ingredient this project spends most of its effort removing.

What the engine relies on instead

Structure. A sweep has to occur against a level that was already on the map before the bar formed, and it has to be answered by a displacement-validated structure shift inside a fixed window. Sequences that were bait mostly fail that second requirement and quietly time out — which is the same outcome an inducement filter would aim for, reached without a mind-reading step.

Common questions

Is inducement in the indicator?

No. Nothing on the chart is labelled as inducement, and no rule references it.

Could it be mechanized at all?

Some traders define it as the last minor swing before a major pool, which is codifiable. But the definitions in circulation disagree with each other, and picking one after seeing charts is exactly the freedom pre-registration is meant to remove.

Does the engine get trapped by inducement then?

Possibly, and that is an honest limitation. What protects the engine is not clairvoyance about traps but its requirements: a sweep only counts against an untapped mapped level, and it must be answered by a displacement-validated structure shift within a fixed window.

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

Liquidity sweep · Liquidity map · Full methodology