Combustion and Deep Combustion: Why They Are Two Fields, Not One

Take a chart with the Moon at 198 degrees and the Sun at 205 degrees. The orb between them is approximately 7.76 degrees. That Moon is combust by any classical measure. Its significations are weakened. A developer who receives is_combust: true from the API has the information they need to flag this condition.

Now take Saturn in the same chart. Saturn sits at 215 degrees, approximately 9.80 degrees from the Sun. Saturn is also combust. The developer receives another is_combust: true. Both planets are flagged identically.

This is where a single boolean stops being sufficient. The Moon at 7.76 degrees from the Sun and Saturn at 9.80 degrees are both combust, but they are not in the same classical condition. Combustion is not a binary. The classical tradition defines a gradient, and the interpretive consequences change as a planet moves deeper into the Sun's orb.

What Classical Texts Say About the Gradient

Phaladeepika and other classical Parashari texts describe combustion in two stages. The outer stage begins when a planet enters the Sun's combustion orb. At this distance, the planet's natural significations are weakened and its karakatwa is reduced in effectiveness. The planet still functions, but with diminished strength.

The inner stage, deep combustion, begins when a planet comes within a tighter orb that varies by planet. At this distance, the classical texts treat the planet as effectively non-functional for the purposes of its natural significations. The distinction matters because a deeply combust planet is not merely weakened - its ability to deliver results in the domains it governs is severely curtailed, more so than combustion alone produces.

The orb thresholds differ by planet. Mars has a wider combustion orb than Jupiter. Venus has different orbs depending on whether it is direct or retrograde. Saturn's deep combustion orb is narrower than its combustion orb by a significant margin. Each planet has its own threshold because each planet has a different relationship to solar proximity in the classical model.

A single is_combust boolean correctly identifies that a planet has entered the solar zone. It cannot identify which zone. A developer who wants to write different interpretive content for a deeply combust planet versus a merely combust planet has no way to make that distinction without a second field.

Why This Matters in Practice

The interpretive difference between combust and deep combust is not subtle. Consider the Moon in the sample chart above. At 7.76 degrees from the Sun, the Moon is combust but not deeply combust. Its significations - mind, emotions, mother, public reputation - are weakened. The native may experience mental restlessness or emotional difficulty, but the Moon retains functional presence in the chart.

A Moon inside the deep combustion threshold would carry a categorically different reading. The classical texts describe such a Moon as producing a native whose mental and emotional faculties face significantly greater strain - and for the Moon specifically, this condition compounds with Paksha Bala, the Moon's phase-based strength, which also diminishes as the Moon approaches the Sun. The two conditions reinforce each other. These are different statements about the same planet at different distances from the Sun.

An application that delivers interpretive content based on a single combust boolean cannot make this distinction. It must either ignore deep combustion entirely, which produces inaccurate readings for planets inside the tighter orb, or it must implement the orb calculation itself, which requires knowing each planet's specific deep combustion threshold. Neither is necessary if the API returns both flags separately.

How the Asterwise Response Is Structured

Every planet in the Asterwise natal chart response carries both is_combust and is_deep_combust as independent boolean fields. When a planet is outside both orbs, both fields are false. Rahu and Ketu, the lunar nodes, are not physical planets and cannot be combust by the Sun - both fields are always false for them regardless of their proximity to the Sun. When a planet is within the outer orb but outside the inner orb, is_combust is true and is_deep_combust is false. When a planet is inside the inner orb, both fields are true simultaneously.

In the sample chart used in this post, Moon returns is_combust: true and is_deep_combust: false. Saturn returns the same pair. Both planets are in the outer combustion zone, not the inner. A third planet at one degree from the Sun would return is_combust: true and is_deep_combust: true - a qualitatively different state requiring different interpretive handling.

This design means the developer does not need to implement planet-specific orb tables. The calculation happens at the engine level. The response surfaces the result of that calculation as two independent flags, and the developer can act on either or both depending on what the application needs to express.

What This Changes for Application Design

For applications that generate interpretive text, the two-field structure enables three distinct content paths per planet: unaffected, combust, and deeply combust. A natal chart feature that simply flags combust planets can use is_combust. A feature that attempts more classical accuracy can use is_deep_combust to trigger a separate, more severe interpretation for the subset of planets inside the tighter orb.

For yoga detection, combustion is a relevant modifier. Certain classical yogas are partially or fully cancelled when a participating planet is combust. The classical texts on yoga cancellation sometimes distinguish between combust and deeply combust when describing what overrides what. An engine that tracks both states can apply these cancellation rules more precisely than one that collapses them into a single flag.

For Dasha interpretation, when the active Dasha lord is combust, the classical tradition notes that the lord's significations are weakened for the duration of that period. When the Dasha lord is deeply combust, the weakening is treated as more severe. A two-field response lets the developer surface this distinction in the timing layer without recalculating the orb from scratch.