Validated Forward Predictions
Using calibrated, chart-specific weights derived from historical backtesting (Research Note #005), we scan six national founding charts for high-confluence windows from March 2026 to December 2030. We identify 12 prediction windows where historically validated signals simultaneously activate, specifically, where at least one signal with lift ≥ 1.5x fires. The most significant findings: India enters a critical window in December 2027 (Ketu over Cancer stellium + Mars–Rahu Angarak Yoga in Capricorn during Rahu–Rahu dasha); Russia shows peak vulnerability in February 2028 (Angarak Yoga at maximum + approaching Rahu return); and the US registers a multi-signal convergence in late 2029 (Ketu over Gemini stellium during Venus–Rahu mahadasha). The 2028–2029 period shows the strongest multi-nation simultaneous activation in our 50-year window, five of six charts register elevated confluence within an 18-month window.
1. Methodology
This note applies the calibrated scoring engine described in Research Note #005. Briefly: nine astrological signatures are scored against each country's natal chart using current planetary positions. Scores are weighted by empirically derived lift ratios (computed from 300+ historical and Monte Carlo data points). Windows where confluence ≥ 18% and at least one strong validated signature (lift ≥ 1.5x) fires are surfaced as predictions.
The scan uses 7-day steps from March 2026 to December 2030 per country. Overlapping windows within 45 days are deduplicated, retaining the highest-confluence date. This produces a clean, non-overlapping set of distinct prediction events.
A "prediction window" means: this is a period of elevated astrological tension for this chart. Historically, windows with similar confluence scores (same signatures at same intensities) have correlated with significant geopolitical events. We do not predict specific events. We predict that this is a window where events are more likely to occur. All predictions are publicly reconcilable: a window that passes without notable occurrence is a miss, recorded publicly.
2. India, December 2027
India's natal chart contains five planets in Cancer (Sun, Moon, Mercury, Venus, Saturn per engine recomputation; Mars sits in Gemini), the most concentrated stellium in any of the six charts we track. This stellium is the chart's dominant sensitive axis. Any malefic activation of the Cancer-Capricorn axis produces historically significant events. The original draft listed Mars in place of Saturn; corrected per Section 9 below.
In December 2027, two simultaneous activations occur: (1) Ketu moves into Cancer, placing it directly over the 5-planet stellium. Rahu simultaneously moves into Capricorn. (2) Mars forms a conjunction with Rahu in Capricorn, the Angarak Yoga, creating a malefic cluster directly opposite the Cancer stellium. The active dasha at this date is Mars mahadasha (28 January 2024 to 27 January 2031), Mercury antardasha (27 July 2027 to 23 July 2028), Sun pratyantara (6 December 2027 to 24 December 2027) per engine compute on the canonical India 1947 natal. The original draft of this note stated "Rahu–Rahu–Rahu" for this card; that attribution was a register-level error and is corrected below in Section 9.
This configuration is structurally similar to the 2019–2020 window (when Saturn entered Capricorn and the same axis activated), which produced the Pulwama attack (Feb 2019), Modi's re-election (May 2019), and the COVID lockdown (March 2020). The December 2027 window lacks Saturn in Capricorn but gains the Angarak Yoga and the Ketu stellium overlay, a different but comparably charged configuration.
- A major political, security or economic development occurs between 1 November 2027 and 28 February 2028
- India's relationship with a neighboring state or external power becomes publicly contested
- A significant domestic policy decision (constitutional, economic or military) is announced or enacted
3. Russia, February 2028
Russia's historical event signature is the most concentrated in our dataset: two signals account for virtually all historical event predictivity. The Mars–Rahu Angarak Yoga has a 5.46x lift, meaning it fires 5.46 times more frequently on confirmed historical crisis dates than on random dates. This is not a subtle signal.
The backtest coverage for Russia, after engine re-verification on 9 May 2026 (see Section 9), includes: the 2014 Maidan-to-Crimea sequence (Mars–Rahu within 4.27° to 4.47° at the 8° signature orb) and the 17 July 2014 MH17 shoot-down (Mars–Rahu within 1.86°). The 1998 financial default and the February 2022 invasion of Ukraine, both originally cited in this note, fall outside the 8° orb at engine separations of 33.76° and 123.91° respectively. Those two events have been retired from the named-precedent set per Note 005 Section 9. The 5.46x lift figure derives from the Monte Carlo distribution on the full historical event set, not from the named precedents in isolation.
In early-to-mid January 2028, Mars approaches its closest transit conjunction with Rahu, with the Angarak Yoga closing to roughly 1.0° on 6 January 2028 in Capricorn per engine compute. Mars then crosses into Aquarius and the separation widens through the rest of February (32.70° by 15 February, 36.91° by 20 February). The original draft stated the peak as "within 5° in February 2028"; engine returns the peak as 6 January 2028. The Rahu return, transit Rahu conjunct natal Rahu (Sagittarius 27.94° on the canonical 12 June 1991 chart), approaches the 8° orb in mid-March 2028 and reaches exact in mid-September 2028. The "approaches within 8° by mid-2028" framing in the original draft is engine-consistent at the rahu-return signal layer. The forward-call window remains open at the rahu-return layer through to the September 2028 exact point.
- A major Russian foreign policy action, military development, or internal political shift occurs between December 2027 and May 2028
- Russia's relationship with Europe, NATO or a CIS state becomes a global news story of significant consequence
- A sudden, unexpected development (not gradual) characterizes the event
4. United States, Late 2029
The US natal chart contains Sun, Mars, Jupiter and Venus in Gemini, a powerful 4-planet stellium. When Rahu or Ketu transits this sign, the chart's core tension activates. The last Rahu-in-Gemini transit occurred approximately 2001 (September 11 falls within this period). The nodal axis returns every 18.6 years.
In mid-2028, Rahu moves into Sagittarius, placing Ketu in Gemini, directly over the natal stellium. This transit persists approximately 18 months. By November 2029, additional malefic configuration develops in Sagittarius (opposing the stellium), while Saturn approaches the Moon's vicinity. Three of the five US-validated signals fire simultaneously, the highest multi-signal convergence for any US window in the 2026–2030 scan period.
The Venus mahadasha (12 April 2022 to 12 April 2042) and the Rahu antardasha (10 June 2029 to 9 June 2032) operating during this window add additional resonance: Venus rules key houses on the Sibly chart, and Rahu is natally placed in Cancer 17.98° (close to natal Venus Gemini 13.76°). The pratyantara active at 30 November 2029 is Jupiter (21 November 2029 to 16 April 2030) per engine compute on the canonical Sibly chart. The original draft stated "Mars (pratyantara)" for this window; that attribution does not match engine output and is corrected below in Section 9.
- The US experiences a significant political, economic or security event between September 2029 and March 2030
- The event involves a sudden shift rather than a gradual trend, consistent with nodal activation patterns
- The event has international ramifications, not solely domestic
5. UK, China, Pakistan
| Country | Window | Primary Signal | Lift | Secondary | Dasha (engine-corrected) |
|---|---|---|---|---|---|
| UK | Mar 2027 | saturn_moon_opposition | 4.21x | jupiter_vedha | Mercury MD, Saturn AD |
| China | Sep 2028 | saturn_near_moon | 2.07x | , | Mercury MD, Rahu AD |
| Pakistan | Oct 2026 | rahu_return | 2.51x | rahu_over_stellium | Moon MD, Mars AD |
| Pakistan | Jun 2028 | rahu_return | 2.51x | malefic_opp_stellium | Moon MD, Jupiter AD |
UK March 2027: Saturn moves into opposition with the UK chart's natal Moon (Libra). This is the UK's highest-lift signal (4.21x). The previous Saturn–Moon opposition correlates with the Brexit vote and Queen Elizabeth's death. The active dasha at March 2027 on the canonical UK 1801 chart is Mercury mahadasha (8 August 2012 to 8 August 2029), Saturn antardasha (25 November 2026 to 4 August 2029), Saturn pratyantara (25 November 2026 to 29 April 2027) per engine compute. The original draft stated "Saturn–Saturn" at the mahadasha–antardasha layer; engine returns Mercury MD with Saturn AD. The Saturn-on-Saturn pratyantara framing inside Mercury MD still produces a Saturn-resonant moment, but the mahadasha lord is Mercury, not Saturn. Section 9 documents the correction.
China September 2028: Saturn approaches natal Moon in Capricorn (PRC natal Moon = Capricorn 6.81° per engine; the original draft prose elsewhere references "natal Moon in Scorpio" which is inconsistent with the canonical 1 October 1949 15:01 CST chart). The active dasha at September 2028 is Mercury mahadasha (19 December 2018 to 19 December 2035), Rahu antardasha (13 June 2028 to 31 December 2030), Rahu pratyantara (13 June 2028 to 30 October 2028) per engine. The original draft stated "Rahu–Jupiter" at the mahadasha–antardasha layer; engine returns Mercury MD with Rahu AD.
Pakistan October 2026 & June 2028: Pakistan shows two Rahu-window-themed signals within the scan period. The Rahu return signature is engine-confirmed inside the 8° orb only at the second window (Imran ouster April 2022, separation 5.00°, was the prior cycle's confirmed activation). Of the four named precedents in the original draft (Zia 1988, Musharraf 1999, Bhutto 2007, Imran 2022), engine returns rahu-natal-rahu separations of 73.78°, 70.38°, 88.48°, and 5.00° respectively. Only Imran 2022 falls within the 8° orb. The 2.51x lift figure is preserved as a Monte Carlo output but the named-precedent prose requires re-verification per Note 005 Section 9 and Note 009 Section 8. The active dasha at October 2026 is Moon mahadasha, Mars antardasha (the Mars antardasha closes on 17 October 2026, so the back half of October 2026 transitions into Rahu antardasha). The active dasha at June 2028 is Moon mahadasha, Jupiter antardasha, Jupiter pratyantara per engine. The original draft stated "Moon–Saturn" for October 2026 and "Mars–Venus" for June 2028; engine returns Moon–Mars and Moon–Jupiter respectively.
6. The 2028–2029 Global Convergence
The most significant finding of this scan is not any individual country window, but the simultaneous activation of elevated windows across five of six charts in an 18-month period spanning late 2027 through mid-2029.
| Country | Peak Window | Dominant Signal | Confidence |
|---|---|---|---|
| India | Dec 2027 | malefic_opp_stellium + rahu_over_stellium | Moderate–High |
| UK | Mar 2027 | saturn_moon_opposition | High |
| Russia | Feb 2028 | mars_rahu_conjunction + rahu_return | Elevated |
| Pakistan | Jun 2028 | rahu_return + malefic_opp_stellium | Moderate |
| US | Nov 2029 | rahu_over_stellium + malefic_opp_stellium | Moderate–High |
| China | Sep 2028 | saturn_near_moon | Moderate |
Multi-nation simultaneous astrological tension has historically correlated with global-scale disruptions: both World Wars, the 2008 financial crisis, and the COVID pandemic all showed multi-chart simultaneous activation in our backtest data (though the backtest was not specifically calibrated for global convergence patterns).
The 2028–2029 window is unusual in that each chart's activation derives from different signals, this is not a single planetary transit (like a Saturn–Pluto conjunction) triggering all charts simultaneously. Each country's independent sensitive axis activates in the same 18-month period from different astrological causes. The convergence is structural, not coincidental.
Convergence of multiple national charts into elevated windows does not constitute a prediction of global catastrophe. Historically elevated windows have also coincided with transformative but non-catastrophic events: elections, major policy shifts, economic restructuring. The quality of the event is not predicted, only the elevated probability that significant events occur in this period.
7. Complete Prediction Register
The following is the full set of publicly reconcilable predictions derived from this note. Each is dated, specific and publicly tracked at tempora.ltd.
8. Scoring Methodology
All predictions in Section 7 are publicly scored. Scoring rules:
- Hit: A qualifying event occurs within ±90 days of the predicted window date
- Miss: No qualifying event occurs within ±90 days
- Partial: An event occurs in the correct window but does not meet all stated criteria
- Scoring is public: Hits and misses are both recorded at www.tempora.ltd/predictions
A "qualifying event" for any prediction requires: (1) contemporaneous media coverage by at least two major international outlets, (2) categorization as political, economic, conflict or major policy event by independent assessment, and (3) the event was not foreseeable from public information at the time of this publication (March 2026). Scheduled elections, planned treaties, and pre-announced policy implementations do not qualify unless their outcome was genuinely uncertain.
9. Reconciliation, 9 May 2026
On 9 May 2026 Tempora's internal audit (run via Tempora's Vimshottari dasha engine + Tempora's Swiss-Ephemeris computation layer) caught the following errors in this note. The note is reconciled below per the discipline that catches errors should be published, not silently edited. The prediction register cited dasha state from a non-canonical computation source. The canonical engine returns different values. Every card in the register is reconciled below. Downstream forward-call articles citing this register inherit the corrections.
9.1 Per-card dasha-state correction
Each of the 6 prediction cards was re-run through Tempora's Vimshottari dasha engine against the canonical natal listed in Tempora's canonical-charts methodology. Results:
| Card | Original draft (MD–AD–PD) | Engine-verified (MD–AD–PD) | Verdict |
|---|---|---|---|
| India December 2027 | Rahu, Rahu, Rahu | Mars (2024-01-28 to 2031-01-27), Mercury (2027-07-27 to 2028-07-23), Sun (2027-12-06 to 2027-12-24) | All three layers wrong; corrected |
| UK March 2027 | Saturn, Saturn (no PD stated) | Mercury (2012-08-08 to 2029-08-08), Saturn (2026-11-25 to 2029-08-04), Saturn (2026-11-25 to 2027-04-29) | MD wrong; AD correct (resonant Saturn pratyantara inside Mercury MD); corrected |
| Russia February 2028 | Jupiter, Mars (no PD stated) | Jupiter (2014-07-18 to 2030-07-18), Mars (2027-03-16 to 2028-02-19), Moon (2028-01-18 to 2028-02-15) | MD and AD verify on the canonical 12 June 1991 chart; the original card's chart-attribution prose carried late-December 1991 which would have produced Moon MD, Venus AD instead; chart attribution corrected |
| China September 2028 | Rahu, Jupiter (no PD stated) | Mercury (2018-12-19 to 2035-12-19), Rahu (2028-06-13 to 2030-12-31), Rahu (2028-06-13 to 2028-10-30) | MD wrong; AD wrong; corrected |
| Pakistan October 2026 | Moon, Saturn (no PD stated) | Moon (2025-05-18 to 2035-05-18), Mars (2026-03-18 to 2026-10-17 then Rahu AD) | MD correct; AD wrong (Saturn AD on Pakistan does not begin until 2030); corrected |
| Pakistan June 2028 | Mars, Venus (no PD stated) | Moon (2025-05-18 to 2035-05-18), Jupiter (2028-04-16 to 2029-08-15), Jupiter (2028-04-16 to 2028-06-19) | MD wrong; AD wrong; corrected |
| US November 2029 | Venus, Rahu, Mars | Venus (2022-04-12 to 2042-04-12), Rahu (2029-06-10 to 2032-06-09), Jupiter (2029-11-21 to 2030-04-16) | MD correct; AD correct; PD wrong; corrected |
Net error count: of 6 cards, 4 carried wrong mahadasha lord, 5 carried wrong antardasha lord, and the one card with wrong pratyantara (US Nov 2029) was the only card with PD stated. The Russia card was the special case where the dasha string itself matched the canonical engine output but the chart-attribution prose declared a different chart entirely.
9.2 Russia natal-chart attribution correction
The Russia card originally read "Russia · Federation chart · late-Dec 1991". Tempora's canonical Russia chart is the 12 June 1991, 12:45 MSK RSFSR sovereignty declaration, per Tempora's canonical-charts methodology change-log entry 9 May 2026. The card now reads "Russia · RSFSR sovereignty declaration · 12 Jun 1991, 12:45 MSK". Engine output for the canonical chart at 15 February 2028 returns Jupiter MD, Mars AD, Moon PD, which matches the dasha string the original draft published. The card was internally inconsistent before this edit (chart-attribution wrong, dasha string right); the correction reconciles them.
9.3 Russia February 2028 mars-rahu transit-peak correction
The original draft stated "Mars forms a transit conjunction with Rahu, with the Angarak Yoga closing to within 5° near its historical maximum intensity" in February 2028. Engine compute on the same date range returns: 15 December 2027 Mars-Rahu separation 19.31°, 15 January 2028 separation 6.55°, 5 February 2028 separation 24.26°, 15 February 2028 separation 32.70°, 28 February 2028 separation 43.65°. The peak transit conjunction is in early-to-mid January 2028 (closest approach 1.0° on 6 January 2028), with Mars then crossing into Aquarius and the separation widening through February. The peak claim was off by approximately 30 days. The forward-call window remains open at the Rahu-return signal layer (transit Rahu approaches the natal Rahu position on the 12 June 1991 chart, hitting the 8° orb in mid-March 2028 and reaching exact in mid-September 2028). The "two signals fire simultaneously" framing in the original draft reduces to "Rahu-return signal fires fully through the window; Mars-Rahu peaked earlier and is separating".
9.4 Implications for downstream articles citing this register
This note's prediction register is the upstream source for every Tempora forward-call article that references a 2026-2030 country window with dasha state. Downstream articles inherit the dasha corrections above. Specifically:
- findings/russia-february-2028: already reconciled in the P0 batch on 9 May 2026 (separate branch). Mars-Rahu peak corrected to 6 January 2028; chart attribution corrected to 12 June 1991 canonical.
- findings/russia-ukraine-resolution-q3-2027: already reconciled in the P0 batch.
- article_054_russia_feb_2028: pending Section 2 reconciliation, queued.
- article_055_us_late_2029: cascade audit had flagged article 055 Section 2 as inconsistent with engine; the corrected pratyantara on the US card here (Jupiter, not Mars) supersedes both the original draft and the article 055 Section 2 framing. Article 055 reconciliation pending.
- article_056_uk_2027: inherits the UK card framing. Mercury MD with Saturn AD now flows down. Reconciliation pending.
- article_057_india_dec_2027 (if shipped) and article_058_pakistan: inherit the India and Pakistan card framings respectively. Reconciliation pending.
- article_060_china_sep_2028 (if shipped): inherits the China card framing. Reconciliation pending.
- tracker.html: tracker entries reference the same windows and lift figures. Tracker prose reconciliation already on the remediation queue.
9.5 Reframe: dasha layer as context, not load-bearing claim
The structural-elevation argument in this note (calibrated transit-against-natal scoring producing elevated confluence at named windows) is unchanged. The dasha layer in each card was published as additional context for the reader. With the corrections above, the dasha layer is now accurate against engine, and the period character framing for each window can be re-derived from the corrected mahadasha-antardasha lord pair. Specifically: India December 2027 carries Mars MD character (assertive, competitive, military or economic confrontation themes) inside Mercury AD (negotiation, communication-driven, mercurial); the original "Rahu MD" framing implied a fundamentally different period character that does not match engine. UK March 2027 carries Mercury MD character with Saturn AD restraint, not "Saturn MD" through-line.
9.6 Pratyantara claim correction at US Nov 2029 (cross-reference to article 055)
Cascade audit on article 055 (commit c59b946) had flagged that the article's Section 2 introduced a fresh error claiming Jupiter AD, where engine returns Rahu AD. This note's original draft stated Mars pratyantara at the same date; engine returns Jupiter pratyantara. Net: the Mars pratyantara claim in this note's original draft and the Jupiter antardasha claim in article 055 Section 2 are both wrong. Engine is the source of truth for both: Venus MD, Rahu AD, Jupiter PD on the canonical Sibly chart at 30 November 2029. Both surfaces require alignment to this engine output.
9.7 Reconciliation commitment
The 12-window forward register in Section 7 stands at the date and window-claim layer. The dasha attributions inside each card have been corrected per engine compute. The Russia chart-attribution has been corrected to the canonical 12 June 1991 chart. The Russia mars-rahu peak date has been corrected from "February 2028" to "early-to-mid January 2028". The named-precedent set for the Russia 5.46x signature is reconciled in Note 005 Section 9 and inherited here. Future revisions of forward registers will apply Gates 5.AB through 5.AD and Gate 5.DD per the research publishing standards document, ensuring per-card dasha verification, FAQ-prose chart consistency, and calendar-table date verification at commit time.
All forward prediction scans in this note are reproducible by running python -m Tempora's prediction engine (CLI) [Country] from the Tempora Research repository. Calibrated weights used are from the calibrated-weights table, generated by python -m engine.calibrate all. Full methodology in Research Note #005. The Section 9 reconciliation is reproducible by running Tempora's dasha engine against the canonical natals listed in Tempora's published canonical-charts methodology document.
9b. Engine Update · 17 June 2026
This note carried the forward-call inventory as published at the time of first publication. The tracker has accumulated resolved verdicts since then. This amendment surfaces the current public scoreboard and the methodology refinement that has taken place across the open windows.
Current public scoreboard (as of mid-2026). 97 published forward calls total. 4 resolved. 1 MET (call 035, March 2026 India double-eclipse on the 2H/8H axis, verified 5 May 2026 with Nifty 50 reversal greater than 2 per cent on 9 March 2026 plus banking and currency stress documented in the same window). 3 FAILED (call 042 gold band overshoot verified 6 May 2026, call 052 West Bengal seat allocation, the retracted Rahu-Pisces water-events call where the temporal premise was found incorrect during the audit cycle). 93 calls awaiting their window close. The scoreboard is published at tempora.ltd/tracker and the per-call audit trails live with the underlying articles.
Methodology refinement applied across the open cohort. Each open forward call has been re-evaluated against the expanded engine state described in Note 002. The re-evaluation produces a verdict shape per call (CONFIRM, SHARPEN with sub-window timing-shift, WIDEN with more uncertainty than the original framing, REVERSE where the engine reads opposite the article direction, RE-ANCHOR where the chart pick may be wrong, REVISE PREMISE where the mechanism description needs reframing). The verdict shape sits alongside the original call on the article's amendment block. The test condition and the public window are unchanged.
Notable verdicts surfaced on open calls. Three calls received REVERSE verdicts where the engine now reads opposite the original direction: gold 2027 post-exaltation reset, Korean Peninsula 2027 to 2028 markers cluster, Russia February 2028 sudden action window. Each carries the chart-side update published openly in the article body alongside the original call. The published forward call stays on the tracker exactly as written; the chart-side disagreement is documented as an amendment, never an edit to the scoreboard. Eight calls received WIDEN verdicts (single-day binary threshold tests where the chart-side reading reads closer to coin-flip than confident-MET).
What this means for the calibration. The scoreboard with four resolved verdicts is too small a sample to draw calibration statistics from. The discipline of the current moment is to publish the small-N state honestly. The Q4 2026 and 2027 windows close substantial portions of the open cohort, and the accumulated resolved-verdict count will grow naturally from the present low-double-digits to a calibration-meaningful sample by late 2027.
The forward-call register documented in this note remains the foundation. The current state is more granular than the original publication could surface. Readers wanting the methodology underlying the verdict refinement should read Note 004 (Public Reconciliation). Readers wanting the expanded chart-side engine that produces the per-call verdicts should read Note 002 (Substrate) and Note 003 (Period Architecture).
10. Frequently asked
What is a forward call in Tempora's framework?
A forward call is a public, dated, publicly reconcilable prediction issued before the window opens. Each call names a country, a window with start and end dates, the transit and dasha signature driving the call, the calibrated lift figure (where calibration is intact) and an explicit reconciliation condition condition that would retire the call if observed.
How is each forward call structured?
Every card carries six fields: (1) country and natal chart canon, (2) window start and end, (3) transit signature with engine-verified orb, (4) Vimshottari dasha lord at MD, AD and pratyantar levels, (5) calibrated lift or uncalibrated tier label, (6) reconciliation condition condition and reconciliation commitment. The lift figure is omitted where the underlying signature was retired in the 9 May 2026 audit.
What did the 9 May 2026 audit reconcile in this note?
Section 9 documents per-card corrections: India December 2027 dasha corrected from Rahu MD to Mars MD; UK March 2027 from Saturn MD to Mercury MD; China September 2028 from Rahu MD to Mercury MD; Pakistan June 2028 from Mars MD to Moon MD; United States November 2029 pratyantar corrected from Mars to Jupiter; Russia chart canon migrated from late-December 1991 to 12 June 1991, with mars-rahu peak shifted from 5 February 2028 to 6 January 2028 in Capricorn.
What is the reconciliation condition discipline?
A forward call must specify, at issue time, the observation that would retire it. For temporal windows this is typically the absence of a stress event of named shape inside the window plus a defined cooldown. A call without an explicit reconciliation condition is not a forward call in Tempora's framework, it is a forecast statement.
What does 'uncalibrated tier' mean for the new register cards?
Where the audit retired the underlying calibration pair, the register card retains the window, signature and reconciliation condition but omits the numeric lift figure and labels the call uncalibrated tier. The call remains public and publicly reconcilable; only the multiplicative confidence claim is withdrawn pending recalibration.
How does Tempora reconcile a forward call after its window closes?
After window close, a reconciliation entry is posted to /tracker recording: did the reconciliation condition fire, what observed events fell inside the window with what shape, and whether the call counts as MET, FAILED or PARTIAL. The reconciliation is reproducible by re-running Tempora's prediction engine against the canonical natal and the post-hoc transit timestamps.