Signal Hooks

Signal philosophy

IIF signals are context stamps, not trade calls. Each one certifies that a specific multi-condition sequence completed at a qualified location: price interacting with a tracked OrderBlock in a particular way, often gated by the CVMI. They compress several bars of orderflow reading into one label, and every one of them executes on confirmed bars only, so a printed signal never disappears.

Block Exhaustion

Default label: “Exhaust” The reversal-condition signal. It certifies that an OrderBlock has absorbed nearly everything thrown at it while the market is stretched: the classic setup for structural reversion.

Exhaustion is a two-stage signal (available when the oscillator is normalized):

• Arming: the block's mitigation reaches the configured fill threshold (default 85%) and the normalized CVMI reaches its extreme (default ≤ 25 bullish / ≥ 75 bearish).
• Firing, controlled by Trigger Mode: Instant (the moment both conditions hold), Osc Exit (default: when CVMI exits the extreme, i.e. pressure starts releasing), or Rebalance (when price closes back outside the block, confirming the bounce).

The three trigger modes span the aggression spectrum: Instant is earliest and noisiest, Rebalance is latest and most confirmed. Off by default; enable it in 05 Signals - Block Exhaustion.

Block Sweep

Default label: “Sweep” (on by default) The stop-hunt detector. It fires when price closes beyond an OrderBlock edge, then reclaims the zone and proves acceptance back inside it.

The qualification chain:

• Sweep depth is bounded. Max Hunt × Width (default 0.33) caps how far beyond the edge price may travel; a close 1.5 block-widths below the zone is a breakdown, not a sweep. Set 0 to accept any wick beyond the edge.
• Reclaim must be proven. Reclaim Closes (default 4) consecutive closes back inside the block are required before the label prints.
• Optional CVMI gate. With Oscillator Filter on, the signal additionally requires CVMI at the favorable extreme (≤ 25 for bullish sweeps, ≥ 75 for bearish).

Block Failure

Default label: “Break”The invalidation signal: the mirror image of a bounce. When price breaches a block's structural break level (see SOMM Phase 3), the block retires and this label marks the spot.

• Trigger: Close (default) requires a confirmed close beyond the level; Wick fails the block on any excursion.
• Directionality: a bullish OB broken downward is a bearish failure event; a bearish OB broken upward is bullish. Failed zones flip their meaning: overpowered demand often becomes supply.
• Usage: counter-trend traders read failures as continuation fuel; mean-reversion traders read them as the definitive “stand aside” marker for that zone.

Structural Shifts

Shift lines are the framework's regime markers: horizontal levels derived from qualified HTF displacement-exit sequences (consecutive HTF gap structure validated by a confirmation bar), optionally snapped to the nearest same-direction LTF gap for surgical placement.

• While intact: a bullish shift below price is territory buyers should defend; the line doubles as a structural stop reference.
• When broken: market flow has genuinely changed hands. Breaks are confirmed by Bars Tolerance consecutive closes (default 6) or a single wick, per Break Confirm.
• As events: both Shift Detected and Shift Broken are available as alert events and Confluence Engine triggers.

Unconfirmed shift lines are color-differentiated while forming, then solidify once confirmed, matching the same no-repaint visual convention used across the framework.

Labels & history

Every signal on this page has bullish and bearish alert variants. Wiring them into webhooks is covered in Alerts & Webhooks, and combining them with filters is the job of the Confluence Engine.