Putrakaraka: PK in Seven and Eight Karaka Schemes
See why Putrakaraka is fifth in one scheme and sixth in another, and why the traditional child association does not predict fertility or family outcomes.
Overview
Putrakaraka, or PK, is fifth in the seven-role list and sixth in Rao’s eight-role list. The traditional association with children or followers is distinct from any factual conclusion about fertility, parenthood or a child’s future.
At a glance
- Seven-role rank
- Fifth
- Eight-role rank
- Sixth; PiK occupies fifth
- Not equivalent
- Not automatically Jupiter or fifth lord
- Limit
- No fertility or child-outcome prediction
Why do calculators give different PK planets?
First inspect the role table. Adding Rahu is not the only difference: the eight-role list adds Pitri Karaka, PiK, before PK. Simply keeping the fifth-ranked planet and relabeling the scheme produces an incorrect comparison.
Jupiter as a natural significator and the fifth-house lord are separate concepts. Neither may replace a correctly calculated PK just because a reader is asking about children or teaching.
Jupiter and Venus change labels
Use seven-scheme advances Sun 28°, Moon 25°, Mars 22°, Mercury 18°, Jupiter 14°, Venus 9° and Saturn 4°. Jupiter is fifth and receives PK.
For the eight-role comparison, include Rahu at 28° within its sign, so its reversed advance is 2° and it sorts last. Jupiter remains fifth but now receives PiK; Venus is sixth and receives PK. The unchanged planetary data yield different labels under the different table.
Does PK indicate whether I will have children?
No. This role calculation does not establish reproductive health, the number of children, a duty to become a parent or a child’s circumstances. Such claims need evidence the ranking does not contain.
A useful interpretation record can identify the role and its actual placement while acknowledging the family question remains open. Do not turn missing birth precision or an unavailable eight-role implementation into a confident family prediction.
Sources and editorial basis
- P. V. R. Narasimha Rao: Vedic Astrology — An Integrated ApproachRao, 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.
- OpenFate Editorial MethodologyOpenFate 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.
- OpenFate Vedic implementation: local source review, 2026-09-08OpenFate 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.