VELS Astrology 301

Kundali Summary N/A

Not a new calculation at all — a five-minute digest pulling together the platform's most-asked-about data points into one screen, and the default landing tab of the whole dashboard.

This aggregation view combines already-computed data from elsewhere: quick facts (Sun/Moon sign, Nakshatra+Pada, Ascendant), your current Dasha widget embedded unmodified, a condensed 4-line Personality Axes readout (Lesson 24 — dominant category only, not the full percentages), and a condensed Numerology line (just the Life Path number). It deliberately computes nothing new: it calls the exact same functions and endpoints as each full tab, then displays a smaller slice of the identical result.

Worked example: a seeker's full Personality Axes tab shows Guna as Sattva 43% / Rajas 29% / Tamas 29%. The Kundali Summary card doesn't repeat those percentages — it shows only "Guna: Sattva" (the dominant category) alongside "Varna: Kshatriya," "Graha Linga: Purusha (Masculine)," and "Tattva: Agni (Fire)," one line each. Clicking "Explore in Detail" jumps straight to the full tab, where the complete breakdown becomes visible. A common mix-up: this tab doesn't run its own lighter-weight version of anything for speed — there is no separate, faster, or less-accurate "summary" computation happening anywhere in this section.

Shadbala — Six-Fold Planetary Strength High

Ask any serious Jyotish practitioner "how strong is this planet, really?" and this is the classical answer they're formally reaching for.

Shadbala ("six strengths") sums five verified strength measurements into one number per planet, expressed in Rupas (1 Rupa = 60 Virupas, or Shashtiamsas), then compares that total against a classical minimum threshold — different for every planet — to judge whether it's strong enough to deliver reliable results on its own.

The five components: Sthana Bala (positional strength — itself five smaller parts, including exaltation proximity), Dig Bala (directional strength by house), Kala Bala (temporal strength — day/night, lunar phase, and more), Chesta Bala (motional strength, including retrograde), and Naisargika Bala (each planet's fixed natural strength rank). The sixth classical component, Yuddha Bala (planetary war), is left out — three irreconcilable classical descriptions of how to determine the "winner" between two close planets turned up during research, so it's dropped rather than guessed.

Worked example: the classical minimum requirement is planet-specific, not one shared bar — Sun and Jupiter each need 6.5 Rupas, Moon needs 6.0, Mercury needs 7.0 (the highest of the seven), Mars/Venus/Saturn need 5.0–5.5. A Jupiter totaling 390 Virupas converts to 390÷60 = 6.5 Rupas — landing exactly on its own threshold, the boundary case between "sufficiently strong" and "below threshold." A common mix-up: a Mercury and a Mars scoring an identical raw Rupa total aren't equally strong — Mercury's 7.0-Rupa bar is a full 2 Rupas higher than Mars's 5.0, so the same raw number can be comfortably above threshold for one and clearly below for the other.

Bhavabala — House Strength High

Shadbala tells you how strong a planet is — Bhavabala asks the same question of a house.

Bhavabala combines exactly two verified components: Bhavadhipati Bala (that house's own sign-lord's already-computed Shadbala total) with Bhava Drishti Bala (a simplified net aspect value — 15 Virupas, a quarter Rupa, added for every natural benefic aspecting the house, subtracted for every natural malefic).

Worked example: a house's lord has a total Shadbala of 380 Virupas. Two natural benefics (Jupiter, Venus) aspect the house, one natural malefic (Saturn) also aspects it: Bhava Drishti Bala = (+15)+(+15)+(−15) = +15 Virupas. Total Bhavabala = 380+15 = 395 Virupas = 395÷60 = 6.58 Rupas for this house. A common mix-up: Bhavabala doesn't include a "natural strength of the sign" component the way Shadbala includes Naisargika Bala for planets — it's built from exactly two verified components. A third classical component, Bhava Dig Bala (positional strength by house), is deliberately left out — independent research found two conflicting classical formulas for it, with no reliable third source to adjudicate.

Divisional Charts, the Full Set High

The complete technical reference for Track A's "zoom level" idea — every Varga VELS actually computes, laid out side by side.

Beyond D1 and D9 (shown elsewhere), this displays every planet's sign placement across 7 more Vargas: D2 Hora (wealth), D3 Drekkana (siblings/courage), D4 Chaturthamsa (property/fortune), D7 Saptamsa (children), D10 Dashamsa (career), D12 Dwadasamsa (parents/lineage), and D30 Trimshamsa (misfortunes/weaknesses).

Worked example: a planet at 5° Leo (an odd sign, 5th from Aries) for D10 — odd signs count their ten 3° segments starting from the sign itself, so segment = floor(5÷3) = 1, giving Leo+1 = Virgo. The same 5° position in Cancer instead (an even sign) counts its segments starting from the 9th sign from it, Pisces, giving Pisces+1 = Aries — an entirely different D10 sign purely because Cancer is even and Leo is odd, even with an identical degree-in-sign. A common mix-up: not every divisional chart simply counts forward from the planet's own sign the way D3 genuinely does — D7 and D10 both apply this odd/even rule where even signs start their count from a different sign entirely (the 7th-from for D7, the 9th-from for D10).

Vimshopaka Bala — 20-Point Divisional Strength High

A single, clean 0–20 score answering: across every meaningful chart this planet appears in, how consistently well-placed is it?

This weights a planet's dignity across the 7 classical divisional charts from Track A (D1, D2, D3, D7, D9, D12, D30 — the Saptavarga set), each contributing a fixed, unequal weight: D1=5.0, D12=4.5, D3=3.0, D9=2.5, D2=2.0, D30=2.0, D7=1.0 — summing to exactly 20. The planet's dignity tier in each Varga (via Panchadha Maitri from Track A) converts to points: own sign=20, great friend=18, friend=15, neutral=10, enemy=7, great enemy=5, debilitated=0.

Worked example: D1 own-sign (20×5.0÷20=5.0), D2 friend (15×2.0÷20=1.5), D3 neutral (10×3.0÷20=1.5), D7 great friend (18×1.0÷20=0.9), D9 own-sign (20×2.5÷20=2.5), D12 enemy (7×4.5÷20=1.575), D30 neutral (10×2.0÷20=1.0). Summed: 5.0+1.5+1.5+0.9+2.5+1.575+1.0 = 13.98 out of 20 — strong dignity in the two highest-weighted charts (D1 and D9) pulling the average up despite a middling D12 result. A common mix-up: a planet doesn't need to be well-dignified in all seven charts to score well — because the weights are deliberately unequal (D1 and D12 alone account for 9.5 of the 20 points), a mediocre score in a lightly-weighted chart like D7 (worth only 1.0) barely moves the total.

Ashtakavarga — The Full Bindu System High

The full technical version of Track A's "8 sources per sign" idea — every one of the 7 classical planets casting a Bindu vote into every sign, for every other planet.

For each target planet, a fixed classical rule table specifies — for each of 8 reference points (the 7 planets plus the Lagna itself) — which houses, counted from that reference point, earn a Bindu when the target planet's sign falls there. Each of the 8 sources has its own distinct list of contributing houses for each of the 7 target planets: 56 separate lists in total, not one shared rule.

Worked example: computing the Sun's BAV bindu for Leo, with the 8 sources at Sun/Aries, Moon/Cancer, Mars/Leo, Mercury/Aries, Jupiter/Sagittarius, Venus/Pisces, Saturn/Aquarius, Lagna/Libra — for each source, count the house-from-source to Leo, then check whether that house appears on the Sun's bindu-list for that specific source. Mars sits in Leo itself (Leo is Mars's 1st house), and 1 is on Mars's list of houses that earn the Sun a bindu — contributing +1. Running this for all 8 sources yields bindus from Mars, Mercury, Jupiter, Venus, Saturn, and Lagna (6 of 8), for a Sun-BAV of 6 in Leo — one sign's contribution toward the Sun's fixed 48-point total across all twelve signs. This produces a per-planet BAV grid, summing into a combined Sarvashtakavarga (SAV) total per sign — the exact mechanism behind the "quantitative veto layer" the Full Report (Lesson 39) uses to resolve conflicting signals. A common mix-up: Ashtakavarga describes sign-level general strength, not a specific planet's personal dignity — that's Track A's exaltation/debilitation's job.

Personality Axes Medium-High

Four classical category splits, computed entirely from data the platform already has loaded — but three of the four are the same for almost everyone, and that's worth understanding before reading too much into them.

Guna (Sattva/Rajas/Tamas), Varna (Brahmin/Kshatriya/Vaishya/Shudra), and Graha Linga (Purusha/Prakriti/Napunsaka) are each a fixed classical table mapping a specific planet to a specific category — Jupiter, Sun, and Moon are always Sattva; Saturn and Mars are always Tamas — and none of the three depend on which sign a planet is in. Only the fourth axis, Tattva (Fire/Earth/Air/Water), is genuinely chart-specific, since it's read from whichever sign each planet currently occupies. Every category is a flat, unweighted count divided by the total planets counted — no planet (not even the Sun, Moon, or Ascendant) counts more than any other.

Worked example: with all nine classical bodies present, Guna always splits 3 Sattva (Sun, Moon, Jupiter) / 2 Rajas (Mercury, Venus) / 4 Tamas (Mars, Saturn, Rahu, Ketu) = 33%/22%/44%, Tamas dominant — identical for every native who has all nine bodies counted, because Guna depends only on which planets exist, never on where they sit. Tattva alone changes chart to chart: a native with 4 planets in Fire signs, 2 Earth, 2 Air, 1 Water gets a genuinely personalized 44%/22%/22%/11% split. A common mix-up, worth correcting directly: three of the four axes are not uniquely personal the way Tattva is — barring a genuinely absent planet, every native gets an identical Guna/Varna/Graha Linga split, so treating them as "your personal Sattva percentage" overstates what's actually being measured.

Avakhada Chakra High

These five attributes are the exact building blocks of 201's 36-point matching system — shown here standalone, as your personal classical birth-constitution summary.

This displays the same five Nakshatra/Rashi-derived attributes used in Ashtakoota compatibility matching (Gana, Yoni, Varna, Vasya, Nadi) as a standalone personal profile. All of them are simply different columns of one fixed lookup table keyed to a single input — your Moon's Nakshatra (and, for a few fields, its Pada) — not independently calculated attributes each with their own formula.

Worked example: a native's Moon is in Ashwini, Pada 1. Because Ashwini is fixed classical lookup data, the module simply reads off Ashwini's pre-tabulated row: Nakshatra Lord Ketu, Gana Deva, Yoni Ashwa (horse), Nadi Adi, and so on through all fields. Change nothing except the Moon's Nakshatra, and the entire profile changes with it. A common mix-up: this isn't a separate calculation from Ashtakoota matching — it's the identical five underlying attributes, just displayed for one person instead of compared between two; the whole module is a lookup, not a calculator in the sense Shadbala or Ashtakavarga are.

Business / Group Synastry High Medium

201's Ashtakoota matching was built for two people — this extends the exact same engine to full business teams, up to 5 people at once.

For a group of 3–5 people, the full 8-Koot matching engine runs pairwise across every unique pair, following n(n−1)/2, not n. A dedicated Business Synastry scoring layer (financial alignment, operational synergy, communication harmony, ego alignment) is added specifically for partnership contexts.

Worked example: a 3-person team needs 3×2÷2 = 3 pairwise checks. A 4-person team needs 4×3÷2 = 6. A 5-person team, the platform's maximum, needs 5×4÷2 = 10 separate Ashtakoota calculations — each additional member adds disproportionately more work than the last, since group size grows linearly but pair count grows quadratically. A common mix-up: adding one more person doesn't add a roughly constant amount of computation — going from 3 members to 5 more than triples the pairwise check count (3→10), since every new member must be checked against every existing member individually.

Arudha Padas — How You're Perceived High

Jaimini's answer to a very specific question: not "what is true about your life," but "what does your life look like to everyone else?"

Find a house's own lord's position, count the distance from the house to the lord, then count that same distance forward again from the lord's position — the result is that house's Arudha Pada. A key exception: if this raw calculation would land the Pada on the house's own sign or its 7th, the result shifts by an additional 10 signs instead.

Worked example: for a Cancer Lagna with Moon (Cancer's own lord) also sitting in Cancer, the count-forward distance is zero, so the raw calculation would place the Arudha Lagna in Cancer itself — the house's own sign. The exception fires, shifting the result to the 10th sign from Cancer instead: Aries. A common mix-up: this exception isn't a rare edge case — any house whose lord sits in its own sign (a routinely strong, common placement) automatically triggers it, since a lord in its own sign always produces a zero-distance count that lands the raw pada back on the house's own sign.

Chara Karakas — Jaimini's Significators High

Forget "Venus always means relationships" — in Jaimini, which planet signifies what is unique to your exact chart, resorted from scratch every time.

This ranks the 7 classical planets (Rahu and Ketu excluded) by their exact degree-within-sign, ignoring which sign each is in — the highest degree becomes Atmakaraka (soul/self), on down to the lowest, Darakaraka (spouse/partnerships).

Worked example: seven planets at Mercury 27°, Sun 22°, Venus 19°, Moon 15°, Saturn 11°, Mars 8°, Jupiter 3° (degrees within their own signs). Sorted highest to lowest: Mercury → Atmakaraka, Sun → Amatyakaraka, Venus → Bhratrukaraka, Moon → Matrukaraka, Saturn → Putrakaraka, Mars → Gnatikaraka, Jupiter → Darakaraka. Note Mercury, not the Sun, becomes Atmakaraka here — the role goes strictly to whichever planet holds the highest degree in this specific chart. A common mix-up carried over from fixed Parashari significators (Sun=soul, Venus=spouse): the Atmakaraka isn't always the Sun, and a Karaka role isn't always held by the planet whose Parashari nature best matches it — the Sun could just as easily end up Darakaraka in one chart and Atmakaraka in the next.

Rāśi Drishti — Sign Aspects High

In Jaimini, it's not planets that look at each other — it's the signs themselves, structurally, permanently, regardless of who's standing in them.

Movable signs aspect all Fixed signs except the one immediately adjacent; Fixed signs aspect all Movable signs except the one adjacent; Dual signs aspect the other three Dual signs, with no adjacency exception needed since no two Dual signs are ever next to each other. Every sign aspects exactly 3 others — a fixed, chart-independent relationship, unlike Graha Drishti which depends on where a planet currently sits.

Worked example: Aries (Movable) aspects all four Fixed signs except the adjacent one, Taurus — leaving Leo, Scorpio, and Aquarius as its three targets, and each of those three aspects Aries right back (the relationship is symmetric). Sagittarius, a Dual sign, aspects the other three Dual signs — Gemini, Virgo, Pisces — with no adjacency exception at all. A common mix-up: the "skip the adjacent sign" rule only governs the Movable-Fixed relationship — it doesn't apply to Dual signs, which aspect all three others with no carve-out.

Chara Dasha — Jaimini's Timeline High

Jaimini's own complete answer to "when" — timing life through the 12 signs rather than through Nakshatras or planets.

Direction is genuinely easy to mix up: it is not the Movable/Fixed/Dual modality used for Rāśi Drishti or Navamsa. Instead, the twelve signs split into two fixed kendra-quadrant blocks of six: Aries, Taurus, Gemini, Libra, Scorpio, Sagittarius count forward; Cancer, Leo, Virgo, Capricorn, Aquarius, Pisces count backward. Each sign's dasha length = the distance counted (in the appropriate direction) from itself to its ruler's current sign, minus 1 year — a ruler sitting in its own sign is a fixed exception, automatically 12 years.

Worked example: Scorpio Lagna, a forward-counting sign with two co-rulers, Mars and Ketu. Suppose Mars sits in Scorpio itself (home) and Ketu sits elsewhere (away) — the "one home, one away" rule resolves to the away co-ruler, Ketu, as the true ruler for length purposes. If Ketu is in Cancer, counting forward from Scorpio to Cancer: Scorpio(1)→Sagittarius(2)→Capricorn(3)→Aquarius(4)→Pisces(5)→Aries(6)→Taurus(7)→Gemini(8)→Cancer(9) = 9 signs, so the Scorpio dasha runs 9−1 = 8 years. Had both co-rulers been in Scorpio (both home), the length would default automatically to 12 years, bypassing the distance count entirely. A common mix-up, confirmed directly during this platform's own build: assuming Chara Dasha's direction follows the same modality scheme taught for Rāśi Drishti — it doesn't; it's a distinct kendra-quadrant grouping that happens to split the zodiac differently.

Upagrahas — 10 Shadow Points High

Beyond the 9 Grahas, classical Jyotish tracks 10 more calculated points — no physical body at all, pure mathematical derivation from the Sun's position and the day's own timing.

The Kalavela group (including Gulika/Mandi) comes from dividing daylight (for a day birth) or night (for a night birth) into 8 equal segments, assigned to the 7 classical planets in weekday order — starting from that day's own weekday-lord for a day birth, or from the weekday-lord's fifth position in that sequence for a night birth. The 8th segment is always lordless. Gulika's longitude is the Ascendant degree rising at the exact start of Saturn's segment — not its midpoint.

Worked example: a day birth on a Sunday (weekday-lord Sun, which is first in the fixed sequence Sun-Moon-Mars-Mercury-Jupiter-Venus-Saturn, so no rotation needed): Sun=part 1, Moon=2, Mars=3, Mercury=4, Jupiter=5, Venus=6, Saturn=7 (the last lorded part before the always-lordless 8th). If sunrise is 6:00am and sunset 6:00pm (90 minutes per part), part 7 begins at 6:00am + 6×90min = 3:00pm — the Ascendant degree rising at exactly 3:00pm, not 3:45pm (the midpoint), is Gulika's longitude. A common mix-up: night births don't reuse the same weekday-to-segment mapping as day births — they start the sequence from the weekday-lord's fifth position, not its first, easy to miss if day and night births are assumed identical.

Special Lagnas High Medium

Your Ascendant isn't the only "Lagna" a chart has — classical Jyotish computes at least five, each answering a different, more specialized question.

Bhava, Hora, and Ghati Lagna share one identical mechanic: all three start from the Sun's longitude at that day's sunrise (not the natal Sun), then add an arc proportional to elapsed time — differing only in rate (Ghati: 1 sign per 1 Ghati; Hora: 1 sign per clock-hour; Bhava: 1 sign per 5 Ghatis). Pranapada Lagna is the one exception, anchored to the Sun's true natal longitude instead, with its own sign-modality correction.

Worked example: Sun at 15° Aries at sunrise. Birth occurs 4 hours after sunrise = 10 Ghatis elapsed (1 Ghati = 24 min). Ghati Lagna = 15° + (10×30°) = 315° = 10° Aquarius. Hora Lagna, at 1 sign per hour = 15° + (10×12°) = 135° = 15° Leo. Both share the identical 15° Aries starting point — they differ only in how fast the arc accumulates. A common mix-up: most Special Lagnas are not anchored to the Sun's actual natal position — Bhava, Hora, and Ghati all use that day's sunrise Sun instead, a fixed reference for the whole day; only Pranapada uses the true natal Sun, which is exactly why it needs its own separate correction step the sunrise-anchored trio don't.

Longevity / Ayurdaya High Medium

Classical Jyotish's most sensitive subject, handled the way VELS handles everything uncertain: compute only what's verified, name what isn't, and never present a category score as a death-date prediction.

Two classical methods run in parallel. Nisargayu assigns each of the 7 planets a fixed base-year value (Saturn highest at 50, Moon lowest at 1), scaled by a 0.5-to-1.0 multiplier tied to its Panchadha Maitri dignity tier. Pindayu instead uses an exaltation-value table, interpolated by the classical rule-of-three: full value exactly at exaltation, half value exactly at debilitation (180° away). Per BPHS Chapter 48, whichever of the Sun, Moon, or Lagna Lord has the highest Shadbala decides which method actually governs the chart.

Worked example: under Nisargayu, Jupiter's base is 18 years. If Jupiter is "Mitra" (friend) to its sign's lord — 15 of 20 Vimshopak points — its multiplier is 0.5+0.5×(15÷20)=0.875, giving 18×0.875 = 15.75 years. Under Pindayu, if that same Jupiter sits 60° from its own exaltation degree (a third of the way around the 180° exaltation-to-debilitation arc), its years = 15×(1−0.5×(60÷180)) = 12.5 years — two different numbers, because the two methods measure completely different things. A common mix-up: Ayurdaya doesn't work from house placements the way Manglik or Kaal Sarpa do — both methods are built entirely from dignity tier or exaltation-proximity, with no house-lordship logic at all, and the classification boundaries are 32/64/100, not the rounder 32/70 sometimes assumed. A third classical method, Amsayu, was tested and dropped after producing wildly inconsistent results on real charts (a ~6-year estimate against 93–99 years from the same chart).

Extended Doshas High Medium

Beyond 201's Manglik and Kaal Sarpa doshas, six more classical single-chart afflictions — each honestly labeled by how well-sourced it actually is, and one popular "dosha" deliberately left out.

Pitra Dosh, Grahan Dosh, Guru Chandal Dosh, Kemadruma Dosh (with real classical Bhanga/cancellation logic), Angarak Dosh, and Gandmool/Gandanta Dosh. Confidence is explicitly mixed and per-dosha: Kemadruma is High (directly attributed to BPHS); the other five are Medium. A commonly-marketed 7th "dosha," Shani Dosh, was researched and deliberately excluded — it functions as an umbrella marketing term across competitor sites with no crisply-bounded classical formula.

Worked example: a native's Moon is in Ashlesha, Pada 4 (the last quarter). Ashlesha is one of the six Gandmool Nakshatras, so this chart is flagged Gandmool — and because Ashlesha's last pada specifically sits at the extreme end of Cancer (water) transitioning into Leo (fire), a listed severe junction point, this escalates from a mild Gandmool flag to a full, severe Gandanta classification. A common mix-up: "Shakata Dosha" (Moon in the 6th/8th/12th from Jupiter) is a real classical concept, but it is not one of VELS's six implemented Extended Doshas — the actual six are Pitra, Grahan, Guru Chandal, Kemadruma, Angarak, and Gandmool/Gandanta.

Latta Dosha — Live Transit "Kick" Medium-High

Not a fixed feature of your birth chart at all — this one changes every single day, computed fresh against whatever the sky is doing right now.

Each transiting planet casts either a forward (Puro) or backward (Prishta) "kick" at a fixed Nakshatra-distance unique to that planet — Mars casts forward at offset 3, Jupiter forward at offset 6, the Moon backward at offset 22. If a planet's kick lands exactly on your birth Nakshatra, a Latta is flagged for that planet.

Worked example: birth Nakshatra Hasta (index 12). Transiting Mars is in Chitra (index 13); Mars's forward kick (offset 3, meaning 2 positions ahead) targets index 13+2=15=Swati — not Hasta, so no Latta from Mars today. Transiting Mercury is in Hasta itself (index 12); Mercury's backward kick (offset 7, meaning 6 positions behind) targets index 12−6=6=Punarvasu — also not Hasta, so this misses too. A Latta only forms on the specific day a transiting planet's own rule happens to land its target exactly on your birth Nakshatra. A common mix-up: this isn't a slow-moving condition like Sade Sati — because it's keyed to Nakshatra-by-Nakshatra transit position, a Latta from the fast-moving Moon can form and clear within about a day, while one from slow Saturn can persist for months.

Chart Sensitivity High

Answers a question most astrology software never even asks: exactly how wrong could your recorded birth time be before the results start changing?

For each verified divisional chart, this computes how many minutes of birth-time uncertainty would shift the Ascendant into the next division — using the real, instantaneous rise-rate of the Ascendant at your exact birth moment and location (via numerical differentiation of the ephemeris), not the commonly-used flat "1 degree per 4 minutes" approximation, which is only exact at the equator.

Beyond the raw per-Varga table, the dashboard also derives an Overall Stability Score (0–100) — a plain average of each scored Varga's sub-score (min(100, tolerance÷30×100)) — plus Very High / High / Moderate / Stable bucket labels per Varga (under 1 min / 1–5 min / 5–30 min / 30+ min), and names your single most-sensitive and most-stable Varga. When the Overall Score falls below 50, a verdict banner suggests birth-time rectification is worth considering, linking to the Nisheka Lagna Calculator and the Life Event Rectification tool (Lessons 37 and 40) — the same <50 cutoff convention used for corroboration-signal strength elsewhere on the platform. This synthesis layer is explicitly labeled a VELS convenience, not a classical BPHS measure — BPHS has no numeric "stability score" for a chart. A common mix-up: a low Overall Score doesn't mean your D1 chart itself is unreliable — it's an average across nine Vargas, so one fast-flipping fine division (like D30) can pull the number down even while your D1 and D9 stay comfortably Stable.

Nisheka Lagna — Conception Rectification High

Not your birth chart at all — a second, independently derived chart for the moment of conception, worked backward using three classical angular factors, not a simple 9-month subtraction.

The gestation length sums three factors: Factor A, the shortest angular distance between Saturn and Gulika (always 0°–180°, never the long way around); Factor B, the direct zodiacal distance from the Lagna to the 9th-house cusp; Factor C, a conditional Moon-degree term added only if the Ascendant Lord occupies houses 1 through 6 (the chart's "invisible half"). The sum is treated as Sauramana (solar-calendar) days — 360 per solar year — then rescaled into real civil days (since a true sidereal year is 365.2564 days, not 360) and normalized into the 250–310 day physiological window by adding or subtracting 30-day blocks.

Worked example: Saturn at 200°, Gulika at 340° — raw difference 140°, already under 180°, so Factor A=140°. Lagna at 10°, 9th-cusp at 190° — Factor B=180°. The Ascendant Lord sits in the 3rd house (the invisible half), so Factor C applies: Moon at 25° within its sign contributes 25°. Total = 140+180+25 = 345 Sauramana days. Rescaled: 345×(365.2564÷360) = 350.1 civil days — above the 310-day ceiling, so the engine subtracts 30-day blocks: 350.1−30=320.1 (still too high), −30 again = 290.1 days, now inside the 250–310 window. The Nisheka moment is the birth Julian Day minus 290.1 days. A common mix-up: this is not primarily a Moon-based calculation the way many other timing techniques in this book are — the dominant factors are Saturn's relationship to Gulika and the Lagna's relationship to the 9th cusp; the Moon only enters at all when the Ascendant Lord happens to sit in the first six houses, and even then it's a minor additive term.

Sade Sati Timeline (Precision) High

201's free Sade Sati Calculator tells you which phase you're in right now — this module tells you the exact calendar dates of every phase, past and future.

This tracks Saturn's exact retrograde loops and sign-boundary crossings relative to the natal Moon — not a simple sign-level generalization — computed once and cached, matching the platform's Whole Sign house system throughout.

Worked example: natal Moon in Leo. The simple version (201) shows three clean phases: Saturn in Cancer, then Leo, then Virgo. But suppose Saturn crosses from Cancer into Leo, then stations retrograde days later and drifts back into Cancer for weeks before resuming forward motion and re-entering Leo for good — the Timeline doesn't smooth this into one continuous "Leo phase." It reports four separate boundary-crossing segments (Cancer→Leo, Leo→Cancer, Cancer→Leo again, eventually Leo→Virgo), each with its own exact date, because the native genuinely experienced Saturn re-crossing that boundary twice. A common mix-up: a Timeline showing more than 3 segments in a cycle isn't a display bug — it's the expected, accurate result whenever Saturn stations retrograde close enough to a sign boundary to briefly cross back over it.

The Full Cosmic Blueprint Report

Every module in this entire curriculum, synthesized into one narrative document by an AI system operating under an explicit, ranked classical-authority hierarchy — not a generic "AI horoscope."

The platform's flagship paid deliverable is a 10-section report combining chart data already computed elsewhere — Dasha, house analysis, yogas, transits, divisional charts, Ashtakavarga, remedies — into AI-generated narrative, built on a large system prompt defining a strict authority hierarchy for resolving conflicting classical signals.

The resolution order: BPHS as Primary Structural Authority (house lordships, Shadbala, core Dasha cycles) → Pulippani as Primary Predictive Authority (heavy Gochara weighting) → Ashtakavarga as a Quantitative Veto Layer (a high Bindu count can soften an otherwise difficult prediction) → Jaimini's Arudha Padas as a Perception Layer → Saptarishi Nadi as Karmic Contextual Authority. If Vimshottari Dasha and a transit reading both point toward a difficult period, but the relevant sign carries a high Ashtakavarga Bindu count, the report's methodology treats that as real evidence the difficulty will be softened — not decoration, but an explicit, ordered step in how the narrative gets written.

This hierarchy is a real, load-bearing methodological choice — a large language model instructed to apply a specific, documented, human-authored priority order across five classical authorities when they'd otherwise disagree. Report generation is cached, and the free "summary" tier deliberately skips the full generation, using a smaller, separate narrative model instead.

Life Event Rectification High Medium

Rather than asking one calculation to carry the full weight of birth-time verification, this checks a known life event through seven classically independent lenses at once.

You submit a real, known life-event date — marriage, childbirth, graduation, divorce — and the tool checks it against seven independent signals reported side by side, never blended: your Parashari Dasha lord's relevance, the event's Jaimini Arudha Pada, Upapada Lagna (a second, structurally distinct Arudha point, scored for marriage/divorce), Jaimini's own Chara Dasha, a Double Transit from your Ascendant, the same Double Transit re-read from your Moon (Chandra Gochara), and divisional-chart dignity in the one Varga tied to that event type.

Rahu and Ketu, which own no sign and would otherwise score zero, are credited through the classical principle that a node "borrows" significance from whatever it conjoins and from its sign dispositor. Two signals also carry yoga-context awareness: Varga dignity recognizes Neecha Bhanga Raja Yoga, rescoring a genuinely-cancelled "debilitated" reading as neutral rather than zero; and the Parashari and Chara Dasha signals surface a plain qualitative note — never a score change — whenever the matched lord natally forms a Viparita Raja Yoga.

The most common misreading is treating any one of the seven percentages — especially the main Parashari one — as "the" rectification score. They're deliberately kept separate: Jaimini's own texts warn against blending Rāśi-Drishti-based logic with Graha-Drishti-based Parashari logic, and a weak reading on one signal with strong readings on others is a genuinely different diagnosis than uniformly weak or uniformly strong readings across all seven. This is a complementary, independent signal to Nisheka Lagna (Lesson 37) — anchored to your own biography rather than gestational-arc math.