Bhaav Nirdeshan (House Significators)

What Bhaav Nirdeshan answers

Pick a house — the 7th, say, for marriage. Ask: which planets can actually deliver it?

That is Bhaav Nirdeshan, house direction. It is the exact mirror of Grah Nirdeshan: the same chart, the same rules, indexed by house instead of by planet. In practice you use both. Grah Nirdeshan tells you what a dasha lord will do; Bhaav Nirdeshan tells you which dasha to wait for.

The output is a list of planets, and — as always in KP — the list is ranked.

The four groups

Then two more slots in the response:

The shape to absorb is the alternation. Star of occupant → occupant → star of owner → owner. At each pair, the star link comes first and the planet itself second; and the occupant’s pair comes before the owner’s pair entirely.

The house lord — the planet a Vedic reading would reach for first — is last.

Why the ordering is what it is

There is one sentence behind the whole table: the sign shows, the star does.

A house lord owns its house the way a landlord owns a flat — the deed is real, but he is not there. An occupant is standing in the room. And a planet in the star of that occupant is the one holding the occupant’s hand. KP puts the star link at the top because a nakshatra lord is what actually releases results.

Once the ordering clicks, the practical use follows. When you are looking for who will bring a marriage, the 7th house’s A group is your first stop, not its lord.

Worked example

House 8 has one occupant, Mercury. Mars and Rahu both lie in Mercury’s star.

• A (rank 1): Mars, Rahu — in the star of the occupant.
• B (rank 2): Mercury — the occupant itself.

So Mars and Rahu — neither of which is anywhere near the 8th house, and neither of which owns it — are stronger 8th-house significators than the planet sitting in it. A dasha of Mars here delivers 8th-house matters more surely than a dasha of Mercury does.

That result is entirely counter-intuitive from a Vedic reading and entirely routine in KP. It is also why the app returns a reason beside every planet: the answer is worthless if you cannot see the chain.

Strongest claim wins

A planet frequently qualifies twice. Mars might occupy house 7 (group B) and own house 7 (group D).

AstroShruti keeps the strongest rank only. Mars there is a rank 2, full stop — not a rank 3 average, not two separate entries fighting each other. The group memberships are all still listed, so you can see it is both; the rank reflects its best claim.

The ranked list comes back sorted by rank, then alphabetically by planet, so the order is stable between runs — nothing reshuffles on you between two views of the same chart.

Rahu and Ketu

The nodes never appear in group D. They cannot: the house lord is the ruler of the sign on the cusp, and no sign is ruled by a node.

They enter through E, the representation rules — a node signifies a house if the house shows up among those reached via the house it occupies, its sign lord, its star lord, or a planet sharing its house. Those four agents are switchable per request. A node that gets in this way is ranked 2, level with the occupants.

That rank is a judgement call on our part and worth naming as one. It says a node representing a house is as strong as a planet standing in it — which is defensible in KP, where the nodes are held to be stronger than the planets they represent, but it is a choice, not an inevitability.

The floor is not a ceiling. Rahu in the star of an occupant is ranked 1 through group A like anything else. In the example above, that is exactly what happens.

The F group is empty

F_associations is in the response schema and the engine never writes to it. It returns [] for every house of every chart.

It was reserved for the association layer — significators reached through conjunction and aspect with the house’s other significators. That layer is not built. We are documenting the field rather than removing it because the contract is public, but do not read meaning into an empty F: it means not computed, not none found.

What the house lord and occupants are computed from

Two definitions decide this whole table, and both are KP-specific:

• The house lord is the ruler of the sign sitting on that house’s cusp — taken from the Placidus cusp longitude, under the KP ayanamsha. Both are forced on the KP pages regardless of your Advanced Settings.
• The occupants are the planets falling in the house’s cusp-to-cusp arc. In KP the cusp is the start of a bhava, not its centre. The app computes the Sripati sandhi midpoints too, but only to flag a planet sitting near a junction — they never decide which house it belongs to.

That second point is the usual source of “your app disagrees with my chart”. It generally is not a disagreement about where the planet is; it is a disagreement about where the house begins.

Where to go next

• Grah Nirdeshan — the same rules, read planet-first.
• Cuspal Interlinks — the cusp lord chains that this table’s house lords open into.
• Vimshottari Dasha — the timing these significators are ultimately read against.