How the PanditOne Engine Works

The engine begins with date, local time, timezone, latitude, and longitude. The local birth moment is converted into a universal calculation moment, recorded as Julian Day UT. This is important because planetary positions are time-dependent and because the same clock time means different sky moments in different timezones.

If time, place, or timezone is missing, the engine can still show some broad signs, but it should lower confidence for houses, Lagna, divisional charts, and timing-sensitive interpretation. A professional reader should always ask whether the birth time is exact, approximate, or unknown before treating house-based claims as strong.

The engine calculates observable planetary positions and then converts them into sidereal longitudes by subtracting ayanamsa. The calculation profile is sidereal-primary with tropical data retained only as secondary audit context. The default ayanamsa path is Lahiri unless another supported setting is explicitly supplied.

This is why a professional report should list ayanamsa degrees. Without that, two readers using different settings may disagree by enough to change a nakshatra, pada, or divisional placement near a boundary.

After the ascendant is resolved, the engine assigns the first house to the ascendant sign and derives the house sequence from there. The current chart profile uses whole-sign style house logic for the Jyotish reading surface, so every sign becomes one house beginning from Lagna.

This makes the chart easier to audit: if Lagna is Capricorn, Capricorn is house 1, Aquarius is house 2, Pisces is house 3, and so on. The South Indian and North Indian displays may look different, but the house assignments are the same underlying D1 data.

Once planets, Lagna, houses, and vargas are available, the engine derives nakshatra, pada, dignity, sign lord, house lordships, aspects, panchanga, Vimshottari dasha, transits, and classical pattern signals. These are not all equal in interpretive weight.

A premium report should tell the user which factors are calculation facts and which are interpretive emphasis. For example, Moon in a nakshatra is a calculation fact. Relationship focus being supportive or mixed is an interpretation built from multiple facts.

The engine records calculation source, ephemeris provider, ayanamsa, house system, node mode, and warnings. This is not internal trivia. It is what lets a student or practitioner audit the chart when a placement looks surprising.

The product should avoid pretending that every output is equally certain. A high-quality reading is transparent: it names its settings, admits limits, and explains why a conclusion follows from chart factors.