United Kingdom, March 2027: Saturn–Moon opposition on the national chart.

The UK national chart's single highest-lift signal — Saturn opposing the natal Moon at 4.21× — fires in March 2027, during a Saturn mahadasha and Saturn antardasha. The same configuration produced the Brexit vote and Queen Elizabeth II's death. The doubled dasha layer adds resonance.

The window

Between December 2026 and June 2027, the UK national chart enters a Saturn–Moon opposition window. Saturn moves into transit opposition with the natal Moon position. The window centers on March 2027.

This signal is the UK chart's highest-lift signature — 4.21× across the calibration dataset. No other signal on the UK chart approaches it. The dasha layer compounds: Saturn mahadasha is active, with Saturn antardasha within. The period lord doubles the resonance — Saturn pressure on the Moon comes during a Saturn-themed life period for the chart.

The signal, in plain terms

The Moon in a national chart represents the public, the body politic, the felt mood of the country. Saturn represents weight, structure, accountability, and the slow-burn arrival of consequence. Saturn opposing the Moon is the configuration the Vedic tradition reads as the public confronting structural pressure — accumulated weight that finally arrives.

Saturn–Moon opposition is one of the slow-cycle configurations: Saturn takes about 29.5 years to complete a full zodiac cycle, so it returns to opposition with any natal Moon position roughly once every 29.5 years. Each return brings a re-encounter with the same set of structural questions, against a different historical context.

When the chart's running mahadasha is also Saturn, the period lord adds another layer of the same theme. The framework reads doubly-Saturn-active windows as periods where decisions deferred over many years are forced into the open.

The math

Lift ratio

The Saturn–Moon opposition has a 4.21× lift on the UK chart. This is the second-highest single-signal lift in the entire Tempora library across all six national charts — exceeded only by Russia's Mars–Rahu (5.46×). The signal is sharp.

The Jupiter vedha (afflicting aspect) provides a secondary signature in the same window, though without a published numerical lift in the calibration. Combined with the Saturn–Saturn dasha layer, the window registers as High confidence — the strongest tier issued for the UK chart in the 2026–2030 scan.

Backtest precedent

The previous Saturn–Moon opposition cycle on the UK chart coincided with two events of national consequence:

• The Brexit referendum (June 2016) and its constitutional aftermath. Structural rupture in the UK's relationship with a multi-decade institutional arrangement. The vote itself fell within the Saturn–Moon active window.
• Queen Elizabeth II's death (September 2022) and the leadership transition. Symbolic and constitutional event of national scope. Falls within the closing tail of the same Saturn–Moon cycle's broader influence period.

The 2027 return is the next iteration of this slow cycle. The dasha layer (Saturn–Saturn) is more concentrated than the prior cycle's dasha alignment — Tempora's framework reads this as a configuration of comparable structural weight, possibly sharper given the doubled period lord.

The atomic claim

UK calibrated lift ratios — in context

Historical events on the Saturn–Moon cycle

The forward call

We expect — and publicly commit to scoring — that the United Kingdom experiences a constitutional, leadership, or major policy event between December 2026 and June 2027. The event:

• Has national consequence (visible across UK media within days; not a regional or partisan-only development)
• Falls into at least one of: a constitutional shift (devolution, succession, or multi-nation arrangement change), a leadership transition (PM, monarch, or major opposition leader), or a major policy event (economic, security, or institutional restructuring of national reach)
• Carries structural weight comparable to the Brexit or Queen's-death precedents — not a routine event of the news cycle

Falsifier — what would prove this wrong

1. No qualifying event occurs within ±90 days of March 15, 2027. The window passes quietly.
2. Events that occur are routine — pre-scheduled elections without major upset, planned diplomatic events, or continuations of trends already public at time of publication (May 2026).
3. Events occur but are partisan-only or regional-only, without national-level structural consequence.

What to watch — the calendar

Disclaimer This research is published for informational and educational purposes only. Temporal pattern analysis is not a guarantee of future political, constitutional, or economic outcomes. Planetary cycle correlations are statistical observations derived from historical data — they describe tendencies, not certainties. No commercial, political, financial, or personal action should be taken based solely on the contents of this article. Tempora Research holds no political affiliation and makes no endorsement of any party, government, or outcome. The probabilistic ranges presented are model outputs calibrated against a limited historical event set per national chart; the UK calibration relies on a single prior Saturn–Moon opposition cycle within the 30-year backtest window. Past patterns are not guaranteed to repeat. Event dates and historical occurrences cited are from publicly available sources.

Dasha-math correction — Saturn mahadasha was Mercury mahadasha

This section is a methodology revision, not a result update. The forward call's evaluation date (June 2027) has not arrived; nothing in the call has been falsified by outcome. What has happened is a Tier 1 forward-call audit, run 5 May 2026 in the wake of the article 052 Bengal post-mortem, which compared every live forward call's cited dasha state against the Tempora canonical computation stack. The audit found that the dasha state cited in Section 1 of this article does not match the canonical computation. This Section 2 documents the divergence, re-derives what the call rests on under the corrected reading, and states what changes — and what does not.

The audit context

The article 052 Bengal 2026 post-mortem (published 5 May 2026, within 24 hours of the counting-day result) named two specific errors that produced the failed call. The first was wrong dasha computation for both principals: Mamata Banerjee's Saturn mahadasha had ended fourteen months before the vote, and Modi was in Rahu mahadasha rather than Mars. The dasha math was not a methodology dispute; it was a calculation that did not reach the actual mahadasha boundary against the canonical natal data computed through Swiss Ephemeris with the PVRN Rao True Pushya Paksha ayanamsha. The Bengal failure prompted a corpus-wide audit of every live forward call against the same canonical stack.

That audit (workings file: forward_calls_audit_verdict_2026_05_05.md) flagged four Tempora articles in the same family of error — articles 054, 055, 056, 057 — where the article's cited dasha state diverges from the canonical computation. This article (056) is one of the four. The same diagnostic that resolved the Bengal failure was run against the UK 1801 chart for the article's target window (March 2027); the result is recorded below.

The divergence

The chart and the ayanamsha both match. The divergence is in the dasha state at the target window. Section 1's central rule — "Saturn mahadasha is active, with Saturn antardasha within. The period lord doubles the resonance — Saturn pressure on the Moon comes during a Saturn-themed life period for the chart" — does not survive contact with the canonical computation. Mercury mahadasha is running in March 2027 on the canonical UK chart.

What collapses, what stands

The article's load-bearing claims separate cleanly into two categories. The dasha-amplification half does not survive the correction; the transit-geometry half does.

Stands — the Saturn–Moon opposition transit signal itself. Saturn's transit position relative to the UK 1801 natal Moon is a positional fact computable from any sidereal stack against the canonical UK natal data. The orb timeline in Section 1 (window opens December 2026 as Saturn enters orb of opposition; exact mid-March 2027; window closes June 2027 as Saturn separates) is independent of which Vimshottari mahadasha is running — the transit is still scheduled, on the same dates, with the same configuration. The published call window (December 2026 – June 2027) and the falsifier conditions (no qualifying event ±90 days of 15 March 2027; routine-only events; partisan-only or regional-only events) carry through.

Stands — the historical analogues. The 2016 Brexit and 2022 Queen Elizabeth II events occurred during prior Saturn-transit aspects to the UK 1801 natal Moon. That is a positional record, not a dasha record. The analogues remain visible to the same transit-geometry argument. What the analogues no longer support is the specific claim that the prior cycle's outcomes were "Saturn-Moon opposition transit amplified by an active Saturn dasha state." The dasha state at Brexit (June 2016) and at QEII's death (September 2022) needs to be re-verified against the canonical UK 1801 chart before the historical pattern can be re-used as a dasha-stacked precedent. Pending that recomputation, the analogues stand only at the transit-geometry level.

Retires — the "doubly resonant Saturn period" framing. Section 1's central explanatory mechanism was that Saturn-on-Moon as a transit configuration was being amplified by a chart running Saturn mahadasha and Saturn antardasha simultaneously. This framing rests on the dasha state Section 1 claimed. With the canonical computation returning Mercury mahadasha at the target window, the "doubly resonant" reading is structurally inapplicable. There is no Saturn-period background against which the Saturn-on-Moon transit lands.

Carries a calibration-revision note — the 4.21× lift figure. The 4.21× lift was calibrated against the Saturn-Moon opposition cycle as a transit signal, with the two named precedents (Brexit 2016 and QEII transition 2022) inside the prior cycle. The lift is a transit-only number in its construction and therefore does not directly depend on the dasha state being claimed for March 2027. However, if the dasha states at the calibration events (June 2016, September 2022) were also computed against a non-canonical UK chart or by manual estimate — the same failure mode that produced the wrong March 2027 dasha — then the calibration's interpretation may have implicitly leaned on a wrong-dasha amplification at those prior events. The 4.21× number is preserved as published, with a flag: the calibration's dasha-overlay component requires recomputation against the canonical UK 1801 chart before being relied on as a stacked-amplification figure. As a transit-only figure, it stands.

What Mercury mahadasha activates on the UK 1801 chart

The structural reason this matters is that Mercury and Saturn rule different houses, in any chart, for any given lagna. A mahadasha is a multi-year activation of the houses ruled by the dasha lord. Saturn mahadasha would have activated the houses Saturn rules from the UK 1801 lagna; Mercury mahadasha activates the houses Mercury rules from that same lagna. The two are not interchangeable. Section 1's reading of the period as a "Saturn-themed life period for the chart" pulls from Saturn's lordship of structure, accountability, and slow-burn arrival of consequence on the UK chart. Mercury's lordship — wherever it falls — pulls from a different domain (communication, treaties, intermediaries, intellect-and-policy), which produces a different background reading for the same March 2027 transit window.

The full functional-lordship analysis under the canonical UK 1801 lagna is owed as a follow-up workings file. The interim point is the one Section 1 made implicitly and which the audit makes explicit: dasha state is load-bearing for any reading that claims a planet's life-period theme amplifies a planet's transit signal. The two need to be the same planet for the amplification to apply. Saturn-Moon-transit-during-Saturn-mahadasha is one configuration. Saturn-Moon-transit-during-Mercury-mahadasha is a different configuration with a different reading.

What this means for the forward call

The call stays live in the tracker. The transit signal — Saturn opposing the UK 1801 natal Moon, exact mid-March 2027, orb window December 2026 to June 2027 — is unchanged. The falsifier conditions in Section 1 are unchanged. The window dates are unchanged. The recommendation to score the call against a UK constitutional, leadership, or major policy event of national consequence in that window is unchanged.

What changes is the explanatory frame. The article will no longer be defended on the basis that a Saturn-themed mahadasha is amplifying a Saturn-on-Moon transit. The defence is narrower: the transit itself, calibrated against the prior cycle, is the signal. The dasha layer is Mercury, not Saturn, and the article's "doubly resonant" claim is retired pending the functional-lordship analysis owed above. If the call hits at evaluation date, it hits as a transit-geometry call rather than a dasha-stacked call. If it misses, the miss is informative for the transit-only signal independently of the (now-corrected) dasha context.

The corpus context — Bengal cascade

The Bengal 2026 failure (article 052) named manual-dasha-computation-without-canonical-stack-verification as one of the two errors that produced the wrong call. The Tier 1 audit confirmed this is a corpus-level pattern: it appears in articles 054 (Russia), 055 (US antardasha), 056 (this article — UK), and 057 (China). All four use the same Note #006 methodology and were drafted in the same batch (3 May 2026), before the canonical-stack discipline was formalised post-Bengal in docs/principles/canonical_charts.md on 5 May 2026.

This article's Section 2 is the second of three Section 2 methodology revisions resulting from the audit. Article 057 (China) and article 055 (US) carry their own Section 2 reconciliations on the same pattern. Each documents its specific divergence, re-derives the call's load-bearing components, and states what stands and what retires. The work is computation hygiene, not analytical disagreement — the fix is "compute against the canonical stack before publishing the analysis," and the discipline applies retrospectively to the live calls drafted before the discipline was formalised.

Recommendation

References (Section 2)

• Tier 1 forward-call audit verdict — forward_calls_audit_verdict_2026_05_05.md (5 May 2026)
• Article 052 Bengal post-mortem — Section 2 of article 052 (the failure that prompted the audit)
• Canonical-charts decision-of-record — docs/principles/canonical_charts.md (5 May 2026)
• UK 1801 canonical natal — tools/natals/uk_1801.json