Moira 6.10.0

Release date: 12 October 2026.

Moira 6.10.0 brings the completed Vedic work through the selected VED-014
Kalachakra profile into an engine release. The Python engine, public facades
and REST API expose the same named policies, bounded calculations and source
provenance. Sixteen of the 24 registered Vedic packages have reached their
selected delivery checkpoints; this release does not claim every tradition.

Vedic calculation and transport

• Daily Panchanga uses local dates, zones and sunrise-owned days, with solved
  limb endings, repeated/skipped sunrise evidence and unavailable solar states.
  Bounded lunar-month context is included; festival catalogues remain research.
• Gochar includes the admitted seven-body/natal-Moon snapshot, reader-bound
  epoch and civil-date composition, and bounded whole-sign windows. The window
  contract retains retrograde re-entry, Vedha, optional natal BAV, boundary
  uncertainty and a complete state partition under explicit resource budgets.
• D60 exposes edition-owned deities, Santhanam signs, a modern full-position
  profile and the explicit classical_derived_linear degree policy. Harmonic
  defaults remain; classical derivation and modern attribution stay distinct.
• Sayanadi admits the selected BPHS Navamsa-ordinal profile with strict inputs
  and dated birth composition. Legacy conditional-effect prose retains its
  separately documented validation limits.
• Chara supports bounded cycles and three named Rangacharya recipes. Argala
  has separate BPHS, PVR and Rath assessments, with repaired result invariants
  and explicit source conflicts.
• Yoga extensions add 21 selected source entries, with independent Navamsa
  readings and bounded BPHS wealth/royal rules. Unresolved aspect-target
  readings are explicitly excluded.
• Kalachakra admits bphs_santhanam_longitude_row_cycle_v1: nine major-period
  occurrences, optional full-parent antardashas, exact rational source years,
  explicit 360/365.25-day projections and bounded active-period lookup. Five
  REST operations provide discovery, supplied/date-derived sequences and
  current periods. Competing continuations and disputed gati remain visible.

Muhurta

• Personalized sampled search now uses actual natal inputs, declared clocks,
  effective ayanamsa and complete applied-policy receipts.
• Seven named window families, Panchanga Shuddhi assessments, selected dosha
  detectors and source-scoped cancellation rules preserve raw restrictions,
  evidence and boundary uncertainty.
• Lagna/Navamsa components and optional strength context are available through
  the same engine and REST policies.
• Source-selected marriage, residential housing/Vastu, ordinary land travel,
  purchase/sale/first-opening and additional named marriage traditions share
  strict request contracts and bounded evaluation/search products.
• Marriage searches reuse request-local exact computations and remove
  redundant work without changing their accuracy or validation thresholds.

Shared repairs and catalog integration

• Polynomial ayanamsas use the IAU 2006 general precession quantity appropriate
  to the scalar calculation. Historical sidereal results can change.
• Direct-input admission, reader binding, timescale provenance, result-tree
  integrity and REST error classification have been hardened across the
  delivered Vedic surfaces. Previously accepted malformed inputs may now fail.
• Packaged small-body manifests and metadata identify external catalog release
  2026.10.10.1. The wheel does not contain the external SPK catalog files.
  Historical scientific receipts remain bound to their original manifests;
  they are not relabelled to certify the newer catalog bytes.
• Publication candidates and exact-tag documentation artifacts retain distinct
  provenance, and generated API/wiki checks run before release.

Validation and limits

The release validation receipt
records the review, selected tests, resource receipts and publication checks.
Individual source and real-kernel acceptance receipts remain linked from the
Vedic register.
These establish the documented computational scope, not predictive efficacy.

Special Lagnas, additional Gochar corpora/modifiers, deferred Pancha Pakshi
doctrines, exceptional lunar-month rules and festival catalogues remain future
work. Natal-discovery and light-box work in the development checkout is excluded.
Website application deployment is separate from this engine/PyPI release.

See compatibility notes before upgrading.

Publication verification

Released from immutable tag v6.10.0, commit a38b43ceee26c8b45f3d45bbf04ff3eaf687fd30.

• Selected integrated acceptance: 9,409 unique tests passed, zero failures, errors or skips; 551/551 DE441 resource uses executed. This is the scoped release acceptance set, not a claim that every repository test was run.
• Release Hardening and Release Acceptance Matrix passed on the tagged commit, including actual Python 3.10 compatibility.
• Tagged publication workflow, successful attempt 2 completed. PyPI 6.10.0 contains 20 wheels for CPython 3.10-3.14 across Linux x86_64, Windows AMD64, Intel macOS and Apple Silicon, plus the source archive.
• The downloaded published Windows CPython 3.14 wheel and source archive match the original CI artifact SHA-256 values. The wheel passed native import, Kalachakra engine calculation, epoch projection/current lookup, five OpenAPI route checks, actual HTTP 200 engine parity and malformed-input HTTP 422. Runtime smoke coverage is Windows CPython 3.14; all platform wheel builds succeeded.
• The source archive and wheel contain the selected Kalachakra engine/REST implementation and exclude unfinished natal-discovery work. Light-box development scripts are absent from the source archive. Deferred development files remain preserved locally.
• The first upload attempt hit PyPI's project storage limit after 15 files. After the maintainer removed older versions, only failed publication jobs were rerun with existing artifacts. Existing release files and the tag were preserved; no replacement artifacts were built.

Published Windows wheel SHA-256: fbe0312094b5c523e62c89a1a32c7eee355b39db3f8651ecccddeb49e4ce30ac.

Published source archive SHA-256: 4f111467f4d5f80c115fe0426fc6c0ad4fbbbad7a1ecd70481a3d24fea6ae120.