Take a chart with Tula Lagna. The Ascendant is at 205 degrees. Venus, the chart's ruling planet, sits at 189 degrees in Tula. By the sign-based system, Venus is in the first house. The Lagna lord is in the Lagna. A strong placement by any classical standard.
Now apply Bhava Chalit. The first house boundary by spatial division falls at 190 degrees. Venus at 189 degrees is just behind it. By the space-based system, Venus occupies the twelfth house.
The Lagna lord in the twelfth house carries entirely different classical implications than the Lagna lord in the first. A practitioner reviewing this chart would read both positions. An application that returns only one is giving an incomplete answer, and it cannot know which planets are near cusps without computing both systems.
This is not an edge case. Any planet within approximately fifteen degrees of a house cusp is a candidate for disagreement between the two systems. In an active chart, that describes several planets at once.
Where the Two Systems Come From
Rashi house placement is sign-based. The Ascendant sign becomes the first house. The next sign becomes the second house, and so on around the zodiac. Every degree of a given sign belongs to the corresponding house. A planet is assigned to whichever sign it occupies.
Bhava Chalit placement is space-based. The actual degree of the Ascendant becomes the midpoint of the first house. Thirty degrees on either side defines the house boundaries in equal-house terms, or the boundaries are computed using the Placidus or Sripathi system depending on the tradition. A planet is assigned to whichever spatial segment it falls within, regardless of which sign it occupies.
For most planets in most charts, the two assignments agree. A planet deep inside a sign is well clear of the nearest cusp and lands in the same house under both systems. The disagreement appears when a planet sits near the boundary between houses, where the sign division and the spatial division fall at different points. In those cases, the two systems give different answers, and both answers are considered valid by different aspects of classical interpretation.
What Each System Is Used For
This is where most explanations stop at the wrong level of abstraction. The question is not which system is correct. The question is which system answers which type of question.
Rashi house placement drives sign-lord relationships, yoga detection, and Parashari aspect analysis. When you identify the lord of a house, you look at which planet rules the sign on that house cusp. When you check whether two planets are in the same sign, or whether a planet aspects a specific house, you use Rashi positions. The entire yoga detection apparatus in classical Parashari texts operates on Rashi houses.
Bhava Chalit house placement answers the question of which house a planet physically occupies, and therefore which house's results the planet delivers. This is what the classical texts call Bhava Phala, house result. BPHS Chapter 11 is explicit on this point: the Bhava Chalit chart determines physical occupation, and the Rashi chart determines sign-based lordship and aspects. Experienced Jyotishis read the planet as influencing both houses when the two disagree, with primary strength coming from the Rashi house and physical presence registered in the Bhava Chalit house.
This means a developer building a feature that asks which house a planet is in needs to decide which question they are actually asking. If the application is detecting yogas, the Rashi house is the correct input. If the application is describing what life area a planet governs by physical placement, the Bhava Chalit house is the correct input. An application that uses one field for both purposes will produce incorrect results for whichever purpose the chosen field does not serve.
Why Most APIs Return Only One
Computing both systems requires knowing the exact Ascendant degree, applying the correct house division method, and running the boundary comparison for every planet. APIs that return a single house number per planet have made a silent decision about which system to use. They usually do not document that decision, which means the developer inherits the assumption without knowing it.
The consequence is invisible until a practitioner reviews the output. For planets that sit cleanly in the middle of a sign, both systems agree and the missing field makes no practical difference. For planets near cusps, the disagreement can be dramatic. A planet assigned to the fifth house by Rashi may fall in the sixth by Bhava Chalit, or the fourth. The interpretive consequences of those two positions are not similar.
In the chart used earlier as an example, Saturn also shows this disagreement. By Rashi, Saturn occupies the second house. By Bhava Chalit, Saturn occupies the first. Saturn in the second house and Saturn in the first house produce different readings in every classical text on the subject. An API that returns only one position has committed the application to one of those readings without exposing the choice.
An API that returns a single house number per planet has made a silent interpretive decision on behalf of every application built on it. Most of those applications do not know the decision was made.
What the Asterwise Response Returns
Every planet in the Asterwise natal chart response carries three house-related fields: a general house field, a rasi_house field, and a bhava_chalit_house field. When the two systems agree, all three fields carry the same value. When they disagree, rasi_house and bhava_chalit_house carry different values and a house_system_note field appears on that planet explaining the discrepancy, naming which field to use for which analytical purpose, and citing the classical methodology per BPHS Chapter 11.
This design means the developer does not need to implement the comparison logic. The API surfaces the disagreement directly in the response and provides enough context to act on it correctly. For an application that only needs Rashi houses, the rasi_house field is always there. For an application that needs Bhava Chalit placement, bhava_chalit_house is always there. For an application that needs to handle the disagreement explicitly, the note provides the classical guidance.
Return to the chart in the opening example. Venus at 189 degrees, Lagna at 205, the house boundary at 190. By Rashi, Venus is the Lagna lord sitting in the first house: a strong placement by any classical standard. By Bhava Chalit, Venus has crossed behind the boundary into the twelfth house of loss.
An application that stores one house number for Venus has made a choice between these two readings without knowing the choice existed. An application that stores both can ask the right question depending on what it is trying to answer. Yoga detection uses the Rashi house. Bhava Phala interpretation uses the Bhava Chalit house. The two fields serve different analytical purposes and cannot substitute for each other.
The Asterwise natal chart response returns both. When they differ, the response includes a note citing BPHS Chapter 11 that identifies which field to use for which purpose. The developer does not need to implement the distinction. The API surfaces it.