Trendline Confluence Engine

From Swing Pivots to a Managed Trade

Everything starts with a search, not an assumption. Instead of connecting the two most recent swing points, the engine scores recent swing highs and lows against each other and keeps the slope with the most confirmed touches, then carries that line through the rest of its lifecycle.

GBP/JPY, 15m. The full read at once: an ascending channel with its equilibrium ray, a confirmed Macro Break, and the dashboard scoring the active support line at a 20% Confluence.

Multi-Pivot Consensus

Rather than anchoring to whichever two swings happened most recently, the engine looks back across recent swing highs (for resistance) or swing lows (for support) and searches for the single slope that connects the most of them with the fewest violations. Any candidate line that price has already closed through is discarded before it's ever drawn, so what survives is the line the market has actually respected, not just the newest one. Pivot lookback auto-scales to the chart's own timeframe, from 15-second charts up to Monthly, so the same logic holds a sensible window whether you're scalping or swinging.

The Channel & Equilibrium Ray

Once a trendline is chosen, a parallel channel is built around it, sized to the furthest wick that hasn't yet breached it, with an optional 50% median line splitting the two boundaries. A single equilibrium ray runs inside that channel, calculated one of two ways:

Confirming a Break

A break only confirms once price closes beyond the line by an ATR-scaled buffer, on a directional candle body, after the line has accumulated enough confirmed touches, and within a slope angle that rules out a hyper-steep line breaking from time drift alone. On top of that base logic, a filter mode controls which confirmed breaks actually print:

Touch & Angle Grades

Every line carries its own grade, A+, A, or B, built from how many times it's been touched and how moderate its slope angle is. A line with a long, patient history of confirmed touches at a reasonable angle grades higher than a fresh, steep line that happens to break in the same direction. The grade travels with the line everywhere it's referenced, on the chart badge, in the dashboard's Nearest Support/Resist rows, and in the Confluence Score.

Retests, Sweeps & the Apex Squeeze

A broken line doesn't disappear. It's watched for a pullback touch and rejection, printed as a Break and Retest signal when it happens. Separately, a wick that pierces a still-active line but closes back inside it is flagged as a Liquidity Sweep rather than a genuine break, price rejected the level instead of breaking it. And when an active support and resistance pair compresses into a tight spread, the indicator flags an Apex Squeeze and estimates how many bars remain until the two lines converge.

Gold Spot/USD, 1h. Several full cycles on one chart, confirmed breaks, retests, and a Minor/Micro Break from the secondary intraday trendline layer, as the range develops.

The Confluence Score

Five factors, macro trend alignment, relative volume and delta, touch count, slope angle, and higher-timeframe bias, combine into a single percentage score with a pass/fail checklist, evaluated for whichever line is currently the most relevant. It's a read on how well-supported that line already is, not a forecast of what price does next. A high score describes the structure behind the line; it doesn't mean a break is imminent.

Trade Lifecycle: Targets & Breakeven

A confirmed break sets a structural invalidation level and, if enabled, up to three take-profit targets, either channel and Fibonacci-based or a fixed risk-reward multiple. Reaching the first target ratchets the invalidation up to breakeven plus a small ATR buffer, taking the original risk off the table. Reaching the second trails that invalidation up again to the first target, so the ray protecting the trade keeps climbing as it works rather than sitting fixed at the original stop.

SOL/USDT, 1h. A confirmed break running through TP1, TP2, and the 1.618 Fibonacci extension, with the invalidation ray trailing up behind price as each target is reached.

Higher-Timeframe Confluence

A higher-timeframe pivot ray is auto-selected in proportion to the chart's own timeframe, no manual pairing required. It's used two ways: a break that also clears this HTF ray earns the Macro grade, and the ray's position feeds into the Confluence Score as one of its five factors.

Reading the Panel

Alerts

Alert messages can be plain text, structured JSON, or both. A dedicated Automation and Bot Webhooks section formats the same events as ready-to-send payloads for Universal JSON, 3Commas, PineConnector, or Alertatron and custom bridges.

Does It Repaint?

Trendlines, channels, breaks, retests, and dashboard values are all committed on confirmed bar closes, and higher and lower-timeframe data uses non-repainting settings. A printed break, retest, or sweep signal never moves or disappears afterward. The one exception worth knowing: the channel's equilibrium ray can settle slightly on the still-forming live bar before locking in at that bar's close. That's an active recalculation on unconfirmed data, not a repaint of a completed signal.

What It Does Not Mean