Liquidity Pools, Sweeps and Market Structure

Model swing extremes, equal highs/lows and liquidity sweeps as context—not guaranteed targets.

Where liquidity references form

A practical chart model can mark prior highs and lows, confirmed swing points, clusters of approximately equal highs/lows and repeated compression structures. These locations are useful because many trading rules naturally place orders around obvious extremes.

Sweep is an event, not a trade

A sweep only tells the engine that price traded through a mapped liquidity reference. It does not prove reversal. The next questions are whether the higher-timeframe context supports reversal, whether displacement follows, and whether local structure actually shifts.

Liquidity quality

Instead of treating every swing equally, an engine can score age, number of nearby equal extremes, timeframe, distance from price and whether the level has already been partially traded through.

pool_score = timeframe_weight + equal_extremes + age_weight
if swept and htf_context_ok and displacement and structure_shift:
    reversal_candidate = true

Stops and liquidity

A structural stop may sit beyond an invalidation swing, but a known liquidity pool near that swing is also a reason to avoid mechanically tightening protection into obvious short-term noise.

Educational engineering material. These are testable market models and implementation ideas, not investment advice or guarantees of performance.