Astrology

Designs for the chart layer above the ephemeris: how canonical positions become natal charts, divisional charts, dashas, panchang, transits, compatibility, and muhurta.

Astrology features consume chart facts only: never an ephemeris provider, never a second copy of the base rules. Astronomy and base semantics live in Ephemeris; this domain composes meaning on top.

Designs

• Astro Composer — stateless composition service. Reads from Astro Binder and returns deterministic charts, vargas, Vimshottari periods, panchang, transits, matching, and muhurta windows (auspicious timing), with explicit profiles and a versioned rulebook.
  • Chart core — frame, houses, occupancy, dignity, combustion, planetary war.
  • Varga engine — sixteen divisional charts (vargas) from the D1 longitude, with rulebook-pinned variant schemes.
  • Dasha engine — Vimshottari periods (planetary cycles) as continuous UTC timelines, independent of clock, calendar, and timezone.
  • Panchang engine — sunrise-anchored tithi, vara, nakshatra, yoga, and karana, with solved boundary instants.
  • Transit engine — gochara, Sade Sati, and ashtakavarga over an immutable reference chart.
  • Matching engine — ashtakoota, its doshas, and named cancellations for a pair of charts.
  • Research and convention register

Not in this domain

• Provider selection, ephemeris data, time scales, zodiac conversion, provenance (Ephemeris).
• Base semantics: signs, nakshatras, padas, motion, aspects, house placement (Astro Binder semantics).
• Saved charts, birth records, user profiles (account/chart domains).
• Interpretation copy, remedies, predictions (product content).

Conventions

• Each design keeps guide and diagrams together: chart-composer/README.md with chart-composer/architecture.svg.
• Every response names the profile, rulebook version, and composer version that produced it.
• A rule that changes any number is a new version, never a runtime toggle.