Calculation transparency

Methodology & Sources

AstroSaki turns established paddhatis into reproducible calculations. Every selected source method remains visible as its own calculation layer, while the final interpretation is anchored in authentic Indian Vedic Astrology and Indian Vedic Numerology.

Vedic Astrology Birth Chart Calculation

  • Planetary longitudes are calculated from Swiss Ephemeris data after the entered local birth time is converted using the historical timezone for the selected birthplace.
  • The Indian Vedic Astrology view uses sidereal positions with Lahiri ayanamsa. The lunar nodes use the mean-node convention, with Ketu placed opposite Rahu.
  • Lagna, houses, planetary degrees, Nakshatra, Pada, Panchang and Vimshottari Dasha are derived from the same birth moment and coordinates.
  • KP uses Placidus houses with its star-lord and sub-lord framework; Lal Kitab uses its fixed-house convention. These supplementary views remain separate, while the final synthesis returns to the chart's Indian Vedic Astrology foundation of Rashi, Bhava, Nakshatra and Navagraha.

Vedic Numerology Calculation

  • Birth Number reduces the day of birth; Life Path Number reduces the digits in the complete date of birth.
  • Name reports use one disclosed Chaldean letter-value table. The final reduced number is then mapped to its Indian planetary ruler in a clearly labelled synthesis.
  • Lo Shu reports preserve a DOB-only 4-9-2 source grid, then show Birth Number and Life Path Number as a separate modern Indian overlay. Present, repeated, missing and all eight line states are disclosed before the final planetary synthesis.
  • Business Compatibility has two separate models. Business Partners uses a business-focused 55% DOB and 45% name structure: Birth Number 15%, Life Path Number 30%, each cross bridge 5%, professional Destiny Number 30%, Soul Urge 5% and Personality 10%. Business Name remains name-only: Business Destiny Number strength 40%, owner-business Destiny Number alignment 40%, Soul Urge 10% and Personality 10%.
  • Love Partner Compatibility uses a love-focused 65% DOB and 35% name structure: Birth Number 30%, Life Path Number 25%, each cross bridge 5%, Destiny Number 25%, Soul Urge 7% and Personality 3%. The weights are a disclosed AstroSaki interpretation model derived from Vedic number roles, not a claimed classical percentage table.
  • The mobile-number index uses an exact 10-digit number and required DOB: complete mobile root 55%, Birth Number-ruler friendship 15%, Life Path Number-ruler friendship 15%, and five fixed two-digit sets 15%. Independent 8th/9th/10th Karm, Madad and Parinam strengths remain visible but do not contribute to the final score. These are disclosed modern weights, not classical percentages.
  • The vehicle index converts the complete legal plate with Chaldean English-letter values and face-value digits. With DOB, its vehicle-specific complete root contributes 55%, adjacent full-plate sequence 15%, Birth Number alignment 15% and Life Path Number alignment 15%; without DOB, a clearly general 80% root and 20% sequence model is used.

The AstroSaki Vedic final-result standard

A calculation system answers how the number or chart value was produced. The Indian Vedic synthesis answers how AstroSaki interprets that final value. We do not rewrite a Chaldean, KP, Lal Kitab or Lo Shu method and call it Vedic. We preserve and disclose the source method, then add a separate Indian Vedic Astrology or Indian Vedic Numerology layer based on planetary rulership, planetary friendship, Rashi, Bhava and Nakshatra.

Reference framework

Swiss Ephemeris

Astronomical positions, houses and calculation conventions used by the chart engine.

Classical Jyotish texts

Traditional concepts cross-checked against works such as Brihat Parashara Hora Shastra and Phaladeepika.

Krishnamurti Paddhati readers

KP house, star-lord and sub-lord terminology and calculation structure.

Traditional number tables

The Chaldean name table and Lo Shu birth-date grid are handled as distinct source methods.

Quality and editorial review

Calculation changes are covered by automated tests and reviewed against known inputs before release. The AstroSaki publisher is responsible for this review and keeps mathematical output separate from explanatory text so a copy change cannot silently alter a result.

Every public numerology calculator also displays its last material content-and-method review date, required inputs, exact calculation summary, verification checklist and scope limits. A date changes only when the page content, formula, structured data or important internal links receive a meaningful review—not when a copyright year changes.

Numerology guides preserve their original publication date and carry a separate editorial review date and review note. Calculator links are selected through a maintained topical relationship map: every linked method must explain what additional input or perspective it contributes. Generic “click here” links and unrelated calculator lists are not treated as editorial connections.

Corrections policy

If a displayed equation cannot be reproduced, a source system is labelled incorrectly or an explanation conflicts with the implemented rule, use the contact form and choose “Calculation issue.” Include the calculator URL, entered values, result shown and expected arithmetic. The publisher reviews reproducible reports, corrects confirmed errors and updates the affected page’s material-review date.

Limitations and responsible use

AstroSaki faithfully implements the established rules of every disclosed paddhati. The final result follows authentic Indian Vedic Astrology and Indian Vedic Numerology principles, supported by classical Jyotish references and documented Navagraha relationships. These traditional interpretations are not guaranteed forecasts. A result may change when the birth time, birthplace, spelling or selected calculation system changes. Use the reports for knowledge, study and personal reflection—not as medical, legal, financial or psychological advice.

Calculator inputs are processed to generate the requested result and are not stored as personal chart records. For broader data-handling details, read our Privacy Policy.