Library
Vedic Astrology Wiki

Darakaraka: Find DK Without Predicting a Spouse

Find Darakaraka from the lowest eligible within-sign advance, handle zero degrees and Rahu variants, and separate partner symbolism from facts.

Names and related terms
Dara Karaka · DK · spouse significator

Editorially reviewed: · Reviewed by OpenFate · Editorial Methodology

Overview

Darakaraka, or DK, is the final role in a declared chara-karaka order: seventh in the seven-role scheme, eighth in the eight-role scheme. It is traditionally associated with a spouse, not a verified description of a future partner.

At a glance

Selection
Lowest eligible within-sign advance
Zero degrees
Valid value, not missing data
Separate concepts
Venus, seventh lord and DK
Not established
Partner identity, appearance or marriage date

Which planet is Darakaraka?

Under OpenFate’s seven-role policy, compare Sun through Saturn and select the smallest within-sign advance. Venus is not automatically DK, and the planet with the smallest total zodiac longitude is not necessarily DK either.

Rao’s eight-role table adds reversed Rahu and puts DK in eighth place. The participant rule matters particularly near zero; do not exclude a real zero-degree value merely because a display uses the same symbol for unavailable data.

Saturn at the beginning of Pisces

Suppose Saturn has total longitude 330°, placing it at 0° Pisces. The other seven-scheme advances are Sun 26°, Moon 22°, Mars 18°, Mercury 14°, Jupiter 10° and Venus 6°. Saturn is DK because 0° is the lowest advance.

Venus could have total longitude 306°, or 6° Aquarius, and still not receive DK. This example separates total longitude from within-sign order. It does not establish a partner’s age, appearance, temperament or time of arrival.

Can DK identify my future spouse?

Not as a factual finding. The traditional role may be used as one interpretive reference, but an actual relationship depends on people, choices and circumstances outside the chart. No single role establishes compatibility or an inevitable marriage.

Check precision and scheme before comparing two DK results. If the lowest advances are tied or input uncertainty can reverse them, preserve the uncertainty; do not choose the planet whose description seems to match a preferred partner.

Sources and editorial basis

  1. P. V. R. Narasimha Rao: Vedic Astrology — An Integrated Approach
    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