China, September 2028: Saturn approaches the natal Moon.

Saturn approaches conjunction with China's natal Moon in Scorpio in September 2028 — the only positively-calibrated signal on China's chart in our scan. Lift is 2.07×. The two prior occurrences in our backtest were the 2008 Sichuan earthquake and the 2020 Wuhan lockdown. The sample is small. We say so.

The window

Between June 2028 and December 2028, the China national chart sees Saturn approach within orb of conjunction with the natal Moon position in Scorpio. The window centers on September 2028.

Of the nine signatures Tempora calibrates per chart, only one shows positive lift on the China backtest: Saturn-near-Moon. The remaining eight signatures either show no signal or have insufficient sample to calibrate. The call rests entirely on this single signature.

The signal, in plain terms

Saturn passing across or near a natal Moon position is the slow-cycle signature the Vedic tradition reads as the body politic encountering structural weight. For India and the US the same configuration appears among multiple signals. For China it stands alone. The chart's other natal placements have not produced enough events in our backtest window to calibrate independently.

Saturn returns to any given natal Moon position roughly every 29.5 years and approaches conjunction (within 6° orb) once every cycle. The 2028 window is the next such conjunction since the prior cycle.

The math

Lift ratio

Saturn-near-Moon has a 2.07× lift on the China chart — the only signal with positive empirical lift in the calibration. Mid-range relative to the broader Tempora signal library (Russia 5.46× and UK 4.21× are sharper; India 1.88× and Pakistan 2.51× are comparable).

Confidence tier: Moderate. The signal is sharp but the base rate of events to test against is the limit.

Backtest precedent

Two events in the China backtest fall within active Saturn-near-Moon windows. Both are large-magnitude events with national consequence:

• May 2008 — Sichuan earthquake. A natural event with national-scale humanitarian and infrastructure consequence. Saturn was within orb of natal Moon during the active period.
• January–March 2020 — Wuhan lockdown and the COVID outbreak's first phase. A health-policy-economic event of unprecedented domestic and international scale. Saturn proximity to natal Moon was active.

The 2028 window is the next return of this slow-cycle configuration. The two precedents are not predictive of the kind of event — one is geological, one epidemiological — but they share the structural feature of being large-magnitude unanticipated events that pressed against the chart's Moon position.

The atomic claim

China calibrated lift ratios — in context

Historical events on the Saturn–Moon proximity

The forward call

We expect — and publicly commit to scoring — that China experiences a significant internal or external event between June 2028 and December 2028. The event:

• Has national consequence (visible across Chinese state media within days; not a regional or municipal-only development)
• Falls into at least one of: an economic disclosure of national reach (slowdown announcement, financial-system stress, currency action), a territorial action (border, maritime, or cross-strait posture change), a leadership succession or major personnel event, or a major foreign-relations shift
• OR — alternative qualifier — a natural or public-health event of national-scale consequence (consistent with both 2008 and 2020 precedents)

Falsifier — what would prove this wrong

1. No qualifying event occurs within ±90 days of September 15, 2028. The window passes quietly.
2. Events that occur are routine — pre-announced policy implementations, scheduled diplomatic events, or continuations of trends already in public view at time of publication (May 2026).
3. Events occur but are local-only, without national-level consequence visible across state media.

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, economic, security, or natural-event outcomes. Planetary cycle correlations are statistical observations derived from historical data — they describe tendencies, not certainties. No commercial, political, financial, security, 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 state, government, or outcome. The probabilistic ranges presented are model outputs calibrated against a limited historical event set per national chart; the China calibration is explicitly small (N=4) and the call carries a corresponding caveat surfaced in the article body. Past patterns are not guaranteed to repeat. Event dates and historical occurrences cited are from publicly available sources.

Dasha-math correction — Rahu mahadasha was Mercury mahadasha

This section is a methodology revision, not a result update. The forward call's evaluation date (December 2028) 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 (057) is one of the four. The same diagnostic that resolved the Bengal failure was run against the PRC 1949 chart for the article's target window (September 2028); the result is recorded below.

The divergence

The chart, the ayanamsha, and the house system all match. The divergence is in the dasha state at the target window. Section 1's atomic claim — "Active dasha: Rahu mahadasha · Jupiter antardasha" — does not survive contact with the canonical computation. Mercury mahadasha is running in September 2028 on the canonical PRC 1949 chart.

What collapses, what stands

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

Stands — the Saturn-conjunct-natal-Moon transit signal itself. Saturn's transit position relative to the PRC 1949 natal Moon in Scorpio is a positional fact computable from any sidereal stack against the canonical PRC natal data. The orb timeline in Section 1 (window opens June 2028 as Saturn enters orb; closest conjunction mid-September 2028; window closes December 2028 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 (June 2028 – December 2028) and the falsifier conditions (no qualifying event ±90 days of 15 September 2028; routine-only events; local-only events without national consequence) carry through.

Stands — the historical analogues at the transit-geometry level. The 2008 Sichuan earthquake and the 2020 Wuhan lockdown occurred during prior Saturn-transit aspects to the PRC 1949 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 underwrite is any specific claim about the prior cycle's dasha overlay. The dasha state at May 2008 (Sichuan) and at January–March 2020 (Wuhan) needs to be re-verified against the canonical PRC 1949 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 Rahu-mahadasha · Jupiter-antardasha dasha-context framing. The atomic-claim block in Section 1 cited "Rahu mahadasha · Jupiter antardasha" as part of the active configuration at the target window. With the canonical computation returning Mercury mahadasha, that framing is structurally inapplicable. There is no Rahu-period background, and no Jupiter sub-period within Rahu, against which the Saturn-on-Moon transit lands. Any reading that leaned on Rahu-Jupiter symbolism (foreign exposure, expansive ambition under disruption, Jupiter as benefic moderator within a Rahu node-period) is retired pending the corrected Mercury-mahadasha analysis owed below.

Retires — the article's atomic-claim phrasing. The atomic-claim block in Section 1 reads: "Active dasha: Rahu mahadasha · Jupiter antardasha. Confidence tier: Moderate, with explicit small-sample caveat." The dasha clause is wrong against the canonical computation. The atomic-claim phrasing does not carry forward as a defendable summary of the call. The call's defendable summary is now narrower: the Saturn-near-Moon transit window centered September 2028, lift 2.07× (with the calibration-revision note below), confidence tier Moderate with explicit small-sample caveat — without dasha-context overlay until the canonical Mercury-mahadasha analysis is filed.

Carries a calibration-revision note — the 2.07× lift figure. The 2.07× lift was calibrated against the Saturn-near-Moon configuration as a transit signal, with the two named precedents (Sichuan 2008 and Wuhan 2020) as the calibration's positive events. The lift is a transit-only number in its construction and therefore does not directly depend on the dasha state being claimed for September 2028. However, if the dasha states at the calibration events (May 2008, January–March 2020) were also computed against a non-canonical PRC chart or by manual estimate — the same failure mode that produced the wrong September 2028 dasha — then the calibration's interpretation may have implicitly leaned on a wrong-dasha context at those prior events. The 2.07× number is preserved as published, with a flag: the calibration's dasha-overlay component requires recomputation against the canonical PRC 1949 chart before it can be relied on as a dasha-stacked figure. As a transit-only figure on an N=4 calibration, the figure is unchanged but inherits the small-sample caveat already surfaced in Section 1, and now additionally inherits the dasha-recomputation flag.

What Mercury mahadasha activates on the PRC 1949 chart

The structural reason this matters is that Mercury and Rahu rule different houses — and signify different domains — in any chart, for any given lagna. A mahadasha is a multi-year activation of the houses ruled by the dasha lord (and, for the nodes Rahu and Ketu, of the houses they occupy and aspect, since the nodes have no rulership). Rahu mahadasha would have activated PRC's foreign-affairs / boundary-disruption / amplified-ambition signatures via Rahu's positional placement on the chart; Mercury mahadasha activates the houses Mercury rules from the PRC 1949 lagna, which is a different domain (commerce, treaties, communication, intermediaries, intellect-and-policy, neighbouring-relations).

The Section 1 body cites the natal Moon in Scorpio as part of the article's geometric reading — that is preserved as positional fact and is the load-bearing element of the transit signal. What was implicit and is now retired is any reading that paired the Saturn-on-Moon transit with a Rahu-Jupiter dasha overlay. The full functional-lordship analysis of Mercury under the canonical PRC 1949 lagna (computed at 15:01 CST in Beijing under True Pushya Paksha ayanamsha) 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 contextualises a planet's transit signal. The two need to be the correctly-computed planet for the contextualisation to apply. Saturn-Moon-conjunction-during-Rahu-mahadasha is one configuration. Saturn-Moon-conjunction-during-Mercury-mahadasha is a different configuration with a different background reading.

What this means for the forward call

The call stays live in the tracker. The transit signal — Saturn approaching conjunction with the PRC 1949 natal Moon in Scorpio, closest mid-September 2028, orb window June 2028 to December 2028 — is unchanged. The falsifier conditions in Section 1 are unchanged. The window dates are unchanged. The recommendation to score the call against a Chinese national-consequence event in that window is unchanged.

What changes is the explanatory frame. The article will no longer be defended on the basis that a Rahu mahadasha and Jupiter antardasha provide the dasha context for the Saturn-on-Moon transit. The defence is narrower: the transit itself, calibrated against the prior cycle (Sichuan 2008 + Wuhan 2020) on an N=4 dataset, is the signal. The dasha layer is Mercury, not Rahu, and the article's "Rahu mahadasha · Jupiter antardasha" claim is retired pending the functional-lordship analysis owed above. The "single positively-calibrated signal on China's chart" framing in Section 1 itself depended partly on the dasha-context overlay; with that overlay now flagged, the framing tightens to "single positively-calibrated transit signal on the PRC 1949 chart, on a small N=4 calibration, without dasha-context underwriting until recomputed." If the call hits at evaluation date, it hits as a transit-geometry call on a small calibration 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 052 (Bengal — Mamata and Modi), 056 (UK — Saturn mahadasha that should have been Mercury), 057 (this article — Rahu mahadasha that should have been Mercury), and 055 (US — partial cascade on the antardasha layer). 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 one of three Section 2 methodology revisions resulting from the audit, alongside article 056 (UK) and article 055 (US). 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)
• Article 056 UK Section 2 — UK Mercury-mahadasha reconciliation (sibling correction in the same audit batch)
• Canonical-charts decision-of-record — docs/principles/canonical_charts.md (5 May 2026)
• PRC 1949 canonical natal — tools/natals/prc_1949.json