Library
Vedic Astrology Wiki

Jaimini Karakas: Roles, Rules and Reading Order

Learn the Jaimini karaka roles, distinguish seven and eight assignments, and choose the right guide before interpreting a calculated ranking.

Names and related terms
Jaimini significators · Jaimini karakas

Editorially reviewed: · Reviewed by OpenFate · Editorial Methodology

Overview

Jaimini karakas are chart-dependent significator roles. Start with the declared participant list and within-sign ranking, then read the individual role. This hub separates that calculation from natural significators, houses and symbolic interpretation.

At a glance

Start here
Scheme, inputs, ranking, then role
OpenFate policy
Seven roles; Sun through Saturn
Alternative covered
Rao’s eight-role scheme includes Rahu
Not a result
A rank does not measure personal worth

Explore concepts

Which guide answers your question?

Use the chara-karaka guide to reproduce the ordering. Use the seven-versus-eight comparison when two programs disagree. The individual AK, AmK, BK, MK, PK, GK and DK pages explain what each label identifies and what extra assumptions must not be added.

The Jaimini astrology overview has a different job: it maps a family of techniques and explains why karakas, sign aspects and timing systems are not interchangeable. A karaka table alone is not a complete reading of that tradition.

Read one seven-role list

In an invented seven-body input, Sun, Moon, Mars, Mercury, Jupiter, Venus and Saturn have within-sign advances of 24°, 20°, 16°, 12°, 8°, 4° and 2°. The descending assignments are AK, AmK, BK, MK, PK, GK and DK respectively.

This ordering does not say that the Sun is brighter, better placed or more beneficent than every other planet. Nor does Venus receiving GK establish an enemy. Each column answers a narrow calculation question; relationships require independent evidence.

Why can two role lists differ?

Compare the participating bodies, precision, zodiac settings and tie policy before interpreting differences. OpenFate’s inspected policy uses seven bodies and excludes Rahu; Rao’s chapter presents eight with a reversed Rahu advance.

Do not merge a role from one scheme with a rank from another. Save the scheme alongside the result, and retain uncertainty if input precision can alter the ordering. A reproducible label is not proof of a soul, family outcome or future event.

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.

Search the Wiki