Most glossaries in this niche describe patterns. These pages describe what our engine does with them — including the ones it refuses to touch. If a concept is missing from the first two groups, it is missing from the engine, and the third group explains why.
Six concepts, in the order the engine applies them. Each page has the exact rule, a live chart the engine marked, and one it deliberately left alone.
Where stops actually rest
Stops taken, move rejected
The rejection grows teeth
The inefficiency the move leaves behind
The footprint of the move's origin
Location decides whether a setup exists
Mechanisms that gate every setup above but rarely get their own page elsewhere.
The energy filter every setup has to pass
The double top retail draws, read as a stop cluster
Well-known ICT ideas that mechanization v1 does not compute. These pages exist so the answer is findable instead of implied — each one states what the concept claims, and why it is absent.
A popular concept this engine does not trade
The trap before the trap — and why v1 stays out of it
What happens to a gap that fails — in theory, and here
Time-of-day filters — deliberately absent from v1
The Fibonacci layer this engine does without
Accumulation, manipulation, distribution — as narrative, not code
Two pairs that get confused constantly, separated by the rule that actually distinguishes them.
Siblings from one displacement leg — and what each one does here
One bar, two readings — separated by where the body closes
ArdenAlgo