Align, then confirm: the two-beat workflow for finding termination zones.

Beat one

Align — scan the HUD for stacks and flips.

The first movement happens on the lower pane. Working from the trading timeframe, the operator scans for phase flips and stacking — the manual's example being higher timeframes turning lime for impulse up while the fast charts finish an orange or teal corrective. When either convergence count reaches MinN, the market has entered a setup regime; at SpecialN, a high-conviction one. Crucially, this beat produces a state, not a trade: knowing that four timeframes are aligned tells you conditions favour continuation, and says nothing yet about where price should be engaged.

Beat two

Confirm — read the overlay for the cluster.

The second movement moves to price. With pivot gating enabled and wave lines shown, the overlay marks bars where alignment coincides with fresh pivot confirmation — and the thing to watch for is multiple timeframes confirming pivots at or near the same price area. That cluster is the termination zone: the end of a corrective leg, or the exhaustion of an impulse, depending on direction. The wave lines make it visible whether timeframes are genuinely converging on one level or merely each doing something nearby, which is the difference between a real zone and a coincidence.

The two classic cases

Continuation and correction, read the same way.

The manual names two use cases that cover most of the tool's practical work. Bullish continuation: the HUD shows higher timeframes at impulse up while lower ones rotate from corrective into impulse, the overlay prints its impulse label, and entries are sought on pullbacks near the cluster of confirmed lows — then managed toward the system's R targets. Bearish reversal or correction: several timeframes flip to corrective down, the overlay prints at a multi-timeframe swing-high cluster, and the read is used either to manage for shorter targets or, just as usefully, to avoid fading the first impulse. That second application is worth noting — a signal used to decline a trade is doing real work.

Pivot sweet spots

Sensitivity tuned per timeframe, not globally.

Pivot detection settings determine what counts as a structural turn, and the manual's tested recommendations differ by timeframe rather than applying one value everywhere. On the fifteen-minute chart, 5/5 lines up well with the EMA stack — by the time the EMAs confirm, a 5/5 pivot there is almost always real structure. On the hourly, 8/8 is the balance point: it filters intraday noise while remaining responsive enough to catch genuine bias shifts, where 3/3 marks nearly every wiggle and 10/10 becomes very clean but slow. On the four-hour, 10/10 or 12/12 matches daily structure and makes convergence with higher-timeframe pivots meaningful, where 5/5 produces mid-leg noise. The principle: a pivot should represent a structural turn on the timeframe it's detected on.

• 15m → 5/5 · 1h → 8/8 · 4h → 10/10 or 12/12. Sensitivity decreases as timeframe increases.
• Too-tight pivots on high timeframes destroy the convergence read — mid-leg pivots cluster at levels that mean nothing.
• Settings are per-timeframe by design; a single global pivot setting is wrong on most of the rows it applies to.

The key idea

Regime and location are different questions.

The two-beat structure exists because 'conditions favour continuation' and 'here is where to engage' are separate findings requiring separate instruments. The HUD answers the first from timeframe alignment; the overlay answers the second from pivot clustering on price. An operator who tries to get both from one view will either trade regimes without locations or locations without context — and the discipline of running both beats, in order, every setup, is what keeps the tool producing decisions instead of impressions.