Left Translation vs Right Translation in Market Cycles

Translation is where a cycle's peak sits inside its span. A peak that arrives late — right of center — means the cycles larger than the one you're watching are pulling price up. A peak that arrives early — left of center — means they're pulling it down. Read the peak's position and you're reading the whole tide underneath the cycle, without phasing a single one of the larger waves.

That's the core of it. The useful detail is why the peak moves, why highs shift far more than lows, and what translation can and can't tell you in real time.

What actually moves a cycle's peak?

In cycle work, price is modeled as a trend plus the sum of a family of repeating waves. No single cycle prints its own peak in isolation. The high you see on a chart is made by a shorter cycle cresting on top of the one you're watching, with everything larger pushing underneath.

When the sum of the larger cycles is rising, price keeps grinding upward past the point where your cycle's true crest occurred — so the printed high lands late, shifted right. When the larger sum is falling, the tide overwhelms the cycle's rise well before its crest is due — so the printed high lands early, shifted left. Lows shift the opposite way, and by much less: an uptrend nudges the printed low earlier, a downtrend nudges it later.

So translation isn't a new force. It's trend made visible inside a single cycle's span. That's what makes it useful: the trend under any cycle is the sum of everything longer, and part of that sum comes from cycles too large to phase at all — the book's word for that unseen remainder is sigma-L. Translation is one of the few ways the chart reports on sigma-L directly.

What do right and left translation look like?

On the 80-day cycle — the one we work most, covered in the 80-day cycle — translation shows up as the shape of an "M." Each 80-day span draws two legs, one per 40-day cycle inside it. In a bullish 80-day cycle, the second 40-day cycle carries price back up to a higher peak: the M's second hump is the taller one, and the cycle's real top lands late. In a bearish cycle the second leg fails below the first: the top was in early, and most of the span is spent declining. The second half of the M is where the cycle confesses.

The book pairs this with a duration tendency worth knowing: shorter 80-day cycles — under about 68 days — are usually bullish, while long ones in the 75-to-80-day range are usually bearish. Duration and translation are different measurements, but both are downstream of the same larger-cycle trend.

Why do highs translate more than lows?

Highs translate far more than lows. In an uptrend the printed high can drift well right of the true crest, and it often splits into two or three sub-peaks as shorter cycles crest one after another on the way over the top. Lows barely move by comparison.

The reason is the same pair of principles that build market bottoms: harmonicity and synchronicity force the troughs of the whole cycle stack to land together, while crests never stack. Bottoms come as a nest of lows — sharp, deep, well timed. Tops come as a negotiation — rounded, staggered, smeared across sub-peaks. I cover that asymmetry fully in why bottoms form faster than tops.

Two working consequences follow directly:

1. Phasing runs on lows. Troughs are the pinned reference points; highs are the thing translation smears. In this method you count troughs, never peaks.
2. Real-time top-calling is inherently loose. You can time a bottom tightly. A top you can only bracket while it forms.

How do we actually use translation?

Four ways, in rough order of how often they earn their keep:

1. As a trend read you don't have to compute. The trend under any cycle is the sum of all longer cycles, and the longest of them can't be phased. Observed translation is one of the few direct reports on that hidden sum — read alongside the run of successive highs and lows, and whether the larger FLD objectives keep getting met.
2. As an error detector — the most sensitive one there is. Forecast the translation your trend read implies, then compare it to what prints. A peak that translates against forecast is the most sensitive tell of a phasing or trend error in the whole method. Expected a late peak and got an early one? Something upstream is wrong — recheck the analysis before trusting the next projection.
3. As an expectation-setter for projections. Whether an FLD objective tends to be overshot, undershot, or just met is decided by the short-term trend — the sum of the two next-longer cycles. Trend with the move, expect overshoot; trend against it, expect undershoot. Translation is the visible face of that same trend. The mechanics live in FLD crossings.
4. As a forecast of the cycle's second act. The M's second half can be read ahead of time from how the first half's projections resolve. When upward projections keep falling short, the span is telling you its second leg will fail — an early-peak, left-translated shape in the making. When they keep overshooting, the taller second hump is the likelier shape.

The same information also arrives letter by letter through the eight FLD interactions — each interaction's overshoot or undershoot is one more vote on which way the span is translating.

What does a translating top look like on a live tape?

Tops smear. Here's a dated example from my own ledger — scored afterward, like everything I say on video:

July 9, 2026 — scored a hit. On the show I said the 80-day cycle was "now probably peaking," with long-term buyers still trying to hold the market up — and that it was "definitely not going to work out for them." What followed was textbook top behavior: the S&P printed a marginal higher high the next session, drifted, printed another marginal high four sessions later, then rolled over. Within about a week it was trading below the level where the call was made. A hit in the ledger — and notice the shape: two shallow sub-peaks days apart, exactly the smeared, negotiated top that translation describes. Nobody rings a bell at a cycle peak. The peak argues with you first.

What can't translation do?

I'd rather state the limits out loud than have you discover them with money on the line.

• It's a lean, not a trigger. Translation tells you which way the tide is pulling. It doesn't time anything by itself.
• It confirms late. You only know a peak's true position once the following trough closes the span. In real time you're estimating, and revising.
• Tops are genuinely ambiguous while they form. Sub-peaks mean "the" peak may not be identifiable until well after the fact.
• It's a tendency. The principle of variation runs through all of this: strong tendencies, not laws. Nothing here is guaranteed — we never guarantee outcomes — and a cleanly translated span can still be followed by a cycle that does something else entirely.

The full stack this sits inside — phasing, FLDs, projections, trend — is laid out in the methodology hub.

Questions traders ask

Is a right-translated cycle proof that the next cycle will be bullish?

No. Translation reads the tide that existed during the span just completed. Larger cycles turn too — the tide itself rolls over on its own schedule — so each new cycle gets read fresh. Treat translation as the latest measurement of trend, not a promise about the future; we never guarantee outcomes.

Can translation be measured as a precise number?

In principle it's just peak position versus the span's midpoint. In practice, highs split into sub-peaks and drift, so the measurement is a lean — early, late, or roughly central — not a decimal. Lows are the precise reference points in this method, which is exactly why phasing counts troughs instead of peaks.

Is translation the same thing as a short or long cycle?

Related, not identical. Duration measures how long the span ran, trough to trough; translation measures where the peak sat inside it. The book's tendency is that 80-day cycles running under about 68 days lean bullish while those stretching 75 to 80 days lean bearish — both readings are downstream of the same larger-cycle trend, but you take them separately.

Which cycle should translation be read on?

Whichever cycle you're analyzing — the peak position of any span reads the sum of everything larger than it. In our work the 80-day cycle is the workhorse, so its M-shape is the read we come back to every couple of months, checked leg by leg against the two 40-day cycles inside it.

Keep reading