Four labels, different objects
Keep geometry, lifecycle events and trading hypotheses separate. The table uses an explicit analytical convention; it does not claim a single authoritative definition for every SMC indicator.
| Label | Object to record | Additional choice needed |
|---|
| Order block | Selected candle range and the event that qualified it | Full wick range versus body; structural-break threshold |
| Fair value gap | Interval between bar 1 and bar 3 | Strict inequality, minimum width and completed-bar requirement |
| Mitigation | A later interaction with an existing zone | First touch, midpoint, full traversal or closing breach |
| Mitigation block | A named failure or return setup in a particular method | Its swing sequence and whether a prior sweep is excluded |
| Breaker block | Previously active zone after invalidation | Whether to wait for a retest or require a prior sweep |
Calculate an FVG without inventing order-flow evidence
For three completed candles numbered 1, 2 and 3, this example defines a bullish FVG when low(3) > high(1), with bounds high(1) to low(3). A bearish FVG requires high(3) < low(1). Equal values produce zero width and do not qualify. This is a chart-range condition: it does not mean the middle candle contained no trades or that only buyers were filled.
| Hypothetical values | Result | Width |
|---|
| High(1)=100; low(3)=102 | Bullish interval 100–102 | 2 price units |
| Low(1)=105; high(3)=103 | Bearish interval 103–105 | 2 price units |
| High(1)=100; low(3)=100 | No bullish gap under the strict rule | 0 |
Why “mitigation” needs a definition
LuxAlgo publishes close, wick and average-level mitigation choices for its zones. A rule based on touching the near edge will mark an event earlier than a rule requiring a close beyond the far edge. A chart that removes a rectangle can therefore disagree with another chart without either using different prices.
When comparing a mitigation-block method that excludes a prior swing sweep with a breaker method that requires one, state those conditions as your chosen taxonomy. The labels do not establish that one has higher conviction or that trapped traders must exit at breakeven. Record the swing price, confirmation time and exact crossing test so another person can reproduce the classification.
Overlap is geometry, not independent confirmation
Suppose an order-block zone is 99–102 and a bullish FVG is 101–103. Their shared interval is 101–102, width 1. The intersection is found by taking the larger lower bound and smaller upper bound. If those values are equal, the zones only touch; if the lower result exceeds the upper result, there is no overlap.
This example does not imply that two signals double the evidence. Both may be derived from the same price move. Compare an order-block-only rule with the same rule plus the overlap filter on held-out data, including how many opportunities the filter removes.
A useful event log for comparing tools
Keep the same fields for every detected zone, including those that fail.
- Store symbol, exchange feed, timeframe and timezone; different candles can create different gaps.
- For each zone, save the bounds, origin time and first detection time. A retrospectively drawn pivot was not necessarily known at its origin.
- Record gap formation only after candle 3 is complete if that is the chosen rule. Intrabar highs and lows can change.
- Track first touch, midpoint reach, full traversal and invalidation separately rather than using one ambiguous “filled” flag.
- Record expiry and overlapping-zone selection so deleted historical rectangles do not silently disappear from the sample.
What to ask a coding tool to implement
Ask Pineify for a script with separate zone arrays and explicit creation, touch and invalidation events. Supply your definitions instead of asking for “the best SMC strategy.” Review the generated source and use TradingView to check timing and behavior. Keep simulated fills and transaction costs separate from the drawing logic; a highlighted gap is not an order.