Level Retests: Testing Whether a Break Can Hold
After a confirmed break, a return to the same area can test whether the market accepts the new side of the level. Retest logic gives automation a second-stage confirmation instead of chasing the first impulse.
Freeze the broken level
Once breakout confirmation occurs, preserve the original level and its tolerance. Moving the reference after every candle makes retest logic impossible to test consistently.
Define the retest window
Set a maximum time or number of bars in which a return is considered related to the breakout. A much later visit should be evaluated as a new structural event.
Require a reaction
Touch alone is not confirmation. The engine can wait for rejection, renewed momentum or a close back in the breakout direction before handing the setup to risk sizing.
Implementation checklist
Automation principle: structure is useful only when the engine can express it as observable conditions, explicit states and a deterministic permission to act or wait.
Educational content for software design and trading-system research. Not investment advice. No profit is guaranteed.