The KP System (Krishnamurti Paddhati)

What is Krishnamurti Paddhati?

Krishnamurti Paddhati — KP — is the system built by K. S. Krishnamurti in mid-twentieth-century Tamil Nadu. It is not a different astrology so much as a different resolution of the same astrology.

Classical Vedic technique often lands on a sign: a planet is in Aries, ruled by Mars, so read Mars. KP’s objection is that a sign is 30° wide, and two people born twenty minutes apart share almost every sign placement while living quite different lives. KP’s answer is to keep subdividing until the divisions are small enough to tell those two people apart — and then to hang the entire judgement on the smallest division that matters, the sub.

The rest of KP follows from that one move.

The sub: nine unequal parts of a nakshatra

Every nakshatra spans 13°20′ and has a star lord from the Vimshottari sequence. KP divides that nakshatra into nine subs, one per lord, in the same order — and crucially, sized in proportion to each lord’s Vimshottari dasha years. They are not nine equal ninths. Venus, with 20 of the 120 years, gets a sub more than three times the width of Sun’s.

Here is Ashwini — star lord Ketu, so the sequence starts at Ketu — exactly as this app computes it:

Nine subs × 27 nakshatras = 243 subs across the zodiac. Every other nakshatra works identically; only the starting lord rotates, so Bharani’s table starts at Venus, Krittika’s at Sun, and so on.

Then it recurses. Each sub divides into nine sub-subs by the same proportions, each sub-sub into sookshmas, each sookshma into pranas. So any longitude resolves to a five-deep chain:

star → sub → sub-sub → sookshma → prana

AstroShruti computes all five levels by default. The deeper two are refinement; in practice the sub lord carries the verdict and the star lord names the source.

The KP ayanamsha, and why it is not yours

Sidereal astrology needs an ayanamsha — the offset between the tropical and sidereal zodiacs. Most of this app defaults to Lahiri, and Advanced Settings lets you pick from a long list.

The KP pages ignore that setting. They force the KP (Krishnamurti) ayanamsha, and they force Placidus houses. If your account is set to Lahiri and Whole Sign, the KP tabs still hand back KP and Placidus, and say so in the response.

This is not the app being opinionated for its own sake. A sub is 0°40′ wide at its narrowest. The gap between Lahiri and KP is around a tenth of a degree — small, but a meaningful fraction of a sub, and easily enough to move a planet from one sub lord to the next. A “KP chart” computed on a Lahiri zodiac would have KP sub lords that KP itself would not recognise. There is no half-way house here, so the app does not offer one.

Houses: the cusp is the start, not the middle

This is the other place KP quietly departs from Vedic habit, and it surprises people.

In the Sripati bhava-chalit convention, a cusp is the madhya — the middle of the house — and the house runs from one sandhi (the midpoint between cusps) to the next. In KP the cusp is the commencement of the house. A planet belongs to the house whose [cusp, next cusp) arc contains it.

AstroShruti computes the Sripati sandhis too, but only as information: they drive a “near junction” flag on a planet sitting close to a boundary. They never decide which bhava a planet is in. That decision is always cusp-to-cusp — which is what makes the app’s KP houses line up with other KP software rather than with the Vedic chart in the next tab.

The practical consequence: a planet can be in a different house in the KP tab than in your Lagna chart, and neither is wrong. They are answering to different conventions.

What the sub lord actually decides

Once every point has a lord chain, KP’s rules are short:

• The star lord is the source. A planet gives the results of the houses its star lord occupies and owns — before its own.
• The sub lord is the verdict. It can confirm what the star lord promises or refuse it. For any question, KP goes to the relevant cusp’s sub lord and asks whether it signifies the houses that event needs.
• Rahu and Ketu own no signs. They represent — through the house they occupy, their sign lord, their star lord, and planets conjoined with them. The app makes each of those agents individually configurable, because schools genuinely differ on which ones count.

The ranking the app applies, strongest first: star lord’s occupation → star lord’s ownership → the planet’s own occupation → its own ownership → its sub lord as a modifier → node representation. Every house in a result carries the reason it got there, so you can read the chain rather than trust it.

That machinery is spelled out in Grah Nirdeshan and Bhaav Nirdeshan; the cusp-by-cusp version is Cuspal Interlinks.

A note on the KP dasha dates

If you compare the Vimshottari dates in the KP tabs against the standalone Dasha tab, they will not match. They are typically about a fortnight apart. This is worth explaining, because it looks exactly like a bug.

The dasha engine is the same one in both places. The Moon is not. The Dasha tab honours your ayanamsha (Lahiri by default); the KP tabs force KP. Roughly 0.1° of ayanamsha difference moves the Moon’s position by enough to shift a Mahadasha boundary by around two weeks.

We keep the KP tabs on the KP Moon deliberately. KP is self-consistent by ayanamsha: the star and sub lords these periods get read against are themselves KP-ayanamsha quantities. Timing them off a Lahiri Moon would produce dates that agree with the Dasha tab and agree with nothing else in the KP chart — the internal inconsistency would be worse than the visible discrepancy. The decision is pinned by tests, so it survives future tidying.

If you want Vimshottari dates on your own ayanamsha, the Dasha tab is the one to read. If you are working a KP judgement, use the KP dates.

Notes on what this app computes

• Ayanamsha: KP (Krishnamurti), forced on all KP pages regardless of your settings. Reported in every KP response.
• House system: Placidus, forced, with cusps read as house starts.
• 243 subs, sized by Vimshottari proportion — and 249 divisions once sign boundaries are counted in, which is the basis of KP Horary.
• Chain depth: five levels (star → prana) by default.
• Node rules are configurable; aspect-based and dispositor-sign representation are deliberately not implemented.