The relevant cusp decides whether timing should begin
The report derives the cusp sub-lord’s KP significations from the natal chart. If the event is not indicated, it stops there and says so.
KP Event Timing
Keep only the periods
Keep only the periods
that pass every KP gate.
Natal promise, dasha eligibility and Moon transit must agree before this report retains a period.
New version coming soon
See the Method
A period is shown only if all three answer “yes”
-
1
Is the event promised?
The relevant cusp sub-lord must signify the event houses.
-
2
Can the active dashas deliver it?
Mahadasha through Sookshma are checked using the same KP event rules.
-
3
Does Moon transit confirm it?
Only event-relevant KP star and sub intervals are retained.
✓Krishnamurti (KP) ayanamsa
✓Placidus / Semi-Arc houses
✓In-house NASA/JPL DE440 engine
✓Mean Node convention disclosed
Eight questions, not one vague “Finance” score
Each question has its own event houses, supporting houses and obstructing houses. The report does not reuse a broad domain label as if every event inside it were identical.
Career progress
Promotion or a meaningful step forward at work
Income and gains
Receipt, earnings or a concrete financial gain
Marriage and commitment
Marriage or a formal partnership, not relationship mood
Recovery and vitality
Recovery support rather than medical diagnosis
Property acquisition
Acquiring a home, land or property
Education progress
Admission, study progress or completing a defined course
Long-distance travel
A substantial journey rather than daily movement
Childbirth and family growth
Childbirth as a specific family event
Why the report can honestly return no period
Selectivity is the product. If one gate fails, the report explains the stopping point instead of filling the calendar.
The active hierarchy must carry enough event support
Mahadasha, Antardasha, Pratyantardasha and Sookshma are tested together. The current moment is never inserted merely because it is current.
Moon narrows eligible periods to local civil dates
The engine solves KP star/sub boundaries, intersects them with eligible dasha periods and projects the retained interval into the report timezone.
Four clear outcomes
Every event question ends with a clear answer. The report does not turn its evidence score into a probability claim.
Invalid input
The chart or requested range cannot be evaluated reliably.
Not indicated
The relevant natal promise does not support this specific event.
No selective signal
Promise exists, but dasha or transit agreement is insufficient in the requested range.
Timing windows
Up to three windows in date order, each with an evidence-strength score and its dasha/transit support.
Simple first. Evidence when you want it.
The first page answers the practical question. Advanced evidence remains available for users who want to audit the KP reasoning.
- ✓Full start and end dates; no month-only labels
- ✓Dasha lords through Sookshma
- ✓Retained Moon star/sub confirmation
- ✓Evidence-strength score, timezone and node convention
What the report does not claim
- It does not guarantee that an event will occur.
- It does not convert ranking into a probability.
- It does not call the first day of the search range a result by default.
- It does not present these periods as electional muhurta.
- It does not replace professional medical, legal or financial advice.
A 12-month report built to say less, with reasons
Use it to review specific event periods, then apply your own judgment and real-world constraints.
New version coming soonWe're reworking this report to make it even better. It's temporarily unavailable while we finish the new version — check back soon.
