Library
Vedic Astrology Wiki

Jaimini Astrology: Techniques and Calculation Boundaries

Understand what Jaimini astrology covers, how it relates to other Jyotish methods, and why a karaka calculation is not a complete system.

Names and related terms
Jaimini Jyotish · Jaimini system

Editorially reviewed: · Reviewed by OpenFate · Editorial Methodology

Overview

Jaimini astrology is a name commonly applied to methods such as chara karakas, sign-based aspects and certain sign periods. The label does not select every calculation setting; the method and its source must still be named.

At a glance

Scope
A group of methods, not one score
Key distinction
Roles, aspects and periods are separate
Calculation check
Within-sign advance is not total longitude
Source position
Rao advocates an integrated approach

Is Jaimini a completely separate astrology?

Rao’s preface disputes a sharp Parasari-versus-Jaimini split and notes that several associated techniques appear in both textual traditions. That is the author’s position, not proof that all practitioners use one uniform system.

For practical study, name the operation: assigning chara karakas, calculating sign aspects, deriving an arudha or choosing a sign-period sequence. Each requires its own rule set. Knowing one of them does not silently establish the others.

The longitude column that changes the answer

Suppose Mercury is at 351° total longitude and the Moon at 59°, with all other participating advances below 21°. Their within-sign values are 21° and 29°. In a seven-body ranking the Moon, not Mercury, receives AK.

Sorting the 0°–360° column would reverse that result. This example demonstrates one operational rule; it does not calculate sign aspects or a dasha, and it supplies no evidence about either person’s vocation or spiritual standing.

What should a comparison record include?

Record the textual method, sidereal settings, body list, chart layer and precision. Compare like with like: an eight-karaka output cannot be checked against a seven-karaka explanation without reconciling their role tables.

OpenFate’s inspected karaka policy is a declared seven-role implementation, not a claim to implement every technique called Jaimini. Study broader traditions as traditions, and keep biographical or relationship judgments outside what the numeric result proves.

Sources and editorial basis

  1. P. V. R. Narasimha Rao: Vedic Astrology — An Integrated Approach
    Rao, Preface, discussion of Parasari/Jaimini terminology: the author advocates integration rather than claiming a universal school definition. Rao, Chapter 8, §§8.1–8.4, printed pp. 79–83; especially §8.2 and Table 13, pp. 80–81: within-sign advancement, the eight-role table, Rahu measured from the sign end, and exact-tie sharing. The seven-role OpenFate policy and its deterministic tie break come from a separate implementation review, not from pretending this eight-role table specifies them. Original ranking examples are editorial arithmetic, not birth-chart evidence or proof of moral, spiritual or family outcomes.A named practitioner’s introduction to Jyotish. Used for terminology and a stated method, not universal school agreement or scientific validation. The added March 18, 2010 note describes changed views; it does not establish a fully revised 2010 edition.
  2. OpenFate Editorial Methodology
    OpenFate Editorial Methodology, stable sections #editorial-principles, #editorial-workflow, #editorial-ai, and #editorial-context. Used for the calculation/interpretation and evidence-boundary policy.OpenFate separates deterministic chart calculation, traditional interpretation, and modern editorial explanation.
  3. OpenFate Vedic implementation: local source review, 2026-09-08
    OpenFate local implementation review, 2026-09-08: app/modules/vedic/logic/policy.ts VEDIC_ENGINE_POLICY.karakaScheme and supportsVedicBav; facts.ts computeKarakas and computeSarvashtakavarga; constants.ts SAV_TABLES, SAV_EXPECTED_TOTALS and SAV_EXPECTED_GRAND_TOTAL; career-evidence.ts buildVedicCareerEvidence.unavailable. The reviewed policy uses seven roles without Rahu and a fixed classical-order exact-tie break. Raw BAV rows total 48/49/39/54/56/52/39, summing to 337; the Moon/Venus variant entries differ from Rao’s stated preference. BAV visibility depends on stored contract, and career evidence explicitly marks shadbala unavailable. This is a dated code review, not proof of current deployment or empirical prediction accuracy.An editorial review of local policy and calculation source files, not an independently accessible publication or proof of the deployed version. Implementation limitations and discrepancies remain separate from traditional arithmetic.
Was this article helpful?

Search the Wiki