United States, November 2029: a three-signal convergence on the Gemini stellium.

Three of the US Independence chart's five validated signals fire simultaneously in November 2029 — the highest multi-signal convergence for any US window in the 2026–2030 scan. The previous Rahu-in-Gemini transit produced 9/11. This is the 18.6-year return.

The window

Between September 2029 and March 2030, the US Independence chart (4 July 1776, Sibly convention) enters its strongest forward window of the 2026–2030 scan period. The window centers on November 2029.

The US natal chart contains four planets in Gemini — Sun, Mars, Jupiter, Venus — a powerful stellium. When Rahu or Ketu transits this sign, the chart's core tension activates. Mid-2028, Rahu moves into Sagittarius, placing Ketu in Gemini directly over the natal stellium. The transit persists approximately 18 months. By November 2029, additional malefic configuration develops in Sagittarius (opposing the Gemini stellium) while Saturn approaches the natal Moon's vicinity. Three of the five US-validated signals fire simultaneously.

The Venus mahadasha–Rahu antardasha–Mars pratyantara active during this window adds resonance: Venus rules the 5th and 12th from the natal chart, and Rahu sits conjunct natal Venus natally — a charged period lord activating its own placement.

The signal, in plain terms

The US chart's Gemini stellium is its dominant sensitive cluster. The Vedic tradition reads the lunar nodes — Rahu and Ketu — as the most disruptive transit influences. They move retrograde through the zodiac on an 18.6-year cycle, returning to any given sign roughly once every 19 years.

When Ketu transits over a stellium, the tradition reads the configuration as forced re-examination of foundational themes. When Rahu transits the opposite sign at the same time (which it does by definition — they are 180° apart), the axis activates from both ends. When malefic transits arrive on the opposite arm and the Moon's natal placement also receives Saturn pressure in the same window, three independent signals converge.

The 18.6-year period is the cycle that returns Rahu to its starting position. The November 2029 window is roughly 18.6 years after the closing edge of the prior Rahu-in-Gemini transit (2001–2003), which produced 9/11 (September 2001) at its opening. The framework reads the upcoming window as the next return of that nodal pattern.

The math

Lift ratios

Three signatures fire in this window with calibrated lifts:

• Rahu/Ketu over stellium — 2.45× lift. The dominant signal for the US chart.
• Malefic opposition to stellium — 2.42× lift. Activates from the opposite arm in late 2029.
• Saturn near natal Moon — 2.20× lift. Adds a third independent configuration in the same window.

Mean lift across the three: 2.36×. None individually as sharp as Russia's 5.46× headline signal, but the simultaneous fire of three independent configurations is the rare event. For the 2026–2030 US scan period, no other window produces this level of multi-signal convergence.

Backtest precedent

The clearest historical analogue is the 2001–2003 Rahu-in-Gemini transit. The opening edge of that transit window saw the September 11 attacks. The closing edge produced the early Iraq War period. Both fall within an active Ketu-over-Gemini-stellium window, though calibrated against the prior nodal cycle.

The 2029 window adds the malefic opposition (lift 2.42×) and the Saturn-Moon proximity (lift 2.20×) — neither was firing as strongly in 2001. The 2029 configuration is the first three-signal convergence on this chart in the 30-year calibration dataset.

The atomic claim

US calibrated lift ratios — in context

The US window's strength is not in any single high-lift number but in the rarity of three independent signals firing together. In the 30-year calibration window, this combination has occurred zero prior times for the US chart.

Historical events on the Gemini stellium

The forward call

We expect — and publicly commit to scoring — that the United States experiences a significant political, economic, or security event between September 2029 and March 2030. The event:

• Has international ramifications, not solely domestic
• Is sudden in form (consistent with nodal-axis activation patterns) rather than gradual
• Falls into at least one of: a security event (military, intelligence, or homeland), a political shift (constitutional, leadership transition, or major policy reorientation), or an economic event (financial system, currency, or major regulatory shift of national-international reach)

Falsifier — what would prove this wrong

1. No qualifying event occurs within ±90 days of November 30, 2029. The window passes quietly.
2. Events that occur are gradual, predictable continuations of trends already in public view at time of publication (May 2026).
3. Events occur but are domestic-only, without measurable international 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, security, or economic 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, party, or outcome. The probabilistic ranges presented are model outputs calibrated against a limited historical event set per national chart. Past patterns are not guaranteed to repeat. The US Sibly chart used here is the standard scholarly convention but not the only chart used in the field; readers should weight the call accordingly. Event dates and historical occurrences cited are from publicly available sources.

Dasha-math correction — Rahu antardasha was Jupiter antardasha

This section is a methodology revision, not a result update. The forward call's evaluation date (March 2030) 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 antardasha 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 (055) is one of the four, and is the third Bengal-cascade reconciliation in the corpus alongside article 056 (UK) and article 057 (China). The same diagnostic that resolved the Bengal failure was run against the USA Sibly 1776 chart for the article's target window (November 2029); the result is recorded below. This article's case is distinct from 056 and 057 in one respect: the cascade is partial. The mahadasha is correct against canonical computation; the antardasha within it is not. The error reaches one level deeper than the mahadasha layer rather than at it.

The divergence

The chart, the ayanamsha, the house system, and the mahadasha all match the canonical computation. The divergence is at the antardasha layer: the canonical sub-period running on the Venus mahadasha at November 2029 is Jupiter, not Rahu. Section 1's atomic claim — "Active dasha: Venus mahadasha · Rahu antardasha · Mars pratyantara" — does not survive contact with the canonical computation at the antardasha level. The Venus mahadasha context is correct; the Rahu antardasha within it is not.

What collapses, what stands

The article's load-bearing claims separate cleanly. The transit-geometry argument is independent of the dasha state and survives intact. The dasha-context overlay that paired the Rahu antardasha with the natal Venus position does not survive.

Stands — the three-signal stellium-axis transit signature. The three transit signals at the centre of Section 1's argument are positional facts computable from any sidereal stack against the canonical USA Sibly natal data: Ketu's transit over the Gemini stellium (lift 2.45×), malefic opposition to the Gemini stellium from Sagittarius (lift 2.42×), and Saturn's approach to the natal Moon's vicinity (lift 2.20×). The orb timeline in Section 1 — window opens September 2029, three-signal convergence peaks November 2029, window closes March 2030 — is unchanged by the antardasha correction. The transit configurations are still scheduled, on the same dates, with the same geometry. The published call window (September 2029 – March 2030) and the falsifier conditions (no qualifying event ±90 days of 30 November 2029; gradual-trend events; domestic-only events without international consequence) carry through.

Stands — the "first three-signal convergence in 30-year calibration" claim. The novelty of three independent calibrated signals firing simultaneously on the USA Sibly chart in the 30-year backtest window is a count of transit-geometry events, not a count of dasha-state events. The claim is geometrically correct independent of which Vimshottari sub-period is running. The article's structural argument that this is the strongest multi-signal forward window for any US window in the 2026–2030 scan stands on its own.

Stands — the Venus mahadasha context. Unlike the 056 and 057 reconciliations, where the mahadasha itself was wrong against canonical computation, the mahadasha layer here is correct. Venus is the active mahadasha lord on the canonical USA Sibly chart at November 2029. Any reading that depended on Venus's life-period theme contextualising the window — Venus's lordship of the 5th and 12th from the natal chart, Venus's natal placement in the Gemini stellium itself — survives the audit. The mahadasha-level frame is intact.

Retires — the Rahu-AD-conjunct-natal-Venus dasha-amplification mechanism. Section 1's mechanism note read: "Venus rules the 5th and 12th from the natal chart, and Rahu sits conjunct natal Venus natally — a charged period lord activating its own placement." This sentence is the load-bearing piece of dasha-amplification reasoning the article offered: Rahu (the antardasha lord) sitting natally conjunct Venus (the mahadasha lord) was framed as the charged sub-lord activating the period lord's own placement. With the canonical computation returning Jupiter as the active antardasha, this mechanism is structurally inapplicable. Rahu is not the active sub-lord at the November 2029 target window; the "Rahu activates Venus's own placement" framing collapses entirely. The mechanism note is retired.

Retires — the Section 1 atomic-claim phrasing at the antardasha level. The atomic-claim block reads: "Active dasha: Venus mahadasha · Rahu antardasha · Mars pratyantara." The mahadasha clause is correct; the antardasha clause is wrong against canonical computation; the pratyantara clause was nested inside the wrong antardasha and is structurally inapplicable as written. The defendable summary of the call is now narrower at the dasha-context layer: Venus mahadasha context (correct), with the Venus–Jupiter sub-period running at the target window as the canonical antardasha context, and pratyantara not separately verified pending recomputation against engine/dasha.py.

Carries a calibration-revision note — the three lift figures and their 2.36× mean. The three lifts (Ketu over stellium 2.45×, malefic opposition 2.42×, Saturn near Moon 2.20×, mean 2.36×) were calibrated against the prior backtest precedents Section 1 names: 9/11 (September 2001) and the Iraq War opening (2003). These calibrations are transit-only numbers in their construction and therefore do not directly depend on the antardasha state being claimed for November 2029. However, if the dasha states at the calibration events (September 2001, March 2003) were also computed against a non-canonical USA chart or by manual estimate — the same failure mode that produced the wrong November 2029 antardasha — then any implicit dasha-overlay component of the calibration's interpretation may have leaned on a wrong-dasha context. The 2.45× / 2.42× / 2.20× figures and the 2.36× mean are preserved as published, with a flag: the historical analogue dasha states (9/11 in 2001, Iraq War opening in 2003) require re-verification against the canonical USA Sibly chart through engine/dasha.py before the calibration's dasha-overlay component can be relied on. As transit-only figures the lifts are intact; as dasha-stacked figures they inherit a recomputation flag and the small-N caveat already implicit in a 30-year calibration.

What Jupiter antardasha on Venus mahadasha activates

The structural reason this matters is that Jupiter and Rahu rule different houses — and signify different domains — in any chart, for any given lagna. An antardasha is a sub-period activation of the houses ruled or occupied by the sub-lord, layered on top of the houses activated by the mahadasha lord. Rahu antardasha on Venus mahadasha would have activated, on the canonical USA Sibly lagna, Rahu's positional placement and the house themes Rahu touches by occupation and aspect (the nodes have no rulership), within a Venus-themed life period — read conventionally as an "amplified-desire-period" overlay where node-disruption colours a Venus life-context. Jupiter antardasha on Venus mahadasha activates the houses Jupiter rules from the canonical USA Sibly lagna, which is a different domain (expansion, faith, fortune, foreign affairs, knowledge, judiciary, philosophy, treaties of the wisdom-and-sanction kind), within the same Venus-themed life-context.

Conventionally, Jupiter antardasha on Venus mahadasha is a benefic-on-benefic period — the two natural benefics layering, which the tradition reads as a generally favourable backdrop with the specific colouration depending on each planet's functional lordship and placement on the chart in question. This is a different signature from the Rahu-AD-on-Venus-MD "amplified-desire-period" reading Section 1 implicitly leaned on. Whether the Venus–Jupiter sub-period reads as smoothly benefic on the Sibly USA chart specifically — or whether Jupiter's functional lordship under the Sibly lagna pulls it into a more pressured reading — depends on Jupiter's house lordship and placement under the canonical 17:10 LMT Philadelphia chart, which has not been computed and recorded as part of this Section 2.

The full functional-lordship analysis of Jupiter under the canonical USA Sibly lagna is owed as a follow-up workings file, matching the handling adopted in articles 056 and 057. The interim point is the one Section 1 made implicitly and which the audit makes explicit: dasha state — at every level cited — is load-bearing for any reading that claims a planet's sub-period theme contextualises a planet's transit signal. The two need to be the correctly-computed planet for the contextualisation to apply. Saturn-near-Moon-during-Venus-MD-Rahu-AD is one configuration. Saturn-near-Moon-during-Venus-MD-Jupiter-AD is a different configuration with a different background reading. The same applies to Ketu-over-Gemini-stellium and the malefic opposition.

What this means for the forward call

The call stays live in the tracker. The chart-geometry signal — three independent calibrated transit configurations firing simultaneously on the canonical USA Sibly chart, peaking 30 November 2029, orb window September 2029 to March 2030 — fires positionally and is unchanged by the antardasha correction. The falsifier conditions in Section 1 are unchanged. The window dates are unchanged. The recommendation to score the call against a US political, economic, or security event of international consequence in that window is unchanged.

What changes is the dasha-context overlay. The article will no longer be defended on the basis that a Rahu antardasha sitting natally conjunct Venus charges the period lord's own placement. The defence is narrower at the dasha layer: the call's transit-based component — three independent signals at 2.45×, 2.42×, 2.20× (mean 2.36×), the first such convergence on the USA Sibly chart in the 30-year calibration — is the load-bearing argument. The Venus mahadasha frame (correct, intact) provides the life-period context. The Rahu-AD-amplification mechanism is retired pending the canonical Jupiter-AD functional-lordship analysis owed above. If the call hits at evaluation date, it hits as a transit-geometry call within a correctly-named Venus mahadasha rather than as a Rahu-AD-stacked call. If it misses, the miss is informative for the three-signal-convergence transit signature independently of the (now-corrected) antardasha 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 — both Mamata's Saturn MD and Modi's Mars MD wrong), 056 (UK — Saturn MD wrong, canonical Mercury MD), 057 (China — Rahu MD wrong, canonical Mercury MD), and this article 055 (US — MD correct, AD wrong: Rahu AD against canonical Jupiter AD). 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.

The error is consistent across the four cases: manual dasha estimation diverges from canonical computation. The depth of the divergence varies — 052, 056, and 057 have wrong mahadashas; 055 has a correct mahadasha with a wrong antardasha within it (the partial cascade). The fix is the same regardless of depth: declare the canonical chart in docs/principles/canonical_charts.md, compute the Vimshottari ladder via engine/dasha.py against the canonical natal data, and check the cited dasha state at every level (MD, AD, PD) before the analysis goes to publication. No manual estimates.

This article's Section 2 is the third of three Section 2 methodology revisions resulting from the audit, alongside article 056 (UK) and article 057 (China). 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)
• Article 057 China Section 2 — China Mercury-mahadasha reconciliation (sibling correction in the same audit batch)
• Canonical-charts decision-of-record — docs/principles/canonical_charts.md (5 May 2026)
• USA Sibly 1776 canonical natal — tools/natals/usa_1776.json