Amatyakaraka: Find AmK and Separate Career Claims
Learn how Amatyakaraka receives second rank, distinguish it from the tenth-house lord, and check an example without predicting a career.
Overview
Amatyakaraka, abbreviated AmK, is second in the chara-karaka order. Traditional associations involve advisers or support for action; the role is not a measured career aptitude or a promise of professional success.
At a glance
- Rank
- Second, not the second house
- Traditional topic
- Advisers and practical support
- Separate field
- Tenth-house lord
- Not inferred
- Job title, income or success probability
How do I identify Amatyakaraka?
Select the scheme and sort all eligible within-sign advances. The second body receives AmK. Do not choose a planet because it occupies the tenth house, rules a career-related house or matches a desired profession.
The first two role names are shared by the seven- and eight-role tables, but adding reversed Rahu can still change their occupants. A similar abbreviation across programs is not proof that the underlying selection is identical.
Second rank is not tenth-house ownership
In an invented seven-role list, Sun is at 28°, Venus 26°, Mercury 19°, Moon 15°, Mars 11°, Jupiter 7° and Saturn 1° within their signs. Venus is second and therefore AmK.
If the same illustrative chart has Cancer lagna, its whole-sign tenth house is Aries, ruled by Mars. Venus as AmK and Mars as tenth lord answer different questions. The example does not provide placements or conditions sufficient for a career reading.
Can AmK choose a profession for me?
No role alone establishes an occupation or a likelihood of promotion. If using traditional career analysis, keep AmK distinct from house ownership, D-10 placements and the timing evidence actually available. Real skills, constraints and employment history remain independent inputs.
The inspected OpenFate career-evidence contract marks shadbala and success probability unavailable. Do not turn the presence of an AmK field into a claim that a full quantitative strength calculation or professional forecast has been verified.
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.