Panchangam Reference

Homahuti and Agnivasa election ​

personal.homa-election

Solar/lunar Nakshatra and Tithi/Vaaram remainders produce Homa offering guidance.

Assurance ​

LevelCurrent statement
Documented and traceableYes — the canonical record includes the process and a worked example.
Regression or reproduction checkedLinked to 2 repository test file(s).
Independently source-supportedAvailable only for the explicitly named provenance claims or comparison cells.

Computation method ​

Method type: formula

Apply two conjunctive hard gates: the lunar Nakshatra must fall in a benefic three-star Homahuti group counted from Surya, and the Tithi/Vaaram Agnivasa remainder must be zero or three.

Process ​

  1. Count lunar Nakshatra cyclically from solar Nakshatra and divide the 27-star cycle into nine groups of three.
  2. Map the group to its Graha lord and require Budha, Shukra, Chandra, or Guru.
  3. Convert full Tithi to ordinal 1-30 and Vaaram to Sunday-based ordinal 1-7.
  4. Compute the modulo-four Agnivasa remainder and require 0 or 3.
  5. Admit only when both requirements pass.

Formulae ​

Homahuti and Agnivasa ​

text
group=floor(((N_moon-N_sun) mod 27)/3)+1; a=(T+1+V) mod 4
  • T: full Tithi ordinal 1-30
  • V: Sunday-based weekday ordinal

Worked example ​

Shukla Pratipat on Sunday, Ashvini Sun and Ardra Moon ​

Inputs

  • Solar Nakshatra: Ashvini
  • Lunar Nakshatra: Ardra
  • Tithi ordinal: 1
  • Vaaram ordinal: 1

Calculation

  1. Ashvini-to-Ardra falls in group 2, ruled by benefic Budha.
  2. (1 + 1 + 1) mod 4 = 3, an admitted remainder.
  3. Both hard gates pass.

Result

  • Admitted: true

Method notes ​

  • Consumers must use the admitted boolean; the existing human reason string overstates earth residence when the remainder gate fails.

Contract ​

Owning layer: personal
Claim kind: textual-rule
Time basis: Evaluated for the candidate slot.

Inputs ​

  • solar Nakshatra
  • lunar Nakshatra
  • Tithi
  • Vaaram

Outputs ​

  • Homahuti group/lord
  • Agnivasa remainder
  • admission guidance

References and evidence ​

Evidence classes: textual
Verification states: verified

The exact Homahuti and Agnivasa rules have registered locators.

muhurta.homahuti ​

Evidence class: textual
Verification state: verified
Locator: Nakshatra-prakarana, 'Homahuti Muhurta' and 'Agnivasa,' verses 35-36, printed pp. 43-44 (OCR lines 2773-2796 in the Internet Archive full text)
Last reviewed: 2026-07-22
Scope: Implements both conjunctive tests in verses 35-36 as hard gates. Homahuti counts the Moon's Nakshatra inclusively from Surya's Nakshatra in nine successive groups of three, assigned to Surya, Budha, Shukra, Shani, Chandra, Mangala, Guru, Rahu and Ketu; groups of the natural benefics Budha, Shukra, Chandra and Guru are admitted. Agnivasa numbers Tithis 1-30 from Shukla Pratipat and weekdays 1-7 from Sunday, adds one to the Tithi count, and admits modulo-four remainders 3 or 0, which place Agni on earth. The activity is deliberately scoped to a Homa offering (Homahuti), not every Yajna; rite-specific Kalpa and Sampradaya requirements remain manual.

Sources ​

  • Muhurta Chintamani — Rama Daivajna; Undated Sanskrit text with Hindi commentary, Internet Archive identifier muhurta-chintamani-hindi; authority type: primary_text_hindi_commentary

The complete machine-readable source registry is available in provenance.json. A regression fixture or same-code reproduction is not independent verification.

Reproduce and review ​

Run the linked tests, then the complete offline contract:

bash
python tools/verify_project.py

Public surfaces ​

  • python-library
  • mcp
  • website

Limitations ​

  • This is election guidance and does not replace ritual prerequisites or a qualified practitioner; the current low-level reason list labels every Agnivasa remainder as earth-resident even when the admission gate fails, so consumers must rely on the admitted boolean until the tracked transparency fix lands.

Implementation ​

This route is generated from computations.json. Edit the registry and canonical reference prose in the same pull request as a behavior change.