Moira

The Light Box Engine

Moira is a Python astronomical computation library built on the principle that transparency is the primary metric of accuracy. Documented calculation stages and named public validation evidence make admitted surfaces inspectable without turning a scoped receipt into a universal claim.

Today Moira is an astronomy-first astrology platform in four parts: a free birth-chart calculator, Moira Enhanced for personalised Urania readings and saved work, Moira Workspace for professional astrology tools, and the MIT-licensed Python engine for developers and researchers.

Why Moira Exists

Developers choosing an ephemeris should evaluate the public API, data requirements, validation evidence, and official license terms for the exact version and integration they intend to ship. Swiss Ephemeris offers AGPL and professional-license paths; Moira publishes a different Python-facing contract under MIT.

Moira was built from a different premise. The question was not "how do we wrap Swiss Ephemeris?" but "what would a modern astronomical computation library look like if it were designed today, with access to JPL DE441, Gaia DR3, IAU 2006 precession, and a physical model of Earth's rotation?"

The answer is a library with documented reduction stages from SPK kernel data to apparent ecliptic longitude, named validation reports, and inspectable Python-facing evidence on admitted surfaces. A versioned Mars-at-J2000 receipt publishes the measured JPL Horizons residual and its raw trace without presenting that historical run as current deployment truth. The ΔT model reports its own uncertainty.

"Transparency is the Primary Metric of Accuracy."

This is the Light Box Doctrine: the philosophical and technical commitment that governs every design decision in Moira. A black box that gives the right answer is less valuable than a transparent system that shows you why.

Development History

2025
Moira v1.0.0 released with a documented planetary reduction pipeline
2025
Arabic Parts and sidereal calculation support expanded
2026
v2.0.0: Gaia DR3 star registry (1,809 stars), physical ΔT model, asteroid family classification
2026
v3.0.0: Full Vedic surface, astrocartography, harmograms, Uranian bodies, dual-substrate architecture
2026
v3.2.2: 3I/ATLAS interstellar visitor, variable stars, multiple star systems, synastry/composite/Davison
2026
v3.4.2: expanded REST surface and full reduction-pipeline visibility (per-stage breakdown via the public API)
2026
v3.4.3: draconic (nodal-zodiac) chart frames: recast any chart with 0° Aries anchored to the Moon's north node, in the library and the public REST API
2026
v4.0.0: expanded Vedic calculation modules with source receipts, including 60 yogas, Shadbala, Ashtakavarga refinements, upagrahas, avasthas, and extended Jaimini, plus released comet and asteroid catalogs with product-specific validation records
2026
v4.0.1: traditional star work: a tiered fixed-star paran canon, honest per-body crossing inventories, birth-moment angular contacts as their own product, and the full heliacal surface through one packet call
2026
v4.1.0: Church of Light astrodynes (natal and progressed, validated against captured reports), progressed contact search with visible numerics, and a paran/heliacal solver rework roughly 20× faster with event times unchanged
2026
v4.2: aspects from caller-supplied positions under the engine's own tiered doctrine, Ramesey's Moon-condition electional test, and relationship REST completion: composite and Davison responses carry the engine's aspect web with honest (null) motion
2026
v5.0.0: first-class declination aspects (Parallel and Contra-Parallel with a motion witness), a hardened label-preserving synastry surface with a cross-chart network product, and the Delta-T truth overhaul binding historical time to each kernel's declared tidal basis
2026
v5.1.0: Source-Scoped Policy and Evidence
2026
v5.1.1: DE440 Historical Delta-T Repair
2026
v5.1.2: Eclipse Geometry Hardening
2026
v5.2.0: Global Eclipse Circumstances and Cartography
2026
v5.2.1: Spatial House-Boundary Geometry
2026
v5.2.2: Node Frames and Proper25 Families
2026
v5.2.3: Installed Small-Body Manifest Readiness
2026
v6.0.0: Hellenistic Engine Completion
2026
v6.0.1: Complete Asteroid Identity Catalog
2026
v6.1.0: Contract and Release Integrity
2026
v6.1.1: 10,025-Body Asteroid Identity Catalog
2026
v6.2.0: Admitted Capability Baseline
2026
v6.2.1: Wheel Asteroid Catalog
2026
v6.2.2: Lunar Node and Lilith Honesty
2026
v6.3.0: Hellenistic Computation Deepening
2026
v6.4.0: Natal Aspect Grid and Delta-T Scenario
2026
v6.4.1: Natal Grid for Every Mover
2026
v6.5.0: Source-Bound Cosmic Catalogs
2026
v6.6.0: Planet-first Stelliums and Selected-zodiac Houses
2026
v6.7.0: Strict Orbital Core, Ephemeris Apsides, and Doctrinal Chesta Bala
2026
v6.8.0: SBDB Osculating Asteroid Orbit Classification and Small Body REST Surface
2026
v6.8.2: KernelPool Native Planetary Evaluator and Indexed Ephemeris Routing

Scientific Standards

Every data source and standard used in Moira's computation pipeline.

Author & The Story Behind Moira

D
Daniel Burkett
Creator & Maintainer of Moira

Daniel is the designer and primary developer of Moira. His work bridges software engineering, numerical astronomy, and astrological research. He created Moira to build open, auditable tools with explicit calculation policies and published validation evidence for practitioners, researchers, and application developers.

Why I Built Moira: The Anti-Black Box Manifesto

In 2024, astrology applications experienced an unprecedented boom. Millions of curious people were downloading apps on their phones, seeking meaning, self-knowledge, and connection. But as a software engineer who also deeply loves the historic rigor of classical astrology, I noticed a troubling, systemic degradation taking place across the industry.

Most modern apps had become opaque black boxes. They took a user's sensitive, intimate birth data—exact birth dates, times, and hospital locations—and fed it into generic commercial Large Language Models that have zero spatial understanding of spherical trigonometry. When AI models guess planetary positions, they hallucinate. They round off house cusps by whole degrees, confuse retrograde stations, and hide their mathematical derivations behind flowery, repetitive prose.

Meanwhile, developers choosing an ephemeris must evaluate API fit, data dependencies, and licensing. Swiss Ephemeris is a mature C library distributed under an AGPL option and a professional-license option. Moira offers a different contract: an MIT-licensed Python-facing engine with explicit policies and receipts. Each team should review the official licenses and its own architecture.

I built Moira to solve both crises at once:

1. For Individuals: Inspectable Calculations

Moira computes chart coordinates from NASA Jet Propulsion Laboratory DE440/DE441 ephemerides and documented IAU standards; Urania adds synthesis after the calculation. Published validation is product- and date-range-specific rather than a universal accuracy guarantee. Moira uses no advertising pixels, while limited operational usage is logged as described in the Privacy Policy.

2. For Developers: The MIT-Licensed Foundation

The Moira computational engine is released under the permissive MIT license and provides Python interfaces with native acceleration in selected paths. Developers should review the licenses of every dependency and dataset used in their own distribution.

"Astronomy is the foundation. Astrology is the purpose. Validation is the proof. Visibility is the doctrine." — Daniel Burkett

MIT License

Moira's repository is MIT-licensed. The MIT license permits commercial and closed-source use subject to its notice and disclaimer; adopters remain responsible for the licenses of their other code, data, and dependencies.

View LICENSE →

These summaries are product information, not legal advice. Review the official license texts and obtain legal advice for your architecture and distribution.