Grah Nirdeshan (Planet Significators)

What Grah Nirdeshan answers

Take one planet. Ask: which houses of this chart will it actually deliver?

That is Grah Nirdeshan — planet direction, the planet-wise significator table. It is the first of the two significator views in KP; its mirror image is Bhaav Nirdeshan, which starts from a house and asks which planets serve it. Same facts, read from opposite ends.

The answer is not one house. A planet in KP typically stands for four to seven houses, and the whole point of the table is that they are not equal. So AstroShruti never returns a bare list — every house comes back with a rank and a sentence saying why it is there.

The levels, strongest first

This is the hierarchy the app computes, exactly as ranked:

Read ranks 1 to 4 again and notice what has happened. The planet’s own house comes third. Its own lordship comes fourth. Two levels of a different planet — the one that owns its nakshatra — sit above both.

This is not a quirk of our implementation. It is the load-bearing idea of Krishnamurti Paddhati: a planet is a lamp, and the star lord is the hand holding it. Where the star lord points is where the light falls.

Worked example

Suppose Mars sits in house 7, rules house 12, and lies in Mercury’s star — and Mercury sits in house 8 and rules houses 2 and 5.

• Rank 1: house 8 — Mercury (Mars’s star lord) occupies it.
• Rank 2: houses 2 and 5 — Mercury owns them.
• Rank 3: house 7 — Mars occupies it.
• Rank 4: house 12 — Mars owns it.

So Mars signifies 8, 2, 5, 7, 12 — and it signifies the 8th more strongly than the 7th it is sitting in. An astrologer reading Mars for a 7th-house matter here would be reading a planet whose primary business is the 8th.

That is the sort of reversal Grah Nirdeshan exists to catch, and why the app returns the reason string beside each house rather than just the numbers.

The fifth level, and why we flag it

Classical KP significator tables have four levels — the four above. AstroShruti computes a fifth: the planet’s sub lord’s houses, folded into the same set at rank 5.

We are being explicit about this because it is a departure. In orthodox KP the sub lord is the deciding factor rather than another rung on the significator ladder — it is what you consult to know whether a matter is promised at all, not something you add to a list of significations. Folding it in makes the app’s house set broader than the book’s.

The rank is the honest signal here. If you want the classical four-level reading, read ranks 1 to 4 and stop. Nothing is hidden from you; rank 5 is labelled rank 5.

One detail worth knowing: at rank 5 the sub lord contributes only the houses it occupies and owns. It does not recurse into its own star lord. The full recursion is what rank 1 and 2 already do for the planet in question, and doing it again one level down would inflate every planet’s set until it meant nothing.

Rahu and Ketu

The nodes own no signs. In KP they are not house lords, ever — the app’s ownership map is built from sign rulership, and no sign is ruled by a node. So the classical levels 2 and 4 are simply empty for them.

Instead they represent. By default AstroShruti gives a node the houses reached through four agents:

• the house the node occupies;
• the houses its sign lord occupies and owns;
• the houses its star lord occupies and owns;
• the houses of any planet sharing its house (conjunction).

Every one of those contributions carries its own reason string, so a node’s house list is auditable line by line rather than being a black box.

All four agents are switches. The API accepts a node_rule on the request, and two further agents exist in the contract but are off and unimplemented: aspect-based representation, and planets in the signs the node’s dispositor rules. We would rather ship four rules that work than six where two are guesses.

A limitation we will not paper over

There is a known gap, and you should hear it from us.

When a planet’s star lord is itself Rahu or Ketu, the app gives that planet only the node’s occupied house at rank 1 — and nothing at rank 2, since the node owns nothing. It does not pass the node’s full representation (its sign lord’s and star lord’s houses) up to the planet sitting in its star.

Much of the KP literature says it should: a planet in a node’s star is held to give the node’s results, and the node’s results are its representations. Our node representation is computed and returned in full — it just is not propagated upward through rank 1 in the current engine.

So for a planet in Ashwini, Magha, Mula, Ardra, Swati or Shatabhisha, treat the rank-1 entry as incomplete rather than wrong, and read the node’s own Grah Nirdeshan row beside it. We are stating this rather than quietly hoping you do not check.

What is fixed, and what you control

• Ayanamsha is KP and houses are Placidus, always. The KP pages override the ayanamsha and house system you may have chosen in Advanced Settings.
• A planet’s house is decided cusp to cusp — in KP a cusp is the start of a bhava, not its middle. This is the deliberate difference from the Vedic Sripati convention, and it is why a planet can land in a different house here than on the Grah Sthiti table.
• The sub lord depth is yours: the chain resolves to sub, sub-sub, sookshma or prana. Grah Nirdeshan only ever uses the sub.

Where to go next

• Bhaav Nirdeshan — the same data indexed by house.
• Cuspal Interlinks — every cusp’s lord chain resolved through this very table.
• Nakshatra — the 27 stars whose lords do the heavy lifting above.