Gaja Kesari Yoga: Jupiter positioned in a Kendra house (1st, 4th, 7th, 10th) measured relative to the Moon's placement.
Condition: $((House_{Jupiter} - House_{Moon} + 12) \pmod{12} + 1) \in \{1, 4, 7, 10\}$
Enhancement: Jupiter is exalted or in its own sign. Neutralization: Jupiter is combust, or the Moon is heavily waned (within 72° of the Sun).
Adhi Yoga (Lagnadhi / Chandradhi): Benefics (Mercury, Jupiter, Venus) positioned in the 6th, 7th, and 8th houses measured from either the Lagna or Moon. Yields exceptional strategic dominance and protection against systemic failures.
Kemadruma Yoga: Evaluated when there are no planets (excluding Sun, Rahu, and Ketu) in both the 2nd and 12th houses relative to the Moon.
Condition: $Count(Planets \in \{House_{Moon}-1, House_{Moon}+1\}) == 0$
Cancellation Pattern: If any planets are in a Kendra from the Ascendant or Moon, the yoga is mathematically cancelled (Kemadruma Bhanga), turning structural vulnerability into resilience.
4. Transit (Gochara) Logic Engine & Muhurta Optimization
For a Muhurta application, a static natal yoga is merely latent capability. Transits act as time-varying wave functions that trigger or suppress these configurations. The structural calculus requires evaluating the transiting coordinate space over the natal frame.
4.1 Planetary Transit Vedha (Obstruction) Matrix
Planets in transit distribute positive or negative metrics relative to the natal Moon's rashi. However, if another transiting planet occupies a specific Vedha house position concurrently, the transit's influence is temporarily obstructed.
Planet ID
Benefic Transit Houses (From Moon)
Corresponding Obstruction (Vedha) Houses
Exemptions & Core Rules
0 (Sun)3, 6, 10, 119, 12, 4, 5No Vedha between Sun and Saturn.
1 (Moon)1, 3, 6, 7, 10, 115, 9, 12, 2, 4, 8Exempt from native structural limits.
2 (Mars)3, 6, 1112, 9, 5Direct physical blockages if Vedha active.
3 (Mercury)2, 4, 6, 8, 10, 115, 3, 9, 1, 8, 12Intellectual processing delays under Vedha.
4 (Jupiter)2, 5, 7, 9, 1112, 4, 14, 10, 8Note: House 14 maps to House 2 in cyclic wrapping.
5 (Venus)1, 2, 3, 4, 5, 8, 9, 11, 128, 7, 1, 10, 9, 5, 11, 3, 6Complex interlocking arrays.
6 (Saturn)3, 6, 1112, 9, 5No Vedha between Saturn and Sun.
4.2 The Ashtakavarga Dynamic Filter
A transiting planet passing through a house that possesses low Ashtakavarga B बिंदु (Bindus) in its specific planetary chart (Bhinnashtakavarga) cannot activate a beneficial natal yoga. The operational algorithm for Muhurta verification is defined below:
def verify_transit_trigger(transit_planet, target_house, natal_chart, transit_chart):
# Step 1: Check baseline natal availability of the yoga
if not natal_chart.has_yoga_relationship(transit_planet):
return "No Natal Base Connection"
# Step 2: Validate current Bhinnashtakavarga Bindu Count for the planet in that house
bindu_score = natal_chart.get_ashtakavarga_bindus(transit_planet, target_house)
if bindu_score < 4:
return "Ineffective - Insufficient Bindu Energy Field (< 4)"
# Step 3: Parse Vedha Interception Matrix
if is_obstructed_by_vedha(transit_planet, target_house, transit_chart):
return "Blocked - Vedha Interception Asserted"
# Step 4: Evaluate transit structural integrity (Combustion/Debilitation)
if transit_chart[transit_planet]['is_combust']:
return "Functional Malefic - Distorted by Combustion"
if bindu_score >= 6:
return "Enhanced / Peak Activation Window"
return "Functional / Effective"
5. Software Application Logic Engine Architecture
To program this logic into a real-time computation engine for Muhurta selection, implement a decoupled evaluation pipeline. The calculations process a series of matrices from raw planetary coordinates down to actionable binary state evaluation objects.
5.1 Complete Structural JSON Data Schema
Below is the standard JSON layout required by the calculation pipeline to validate all structural conditions from BPHS, Saravali, and Jataka Tattva simultaneously.
{
"calculation_metadata": {
"jd": 2461192.91,
"ayanamsha_value": 24.23412,
"timestamp_utc": "2026-06-01T10:19:00Z"
},
"ascendant": {
"rashi": 6,
"longitude_in_rashi": 14.5212
},
"planetary_positions": {
"0": { "name": "Sun", "rashi": 2, "house": 9, "longitude": 16.2231, "is_retrograde": false, "is_combust": false },
"1": { "name": "Moon", "rashi": 8, "house": 3, "longitude": 4.1102, "is_retrograde": false, "is_combust": false },
"4": { "name": "Jupiter", "rashi": 4, "house": 11, "longitude": 5.0021, "is_retrograde": true, "is_combust": false }
},
"house_cusps": {
"1": { "start_rashi": 6, "center": 15.0 },
"2": { "start_rashi": 7, "center": 15.0 }
}
}
5.2 Logic Core Pipeline
Coordinate Processing Stage: Ingest epoch timestamps, apply Ayanamsha correction, compute absolute longitudes ($0^{\circ}$ to $360^{\circ}$), and map planetary coordinates to their respective houses and signs based on the selected house-cusp system (e.g., Shripati or Equal House).
State Assignment Stage: Evaluate positional properties to flag states such as combustion, retrogradation, Graha Yuddha victory/defeat, and directional strength (Dig Bala).
Yoga Evaluation Stage: Run the structural array algorithms against the processed state data. This stage maps the spatial rules defined in BPHS and Saravali, processing structural dependencies and cancellations (such as Neechabhanga).
Transit Verification Stage: Project the target time vectors onto the natal baseline. Calculate the current house positions from the natal Moon, evaluate the dynamic Vedha matrix, check Ashtakavarga thresholds, and output the final structural score.
Architectural Core Specifications Document • Structured for Automated Systems Engineering.