How Anvaya reads a chart
Until the marketing CMS ships (Phase 3), this static bridge explains our Vedic-first workflow: birth data → compute → calibration → Atlas prose → optional synastry and matchmaking SKUs.
Compute lineage
Anvaya uses KP/Krishnamurti ayanamsha with Placidus cuspal houses, while Parashari lordship and yoga rules use whole-sign houses. Strength calculations use compound panchadha friendship; plain chart labels use natural friendship for readability. Declared conventions include Taurus/Scorpio nodes, post-classical D6 as a supporting health witness only, Tajika night saham reversal, activity-scoped Panchaka, and refined 5-9 Bhakoot treatment.
- KP / Krishnamurti
- Keeps natal, panchang, muhurat, and Tajika frames aligned.
- Placidus cuspal default; whole-sign for lordship/yoga (HR 24.1)
- Preserves KP cuspal house reads while keeping Parashari lordship/yoga canonical.
- Compound panchadha for Bala/strength; natural friendship for plain surface labels
- Strength requires natural x tatkalika relationship; surface labels stay readable.
- D6 post-classical extension; odd signs count from Aries, even signs from Libra; multi-witness health only
- D6 is not part of the classical shodashavarga; stability plus disclosure beats unsourced switching.
- Rahu Taurus, Ketu Scorpio
- Node exaltation has no single consensus; readings keep node dignity low-weight.
- Night reverses A-B+C to B-A+C by default; Vivaha, Bhratri/Bhratru, and Roga do not reverse
- Makes day/night Varsha Pravesha treatment explicit.
- Classical Janma Panchaka span: Dhanishtha p3-4 through Revati; weekday table removed; activity-scoped DQ
- Avoids confident wrong weekday gates and over-rejection outside governed activities.
- 5-9 Bhakoot treated as refined non-dosha
- Preserves supportive nava-pancham treatment while keeping other bad pairs gated.