Ayanamsa Baseline
ValidatedThe sidereal (Lahiri / Chitrapaksha) ayanamsa is the first gate: it must agree with the reference to within a tight arcsecond tolerance before any downstream position is trusted.
Tolerance: ayanamsa ≤ 2″.
Horoscope positional validation passed across every curated check.
DevDarsha Horoscope accuracy is measured as positional and structural correctness of sidereal (Lahiri) Jyotish calculations — grahas, lagna, nakshatra, pada, the D9 navamsa, and Vimshottari dasha — checked against curated public reference charts. It is a phase-1 snapshot, not a prediction claim.
DevDarsha Horoscope is validated against curated public Jyotish reference charts for deterministic sidereal calculation, with 100% of curated positional checks passing at the phase-1 corpus. This is positional and structural validation only — it is not a prediction-accuracy claim.
Snapshot, not a live metric. The figures on this page are a validation snapshot as of 2026-06-30. The curated corpus is intentionally small and growing; future snapshots will expand it. Please independently verify outputs before relying on them for any high-stakes decision.
Want the full explanation? Read the Horoscope methodology guide.
Live Panchang Production API with published release-validation snapshot. View →
Live Horoscope / Kundli Certified deterministic engine, now live. You are here.
Live Numerology Live validation surface. View →
15 / 15 Curated public reference charts validated (phase-1 target met) Source →
100% Curated positional checks passed, 363 / 363 (grahas, lagna, anchors) Source →
≤ 2″ Ayanamsa tolerance vs references; grahas ≤ 1′, nodes ≤ 2′ Source →
Deterministic Byte-identical output for identical birth input Source →
What “accuracy” means here. We publish a verifiable public manifest with a SHA-256 integrity hash. It summarizes the phase-1 positional validation result against curated public reference charts without exposing internal implementation artifacts. Open the manifest at /accuracy-manifest-horoscope.
Verification Layers
Each output category is validated for exact or tolerance-bounded agreement with curated public Jyotish reference values. Learn how we validate.
Graha & Lagna Positions
ValidatedSidereal sign for the nine grahas (including Rahu/Ketu) and the ascendant is checked for exact agreement with curated references across the corpus.
Grahas 345 / 345 and lagna 13 / 13 curated checks passed (100%).
Nakshatra & Pada
ValidatedNakshatra and pada are checked for exact equality with curated references as part of each graha's positional evaluation.
Exact-match nakshatra + pada across curated charts.
Divisional Chart D9
ValidatedThe public divisional contract is D1 + D9 only. The navamsa (D9) sign is checked for exact agreement with curated references.
D1 + D9 only; exact navamsa sign match.
Dasha Sequence
ValidatedThe Vimshottari birth dasha lord is checked for exact agreement, and the birth balance within a small tolerance for source rounding.
Birth lord exact; balance within ±0.1 years.
Deterministic Output
ValidatedFor a fixed birth input the engine returns byte-identical output across repeated calls. Interpretation content is deterministic framing, not a forecast of real-world events.
Repeat-call output is byte-identical.
Corpus & Coverage
The accuracy basis is curated public Jyotish reference charts — not Swiss Ephemeris, and not a prediction model.
Basis: curated public Jyotish reference charts Ayanamsa: Lahiri (Chitrapaksha), sidereal Corpus stage: phase 1 — 15 charts Independent Sun-sign anchors: 5 (Sankranti dates) Divisional contract: D1 + D9 only Roadmap: 15 → 50 → 100+ charts The curated corpus is intentionally small and growing; coverage expands with each validation cycle. This is a calculation-validation basis, not a prediction-accuracy claim.
Release Gate
Every engine release is gated on the full curated regression before deployment. No update ships unless it passes all existing curated checks, and new reference charts are added as the corpus grows.
Verify it yourself
Open the public Horoscope accuracy manifest, a verifiable JSON snapshot with a SHA-256 hash for integrity checking. It lists the validated sections, tolerances, corpus stage, and the public validation boundary.