Matrikaraka: MK Calculation and Maternal-Role Boundaries
Find Matrikaraka by fourth rank, distinguish variable MK from the Moon and fourth house, and keep family interpretations separate from calculation.
Overview
Matrikaraka, abbreviated MK, is fourth in the chara-karaka ordering. Its traditional maternal association does not mean that the Moon is always MK or that a birth chart verifies facts about a parent.
At a glance
- Rank
- Fourth in the selected list
- Natural versus variable
- Moon symbolism is not the MK assignment
- Related but separate
- Fourth house and its ruler
- Not determined
- Parentage, health or caregiving quality
What does the MK label identify?
MK labels one eligible planet after sorting within-sign advances. The seven- and eight-role tables both place MK fourth, although their participating bodies differ. The label should always travel with the scheme that produced it.
A traditional maternal association is an interpretive category, not a biological or social identification test. Family structures and caregiving arrangements cannot be reconstructed reliably from a role abbreviation.
The Moon is first, Saturn is fourth
Take invented within-sign advances Moon 28°, Mercury 25°, Sun 21°, Saturn 18°, Jupiter 14°, Venus 8° and Mars 3°. In the seven-role scheme the Moon is AK and Saturn is MK.
This is not a contradiction: a natural association of the Moon and a variable role assigned to Saturn belong to different methods. The fourth rank also says nothing about which sign or house Saturn occupies.
Can this describe my mother’s life?
Not as a verified conclusion. A coordinate ranking cannot establish a parent’s character, illness, longevity or relationship quality. Keep any traditional reflection conditional and separate from actual family evidence.
If two programs disagree on MK, compare full precision and the seven/eight participant list before changing the interpretation. Exact ties also need a stated rule; selecting whichever description feels more familiar is not a calculation check.
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.