Why Do Some Cycle Lows Matter More Than Others?
Not every cycle low carries the same weight. A trough where only one short rung bottoms is a minor pause; a trough where several rungs of the ladder bottom together — 80-day, 20-week, sometimes more — tends to produce a bigger, cleaner move on the way back out. Confluence is the word for rungs lining up, and it's one of the clearest signals the method gives you for how much a given low should matter.
This page covers what confluence actually is, how to check for it on a real chart, why it changes the size of the move that follows, and why the same idea shows up — more rarely, and more meaningfully — at tops.
What is cycle confluence?
Every rung on the nominal cycle ladder has its own troughs — the 80-day bottoms roughly every 68 calendar days, the 40-day about every 34, and so on, each nested inside the one above it. Because the rungs nest by two, a trough of a longer cycle is mathematically also a trough of every shorter cycle beneath it. Most of the time that nesting is invisible on a chart, because the shorter rungs are also making their own troughs in between, at points where the longer rung isn't bottoming.
Confluence is what happens when the timing lines up in a way you can actually see: a longer-rung trough, a mid-rung trough, and sometimes a still-longer trough (20-week, 18-month) all landing on or near the same date. Phasing analysis marks these stacked confirmations with diamonds, one row per rung, directly under the date on the chart — a single diamond means one rung bottomed there; a tall stack means several did.
Why does a stacked low behave differently?
Go back to the companion principle behind the ladder: summation. Price at any moment is the sum of every rung plus the trend beneath them. If only the 10-day rung is bottoming on a given date, that rung's contribution to the sum turns up while the 20-day, 40-day, and 80-day rungs are still doing whatever they're doing — the net effect on price is small, because most of the stack isn't participating.
If the 80-day and the 20-week both bottom together, every rung nested inside them is, by definition, also near a trough at the same moment. The whole stack turns up together instead of one thread at a time. That is the entire mechanical reason a confluent low tends to launch a faster, cleaner, longer-running move than an ordinary one — more of the sum is pushing the same direction at once, not fighting itself.
The long version of this is in the book — Become a Cyclitecnical Trader: the cycle ladder, the FLD, and the eight interactions, written out end to end. It's free. Send me a copy. We email it to you. No card, and you can unsubscribe any time.
How do you actually check for confluence on a chart?
Work from the longest rung down, the same directional rule that governs counting any cycle low:
- Locate the longer-rung trough first. If you're checking a candidate 80-day low, confirm it against the 80-day's own spacing and depth before looking at anything shorter — a longer cycle's trough locates the shorter cycles' troughs beneath it, never the reverse.
- Check the next rung down for a trough on the same date, or within a few sessions. A trough that lands within the shorter rung's normal tolerance still counts as confluent; cycles run on averages with real spread, not to the day.
- Repeat one rung further down if the chart is clean enough to phase it. Three aligned rungs is a stronger read than two; four is rare and worth noting when it happens.
- Check one rung above, if you can see it. A 20-week trough landing on the same date as an 80-day trough is the single most reliable confluence signal on the ladder — it's the exact relationship the nominal ladder page flags as worth watching even for traders who never formally phase the 20-week.
The honest failure mode here is forcing it — squinting at troughs that are actually a week or two apart and calling them confluent because you want them to be. If the alignment needs an argument, it isn't confluence.
What does confluence change about how you trade the low?
| Single-rung low | Confluent low | |
|---|---|---|
| What's turning up | One rung only; the rest of the stack is mid-cycle | Multiple nested rungs together |
| Typical move off the low | Modest, often chopped by the shorter rungs still cycling | Faster, cleaner, tends to run further before the next real pause |
| How much weight to give it | Treat as one data point among several | Treat as the more significant turn on the chart right now |
| What invalidates it | A close back below the low on the shortest rung involved | A close below the low on the longest rung involved — the shorter rungs can misbehave without breaking the larger read |
None of this changes the discipline underneath it. A confluent low is still a read, not a certainty, and it still needs an invalidation level stated before the fact — the same rule that governs every call logged in the ledger, confluent or not.
Does the same idea apply at tops?
Yes, with an important asterisk already covered on this site: tops don't nest the way lows do. Because trend drags a cycle's peak off-center — translation — peaks from different rungs are naturally staggered rather than stacked, which is exactly why tops round off while lows snap. Confluent tops are rarer than confluent lows for that structural reason. When one does show up, it tends to be worth taking seriously precisely because it's unusual:
July 13, 2026 — S&P 500, the 80-day cycle probably topping with the 20-week topping alongside it — HIT. On the show that day the read was explicit: "I already know that the 80-day cycle is already probably topping. And by that, it's also the top of the 20-week cycle, probably." The stated plan was to favor stocks that had already moved at least two points, rather than fresh breakouts, on the view that the larger tide was turning. What happened: the index pushed to one more marginal higher close two sessions later, then rolled over hard — down about 2.7% from the call by two weeks out, and about 6.6% off the interim high, with the Nasdaq confirming a genuine correction over the same stretch, not just a stall. Two rungs topping together produced exactly the bigger, uglier move the confluence idea predicts — even on the side of the market where alignment is the exception, not the rule.
What confluence is not
- It is not a guarantee of size. It raises the odds of a bigger move; it does not set a target. Proportionality still governs how far any given rung tends to carry price, confluent or not.
- It is not visible every cycle. Most 80-day lows arrive without a clean 20-week alignment on top of them. Ordinary, non-confluent lows are the majority case, and they're still tradeable — just with a smaller expectation attached.
- It is not a substitute for counting the trough correctly in the first place. Confluence is a second-order read layered on top of a correctly identified low, not a shortcut around doing that work.
- It does not mean every rung has to line up. Two rungs aligning is real confluence. Waiting for four before acting on anything just means missing most of the good lows, which arrive with two or three.
Questions traders ask
How close do troughs need to be to count as confluent?
Close enough to fall inside the shorter rung's normal spread — a few sessions, not a few weeks. The nominal model is a ruler with real tolerance built in, not a metronome; two troughs a week apart on rungs that each run with several days of natural variation can still be a genuine alignment. If confirming it requires stretching the calendar past what that rung normally does, treat it as coincidence, not confluence.
Is a confluent low the same thing as a nested trough?
Related, but not identical. Nesting is the underlying mathematical fact — a longer rung's trough is always technically also a trough of every rung beneath it, whether or not you can see the shorter rungs' own troughs land there too. Confluence is the visible, checkable version: multiple rungs' troughs actually landing close enough together on the chart to phase and mark.
Can confluence happen on the way down too — multiple rungs peaking together and driving a sharper decline?
Yes, and the July 13 retrospective above is exactly that case: two rungs topping together produced a larger correction than either rung topping alone would have. The mechanism is symmetric — summation runs both directions — even though staggered peaks are the more common shape at tops, for the translation reasons covered on the tops-vs-bottoms page.
Confluence is one more piece of evidence, not a trigger on its own — the same way every read on this site sits alongside an invalidation level and a place in the ledger where it gets scored, win or lose. How every call here gets logged and graded is covered on the methodology page.
Keep reading
Get the Cycle Pass — from $297