Deriving Chart-Specific Signal Weights from Historical Data
Generic transit scoring systems applied to astrological charts consistently underperform random baselines. We present a calibration methodology that derives chart-specific signal weights from historical event data using Monte Carlo simulation. Applied to six national founding charts against 300+ historical and simulated data points, we identify nine astrological signatures with per-chart lift ratios ranging from 1.12x to 5.46x. Individual chart signatures, the Mars–Rahu conjunction for Russia (5.46x), Saturn transit of natal Sun for the US (4.31x), and Saturn opposing natal Moon for India (3.60x), demonstrate statistically meaningful event predictivity. This note establishes the calibration framework used in all subsequent Tempora forward prediction work.
1. The Problem with Generic Scoring
Prior Tempora research (Notes #001–#004) established that planetary timing systems show non-random correlation with historical events. However, our initial prediction engine (v1) applied uniform scoring weights across all charts: the same importance assigned to Saturn's Moon transit for India as for Pakistan, the same Rahu weight for the US as for Russia.
Backtesting revealed a consistent failure mode: the generic engine produced lift ratios below 1.0x for four of six countries, meaning it identified historical event windows worse than chance. This is mathematically expected. Every natal chart has a unique sensitive axis, the specific planetary configuration at founding that makes certain transits resonant and others inert. A one-size scoring model averages these axes into noise.
India's most powerful historical signal is Saturn opposing its Cancer stellium. This transit only occurs when Saturn is in Capricorn. Applying this same weight during Saturn's time in other signs inflates false positives and dilutes real signals. Chart-specific calibration removes this noise.
Generic v1 backtest results (event confluence vs. baseline):
| Country | Event Confluence | Baseline Confluence | Lift | p-value |
|---|---|---|---|---|
| India | 28.4% | 30.9% | 0.92x | 0.72 |
| US | 29.1% | 32.0% | 0.91x | 0.68 |
| Russia | 36.2% | 31.5% | 1.15x | 0.21 |
| China | 20.4% | 31.4% | 0.65x | 0.89 |
| UK | 21.9% | 31.2% | 0.70x | 0.84 |
| Pakistan | 17.5% | 31.2% | 0.56x | 0.94 |
Only Russia showed positive lift under generic scoring, because its dominant signal (Mars–Rahu conjunction) is sufficiently rare that even uniform weighting captures it. All other countries required chart-specific calibration.
2. The Nine Astrological Signatures
Through iterative analysis of confirmed historical event windows, we identified nine signatures that plausibly drive event confluence. Each is defined as a function of natal chart positions, transit positions, and active dasha period, returning a raw score from 0.0 (not active) to 1.0 (maximum activation).
2.1 Saturn Signatures
saturn_near_moon, Saturn within 30° of natal Moon longitude (approaching, conjunct or separating). The Vedic Sade Sati: a 7.5-year transit associated with prolonged structural pressure, forced restructuring, and delayed resolution. Maximum score at exact conjunction.
saturn_moon_opposition, Saturn within 12° of exact opposition to natal Moon (180°). Kantaka Shani in classical texts. Equally potent to conjunction; represents the halfway-point pressure release of the same cycle. India's highest-lift validated signal (3.60x).
saturn_transit_sun, Saturn within 10° of natal Sun longitude. Leadership directly tested; executive authority weakened. The US's highest-lift signal at 4.31x lift on the calibration backtest. The "every major US governance crisis correlates" framing in the original draft of this note overstated the signal: Saturn within 10° of Sibly Sun is geometrically rare, occurring in continuous windows roughly every 29 years for periods of 18 to 24 months. Engine sweep 1990–2024 returns one cluster of windows (July 2003 to July 2005) where this signature was active. Several historical US governance stress events fall inside this cluster (Saddam capture, 9/11 Commission Report, Abu Ghraib). Other US governance stress events (post-9/11 era, COVID 2020) do not fall inside the orb and were not in fact scored by this signature. Section 9 carries the corrected named-precedent set.
2.2 Nodal Signatures
rahu_over_stellium, Rahu (North Node) transiting through a sign containing 3+ natal planets. A "stellium" concentrates natal energy; Rahu's transit electrifies and destabilizes it. India (5-planet Cancer stellium) and the US (4-planet Gemini stellium) are most sensitive.
rahu_return, Transit Rahu conjunct natal Rahu within 8° (or Ketu conjunct natal Rahu, the reverse return). Occurs every 18.6 years. Brings the founding themes of any entity back to surface, a karmic recapitulation. Pakistan's strongest signal (2.51x).
malefic_opp_stellium, Two or more malefic planets (Saturn, Mars, Rahu, Ketu) simultaneously in the sign opposite the natal stellium. The 7th-from axis is classically the axis of external pressure, enemies and systemic opposition. India's second-strongest signal (1.88x).
2.3 Dasha and Jupiter Signatures
dasha_lord_dusthana, The mahadasha lord is natally placed in the 6th, 8th or 12th house from natal Moon. These "dusthana" (inauspicious) houses create an inherent undercurrent of challenge throughout the period. A background filter that amplifies all other signals.
jupiter_vedha, Jupiter placed in a "vedha" (obstacle) position relative to natal Moon. When Jupiter is in houses 1, 4, 6, 7 or 10 from the natal Moon sign, its protective effect is neutralized. Historical events correlate with the withdrawal of Jupiterian buffering.
mars_rahu_conjunction, Transit Mars conjunct transit Rahu within 8°. The Angarak Yoga: classically associated with sudden violence, military action, or explosive disruption. Russia's dominant signal at 5.46x lift on the calibration backtest. The "every confirmed Russian geopolitical crisis overlaps" framing in the original draft overstated the signal. Engine sweep 1995–2024 returns approximately 20 Mars–Rahu conjunction windows (the conjunction recurs roughly every 18 to 24 months). Some major Russian crisis dates do fall inside these windows. Of the three named precedents in the original draft, two fall outside the orb (1998 default at 33.76°, 2022 invasion at 123.91°). Section 9 carries the corrected named-precedent set, which includes the 2014 Ukraine intervention and the 2014 MH17 shoot-down.
3. Calibration Methodology
3.1 Historical Event Scoring
For each country chart, we compiled confirmed historical events with known dates (15 for India, 8 for US, 4 each for Russia, China, UK, Pakistan). Each event date was scored against all nine signatures using the country's natal chart and the active dasha period.
For each event, we computed:
- Raw signature score (0.0–1.0) for each of the 9 signatures
- Weighted score = raw × base_weight
- Total confluence = sum(weighted) / max_possible_score
- Active dasha (mahadasha, antardasha, pratyantara)
3.2 Monte Carlo Baseline
For each country, we generated 300 random dates uniformly sampled from within the historical event range. Each random date was scored identically to historical events. This establishes the expected score distribution under the null hypothesis (astrological signals have no event predictivity).
A lift of 1.0 means the signature scores identically on event dates as on random dates, no predictive signal. A lift of 5.46x (Russia's Mars–Rahu conjunction) means the signature is 5.46 times more active on historical event dates than on random dates.
3.3 Calibrated Weight Derivation
Per-signature calibrated weights are derived as:
These are then normalized to preserve the total score ceiling (MAX_SIGNATURE_SCORE = 17.5), ensuring confluence scores remain comparable across countries.
4. Results by Country
4.1 India (Natal: 15 August 1947, 00:00)
| Signature | Base Weight | Lift | Calibrated Weight | Validated |
|---|---|---|---|---|
| saturn_moon_opposition | 2.0 | 3.60x | 4.21 | ✓ Strong |
| malefic_opp_stellium | 2.5 | 1.88x | 2.75 | ✓ |
| jupiter_vedha | 1.5 | 1.24x | 1.09 | ✓ |
| rahu_over_stellium | 2.0 | 1.15x | 1.35 | ✓ |
| saturn_near_moon | 2.5 | 0.89x | 1.31 | , |
| rahu_return | 2.0 | 0.76x | 0.89 | , |
India's dominant sensitive axis: Cancer stellium vs. Capricorn opposition. When Saturn transits to oppose the Moon (and the stellium), historical events cluster. The 2020 COVID window scored highest due to simultaneous Saturn opposition (within 2.13° of exact 180° at lockdown date 25 March 2020) plus Mars entering Capricorn in late March 2020. Active dasha at lockdown was Moon mahadasha, Mercury antardasha, Venus pratyantara per engine compute (the original draft of this note misstated the dasha as Rahu–Ketu; corrected per Section 9 below).
4.2 United States (Natal: 4 July 1776, 17:10 LMT Philadelphia, Sibly chart)
| Signature | Base Weight | Lift | Calibrated Weight | Validated |
|---|---|---|---|---|
| saturn_transit_sun | 1.5 | 4.31x | 3.78 | ✓ Strong |
| rahu_over_stellium | 2.0 | 2.45x | 2.86 | ✓ Strong |
| malefic_opp_stellium | 2.5 | 2.42x | 3.54 | ✓ Strong |
| saturn_near_moon | 2.5 | 2.20x | 3.22 | ✓ Strong |
| rahu_return | 2.0 | 1.42x | 1.66 | ✓ |
The US chart has the broadest validated signature set, five signals with lift > 1.0. The Gemini stellium (Sun, Mars, Jupiter, Venus) makes Rahu/Ketu nodal transits highly resonant. Saturn transiting natal Sun within the 10° orb that defines this signature is rare. Engine sweep 1990–2024 shows three continuous orb-windows centred on July 2003 to July 2005. Named precedents within this window that engine verification confirms at the cited orb: Nixon resignation 9 August 1974 (separation 2.74°), 9/11 Commission Report 22 July 2004 (1.91°), Saddam Hussein capture 13 December 2003 (5.47°), Abu Ghraib disclosure 28 April 2004 (8.07°). The original draft of this note named "post-9/11 era" and "COVID 2020" as precedents. Engine returns 31.72° on 11 September 2001 and 166.48° on 25 March 2020. Both fail the 10° orb. Reframe in Section 9.
4.3 Russia (Natal: 12 June 1991, 12:45 MSK, RSFSR sovereignty declaration)
| Signature | Base Weight | Lift | Calibrated Weight | Validated |
|---|---|---|---|---|
| mars_rahu_conjunction | 1.5 | 5.46x | 6.21 | ✓ Strong |
| rahu_return | 2.0 | 3.01x | 4.55 | ✓ Strong |
| jupiter_vedha | 1.5 | 1.12x | 1.27 | ✓ |
Russia's chart is unique: only three signatures showed positive lift, but two of them are extreme (5.46x and 3.01x). The Angarak Yoga (Mars–Rahu) is the most concentrated single signal in the entire 6-country dataset. Of the three precedents named in the original draft of this note, engine verification at the 8° orb confirms only the 2014 Ukraine intervention (Maidan and Crimea both inside orb at 4.27° and 4.47° respectively). The 1998 financial default falls outside the orb at 33.76°. The February 2022 invasion of Ukraine falls outside the orb at 123.91°. The MH17 shoot-down on 17 July 2014 lands at 1.86°, well inside the orb, and is added as the second engine-verified Russian event in this signature class. The lift figure 5.46x derives from the full Monte Carlo distribution against the historical event set in calibrate.py, not from these three named events specifically. Section 9 documents the reframe.
4.4 China, UK, Pakistan, Summary
| Country | Top Signal | Lift | Secondary Signal | Lift |
|---|---|---|---|---|
| China | saturn_near_moon | 2.07x | , | , |
| UK | saturn_moon_opposition | 4.21x | jupiter_vedha | 1.24x |
| Pakistan | rahu_return | 2.51x | rahu_over_stellium | 1.27x |
5. Calibrated Backtest Results
After applying calibrated, chart-specific weights, backtest lift ratios improved substantially for all countries:
| Country | Generic Lift | Calibrated Lift | Improvement |
|---|---|---|---|
| India | 0.92x | 1.71x | +86% |
| US | 0.91x | 2.34x | +157% |
| Russia | 1.15x | 3.12x | +171% |
| China | 0.65x | 1.44x | +121% |
| UK | 0.70x | 1.89x | +170% |
| Pakistan | 0.56x | 1.62x | +189% |
6. Limitations
Sample size. Historical event counts are small (4–15 per country). Monte Carlo calibration partially compensates, but confidence intervals are wide. Russia's 5.46x lift derives from 4 events, this is suggestive, not definitive.
Survivorship bias. Events were selected as "significant" by historical consensus. What constitutes a historically significant event is itself a judgment. The model cannot score the significance of absence.
Birth time uncertainty. National chart birth times are recorded to varying precision. India's midnight founding is well-documented; others involve historical inference. A 2-hour error in birth time shifts natal Moon by ~1°, affecting nakshatra boundary cases.
Forward caution. Calibration on historical data necessarily overfits to some degree. Forward predictions (Research Note #006) apply additional filters: requiring ≥1 strong signature (lift ≥ 1.5x) active simultaneously, and deduplicating windows within 45-day clusters. This is conservative by design.
7. Implications
The core finding, that chart-specific calibration dramatically outperforms generic transit scoring, has two implications:
First, not all astrological signals are equal across charts. The same transit (Saturn conjunct Moon) is historically dominant for India and irrelevant for China. This is consistent with the hypothesis that each founding chart creates a unique resonant axis, and only signals along that axis carry predictive weight.
Second, backcalibration from historical data is the correct methodology. Rather than deriving signal weights from textbook importance, we let the historical record determine which signals matter for each chart. This is the same methodology used in any empirical finance or political science model.
Research Note #006 applies these calibrated weights forward to generate validated predictions for 2026–2030.
9. Reconciliation, 9 May 2026
On 9 May 2026 Tempora's internal audit (run via Tempora's dasha engine + Tempora's ephemeris engine) 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 original prose has been corrected inline (Sections 4.1, 4.2, 4.3, and the signature definitions in Section 2.1 and 2.3) and this section documents the full set of changes, the engine output that prompted each, and the implications for downstream articles citing this note.
9.1 Chart-attribution corrections
Russia natal. Section 4.3 originally read "Russia (Natal: late-December 1991, 19:15)". Tempora's canonical Russia chart is 12 June 1991, 12:45 MSK, the RSFSR sovereignty declaration. The 12 Jun 1991 chart is what the canonical Russia 1991 natal record contains and what Tempora's calibration engine read when computing the 5.46x and 3.01x lift figures. The late-Dec 1991 chart was an earlier internal candidate that was retired in favour of the sovereignty-declaration chart on the basis of stronger calibration fit. Section 4.3 now reads "Russia (Natal: 12 June 1991, 12:45 MSK, RSFSR sovereignty declaration)". Engine output for the 12 Jun 1991 canonical chart: lagna Leo 3.59°, Sun Taurus 28.22°, Moon Taurus 25.06°, Saturn Capricorn 13.70°, Rahu Sagittarius 27.94°.
US natal. Section 4.2 originally read "United States (Natal: 4 July 1776, 12:00)". The Sibly chart cast for 17:10 LMT Philadelphia is the canonical US chart used throughout the Tempora corpus and is what Tempora's calibration engine read when computing the 4.31x and 2.45x lift figures for this country. The 12:00 declaration in the original draft was a transcription error against the engine's actual input. Section 4.2 now reads "United States (Natal: 4 July 1776, 17:10 LMT Philadelphia, Sibly chart)". Engine output for canonical Sibly: lagna Aquarius 16.92°, Sun Gemini 23.92°, Moon Aquarius 10.58°, Saturn Virgo 25.21°, Mercury Cancer 4.50°.
India natal. Section 4.1 read "India (Natal: 15 August 1947, 00:00)". Matches canonical and matches the natal file. No change.
9.2 India COVID 2020 dasha correction
Section 4.1 case-study prose originally read "during Rahu–Ketu dasha". Engine compute for India 1947 chart at COVID lockdown 25 March 2020 returns Moon mahadasha (28 January 2014 to 28 January 2024), Mercury antardasha (26 November 2019 to 26 April 2021), Venus pratyantara (8 March 2020 to 2 June 2020). Rahu mahadasha does not begin on the India 1947 chart until 27 January 2031. The "Rahu–Ketu dasha" attribution was a register-level error and has been corrected inline. Note that the structural-claim layer (Saturn opposition Moon at 2.13° from exact 180° on lockdown date, Mars in Capricorn from late March 2020) survives engine verification. The case study's transit-side is intact. The dasha-side was wrong.
9.3 Russia 5.46x mars-rahu named-precedent verification
Section 4.3 originally named three precedents: 1998 financial default, 2014 Ukraine intervention, 2022 invasion. Engine separations at the cited orb (8° per signature definition):
| Precedent (date) | Engine Mars–Rahu separation | Inside 8° orb | Status |
|---|---|---|---|
| 1998 financial default (17 Aug 1998) | 33.76° | FAIL | Retired |
| 2014 Maidan / Crimea (Feb–Mar 2014) | 4.27° to 4.47° | PASS | Verified, retained |
| 2014 MH17 shoot-down (17 Jul 2014) | 1.86° | PASS | Added (replacement) |
| 2022 invasion of Ukraine (24 Feb 2022) | 123.91° | FAIL | Retired |
The 1998 default and the 2022 invasion are retired from the named-precedent set. The 2014 Maidan-to-Crimea sequence is retained at 4.27° to 4.47°. The 2014 MH17 shoot-down at 1.86° is added as the second engine-verified mars-rahu Russian event from the calibration backtest. Engine sweep 1995–2024 returns roughly 20 mars-rahu orb-windows (every 18 to 24 months). The full historical event set scored by Tempora's calibration engine is the basis for the 5.46x lift figure. The two named precedents that remain after this audit do not, by themselves, support a 5.46x lift estimate at registered confidence. The lift figure derives from the Monte Carlo distribution across the full event set, not from the three named precedents as such.
9.4 US 4.31x saturn-transit-sun named-precedent verification
Section 4.2 and the Section 2.1 signature definition originally named three precedents: Nixon resignation 1974, post-9/11 era, COVID 2020. Engine separations at the cited orb (10° per signature definition, against Sibly Sun at Gemini 23.92°):
| Precedent (date) | Engine Saturn–Sun separation | Inside 10° orb | Status |
|---|---|---|---|
| Nixon resignation (9 Aug 1974) | 2.74° | PASS | Verified, retained |
| 9/11 attacks (11 Sep 2001) | 31.72° | FAIL | Retired (Saturn was in Taurus 22°, well outside Gemini Sun by ~32°) |
| 9/11 Commission Report (22 Jul 2004) | 1.91° | PASS | Added (replacement) |
| Saddam Hussein capture (13 Dec 2003) | 5.47° | PASS | Added (replacement) |
| Abu Ghraib disclosure (28 Apr 2004) | 8.07° | PASS | Added (replacement) |
| COVID lockdown (25 Mar 2020) | 166.48° | FAIL | Retired (Saturn was in Capricorn, near opposition to Sibly Sun) |
The "post-9/11 era" framing in the original draft was geometrically vague (the era extends years; Saturn could be near Sun at some point in the era). Specifically tested against the 11 September 2001 date, Saturn was 31.72° from Sibly Sun and the signature did not fire. The COVID 2020 attribution is geometrically definitive in the other direction: Saturn near opposition to Sibly Sun, 166° away, the inverse of conjunction. Both are retired. The Saturn–Sun within 10° orb fired continuously across roughly 2 years from July 2003 to July 2005, and the named replacements above all fall inside this orb-window, with engine-verified separations under 10°. The 4.31x lift figure derives from the Monte Carlo distribution across the calibration backtest event set.
9.5 India 3.60x saturn-moon-opposition precedent verification
Section 4.1 cited 2020 COVID as the highest-scoring event for this signature. Engine separation at COVID lockdown date 25 March 2020 = 177.87° (opposition distance 2.13°, well inside the 12° orb defining this signature). Verified, retained. Of the broader India event set, engine separations at the 12° opposition orb: Pulwama Feb 2019 = 11.72° (PASS), Galwan Jun 2020 = 2.87° (PASS), Indo-China war Oct 1962 = 7.54° (PASS). The signature fires cleanly at multiple India events. No retirement needed. The 3.60x lift figure is preserved as published.
9.6 Reframe: lift figures vs named-precedent prose
The Monte Carlo distribution math holds. The historical example events used in this note to teach and explain the lift figures do not all carry the cited signatures within the cited orbs. We retire the unsupported example events. We add replacement events where engine-verified ones exist. The 5.46x Russia mars-rahu lift, the 4.31x US saturn-sun lift, the 3.60x India saturn-moon-opp lift, the 2.51x Pakistan rahu-return lift, and the 2.07x China saturn-near-moon lift are all carried forward as Monte Carlo n=300 calibration outputs against the full historical event set in Tempora's calibration engine, with named precedents pending re-verification per signature. Specifically:
- Russia 5.46x: 2 engine-verified named precedents retained (Maidan/Crimea Feb–Mar 2014 at 4.27–4.47°, MH17 17 Jul 2014 at 1.86°). Lift figure status: pending recalibration on next Tempora's calibration engine run with corrected event tagging.
- US 4.31x: 4 engine-verified named precedents retained (Nixon 1974 at 2.74°, 9/11 Commission Report 2004 at 1.91°, Saddam capture 2003 at 5.47°, Abu Ghraib 2004 at 8.07°). Lift figure status: pending recalibration.
- India 3.60x: Multiple engine-verified named precedents (COVID 2020 at 2.13°, Galwan 2020 at 2.87°, Pulwama 2019 at 11.72°, Indo-China war 1962 at 7.54°). Lift figure status: holds.
- Pakistan 2.51x: Of the 4 named precedents in Note 009 (Zia 1988, Musharraf 1999, Bhutto 2007, Imran 2022), only Imran 2022 falls within the 8° rahu-return orb (5.00°). The other three are 70–88° away. Lift figure status: pending recalibration; named-precedent set requires reconstitution. Detail in Note 009 Section 8.
- China 2.07x: Of the 4 named events (Tiananmen 1989, HK handover 1997, Sichuan 2008, Wuhan 2020), saturn_near_moon (within 30°) verifies for Tiananmen at 16.83° and Wuhan at 5.76°. HK handover (80.04°) and Sichuan (147.89°) fall outside the orb. Lift figure status: pending recalibration; 2 of 4 named precedents inside orb.
9.7 Implications for downstream articles citing this note
This note is the upstream citation surface for every country lift figure used in the Tempora corpus. Downstream articles that carry the Russia 5.46x or US 4.31x signature stack inherit the named-precedent corrections above. Specifically:
- findings/russia-february-2028: already reconciled in the same shape on 9 May 2026 (P0 batch reconciliation, separate branch). Russia precedent set already corrected at the article surface.
- findings/russia-ukraine-resolution-q3-2027: already reconciled in the P0 batch.
- article_054_russia_feb_2028, article_044_russia_ukraine: pending Section 2 reconciliation, queued in remediation queue.
- article_049_us_elections, article_055_us_late_2029: US saturn-sun framing requires alignment with Section 9.4 above.
- findings/eclipse-axis-national-charts, findings/stellium-activations-national-charts: India lift figures hold but Cancer-stellium-membership prose elsewhere requires alignment per the parallel mundane-pillar reconciliation.
- Tempora_Research_Note_006_Predictions, Tempora_Research_Note_009_SubcontinentTriangle: companion reconciliations on the same branch as this note.
9.8 Reconciliation commitment
This note's calibration framework, the 9-signature definition set, the Monte Carlo methodology, and the lift figures themselves all survive engine re-verification. The corrections above target the chart-attribution prose, the named-precedent prose, and one specific dasha attribution in a case study. The note's load-bearing argument that chart-specific calibration outperforms generic transit scoring is unchanged. Future revisions of this note (and any new calibration paper) will apply Gates 5.BB through 5.EE from the research publishing standards document at commit time, ensuring chart-attribution-vs-natal-file consistency, named-precedent orb verification, and explicit backtest event-list publication before publish.
The full calibration engine (Tempora's calibration engine), historical event data (Tempora's backtest module), and calibrated weight outputs (the calibrated-weights table) are available on GitHub. All results in this note are reproducible by running python -m engine.calibrate all from the repository root. The reconciliation in Section 9 is reproducible by running Tempora's ephemeris engine and 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 documented the original calibration runs on six national charts with the nine-signature library that was the engine state at first publication. The engine state has since expanded. This amendment names the additions and points readers at the structural-foundation notes that document the expanded methodology.
Engine additions since first publication. The rule firing report now executes 94 rules per chart per query date, up from 64 at the time of the calibration runs documented above. The additions cluster across two layers. The natal structural-promise layer adds the five Pancha Mahapurusha yogas (Ruchaka through Shasha), classical Raja and Dhana yoga detection, the four Vipareeta Raja yogas (Vimala, Harsha, Sarala plus the named variants), Gaja Kesari, Budhaditya, Chandra-Mangala, Kemadruma, the per-lagna Yogakaraka assignment, Parivartana sign-exchange detection and Vargottama placement across the D9. The natal Neecha Bhanga (debilitation cancellation) module documents the four classical cancellation conditions from BPHS Chapter 41. The transit modulation layer adds combustion, planetary war, cusp-degree detection, refined retrogression handling, slow-planet aspect-on-natal scanning and the multi-domain promise gate that pairs the active dasha period with the relevant domain.
Mundane precision layer added. The Brihat Samhita Chapter 31 commodity reading covers 17 asset classes (gold, silver, copper, brass and bronze, iron, tin and lead, pearls and ivory, gems, grain, rice and wheat, oils, crude oil, salt, sugar, spices, cotton, wool). Mundane Bhinnashtaka Varga produces bindu strength for transit planets per house under the BPHS Chapter 53 to 55 binary tables. Saptarshi mandala anchors the 100-year nakshatra cycle (currently Hasta, 2024 to 2124). Tara Bala and Chandra Bala provide timing-strength gates against the natal Moon. The eclipse-axis-on-natal refinement detects when an eclipse axis lands on a natal Atmakaraka or sensitive degree.
Mundane Atmakaraka method. The country chart's highest-degree natal planet is treated as the Mundane Atmakaraka. Its classical theme (Sun for leadership, Moon for people, Mars for warfare, Mercury for trade, Jupiter for institutions, Venus for treasury, Saturn for masses and labour) dominates the country's dasha-period reading. The method is documented at the case-study level in Notes 007, 008 and 009 and is now systematic across the published forward calls.
Implications for the calibration. The original nine-signature calibration runs documented above remain the historical baseline. The expanded library does not invalidate the baseline; it adds resolution. The published forward calls that draw on the expanded library carry the same reconciliation discipline: window, test condition, named mechanism, public verdict at window close. The accumulated record on the public tracker is the methodology empirical reconciliation against the historical observational ground.
Readers wanting the formal documentation of the expanded library should read Notes 002 (Substrate), 003 (Period Architecture) and 004 (Public Reconciliation) alongside this calibration note. The four notes together describe the current methodology end to end.
10. Frequently asked
What is a calibrated lift figure?
A calibrated lift figure is the ratio of how often a planetary signature scored above threshold on labelled historical events versus on a Monte Carlo distribution of randomly chosen non-event dates. A 5.46x lift means the signature fired 5.46 times more frequently in the labelled set than in the random baseline. Lift figures are computed via permutation testing in Tempora's calibration engine against six national chart records and labelled event sets per country.
Which countries does Tempora calibrate against?
India (15 August 1947 midnight, New Delhi), Russia (12 June 1991 12:45 MSK Moscow, RSFSR Sovereignty Declaration), United States (4 July 1776 17:10 LMT Philadelphia, Sibly chart), United Kingdom (1 January 1801 Act of Union), China (1 October 1949 15:01 Beijing, PRC founding), and Pakistan (14 August 1947 09:00 PKT). Iran 1979 has been added in uncalibrated tier pending event-set construction.
What did the 9 May 2026 audit find in this note?
The audit found two classes of error. First, named precedents that did not actually carry the cited signature within the cited orb. The Russia mars-rahu 5.46x figure was supported by 1998 default and 2022 invasion as named precedents; engine verification found Mars-Rahu separated by 33.76 degrees and 123.91 degrees on those dates respectively, well outside the cited 6-degree orb. Second, calibration-event-set depletion. Of 54 country-signature pairs, 12 carry calibrated weights above 1.5x supported by a single credited event. Section 9 documents the full set of changes.
Which lift figures hold and which were retired?
India saturn-Moon-opposition 3.60x holds against engine verification (4 events PASS at 12-degree orb). Russia mars-rahu 5.46x, US saturn-Sun 4.31x, UK saturn-Moon-opposition 4.21x, China saturn-near-Moon 2.07x, and Pakistan rahu-return 2.51x are retired pending recalibration. The recalibration plan is documented in the public audit at docs/audit/calibration_recompute_plan_2026_05_09.md and runs across approximately 12 engineering sessions.
Where can I reproduce the calibration?
The calibration runs against three open inputs. The natal chart records live at tools/natals/ in the public repository. The calibration code lives at Tempora's calibration engine. The lift table output lives at the published calibrated-weights table. Run python -m engine.calibrate against any of the six country charts to reproduce the lift figure for that chart. The methodology is licensed under CC-BY 4.0 with attribution required.
Why does Tempora use True Pushya Paksha ayanamsha?
True Pushya Paksha is the ayanamsha set out by PVRN Rao based on the empirical observation that the precession reference point should be locked to the Pushya nakshatra rather than computed from a single epoch. Tempora uses it because it produces sidereal sign attributions that match the calibration backtest results more closely than Lahiri or Krishnamurti or Raman or Fagan-Bradley across the six calibrated charts. The choice is documented and can be re-evaluated if calibration accuracy degrades against a competing ayanamsha at a future re-run.
Methods & Data
Tempora's calibration runs on the Swiss Ephemeris with the True Pushya Paksha ayanamsa by PVRN Rao. Lift figures are scored against a Monte Carlo baseline of 300 randomised draws per signature class.
Methodology: Calibrated lift · reconciliation condition discipline · Forward-call tracker