HomeValidationMoira 5.1–5.2 Release Evidence

Moira 5.1–5.2 Release Evidence

A status-explicit index of the validation and documented evidence added from Moira 5.1.0 through 5.2.3.

Moira 5.1-5.2 Release Validation Ledger

Engine baseline: 5.2.3 Last verified: 2026-07-25 Scope: public evidence added or materially changed after 5.0.0

This ledger makes recent release evidence discoverable without widening any claim beyond its named oracle, corpus, invariant, or runtime boundary. It supplements the three standing validation reports and the versioned release notes; it does not replace either.

Status vocabulary

  • Validated — checked against a named external authority or a clearly bounded authority corpus under declared semantics.
  • Partial — meaningful external or invariant evidence exists, but the entire surrounding subsystem is not closed.
  • Documented — behavior and failure policy are exercised and recorded; no broader external-truth claim is made.
  • Research-only — evidence remains outside the admitted public runtime doctrine.
  • Not evaluable — the available source cannot answer the claimed question under matching semantics.

Release evidence

ReleaseProduct sliceStatusEvidence and boundary
5.1.0Source-scoped Pancha Pakshi public surfacesPartialSource-table fidelity, immutable provenance, exact arithmetic, routing, and structural invariants are exercised. These checks do not establish empirical astrological efficacy or a universal Pancha Pakshi canon. Private research ledgers remain outside the website publication allowlist.
5.1.0Dignity policy switchesDocumentedAll six dignity REST routes and the engine policy surface exercise independent Halb and Oriental/Occidental inclusion without changing the underlying phase or sect geometry.
5.1.0Gauquelin g5 historical corpusValidatedThe dedicated Gauquelin g5 ledger binds the public computation to a named historical dataset, plus-zone policy, cached Swiss method-0 comparison, and declared tolerances. The result is limited to that corpus.
5.1.1DE440 historical Delta-T bindingDocumentedContent-derived DE440/LE440 identity, basis-sensitive historical conversion, and continued fail-closed behavior for unknown DE/LE products are regression-enforced. This is a clock-binding repair, not a new ancient-position accuracy claim.
5.1.2NASA/GSFC 1901-2000 lunar eclipse corpusValidatedAll 229 published events are classified with the correct type family at the catalog TD/TT maximum; forward, backward, and bulk searches recover the full ordered sequence. The greatest-eclipse TT residual remains below 55 seconds for this named cross-model corpus.
5.1.2Solar footprint topology repairPartialNative/Python parity, connected-boundary incidence, exact horizon junctions, and affected-event regressions are exercised. Performance measurements are not scientific validation.
5.2.0Solar and lunar global circumstancesValidatedGlobal vessels are bound to existing NASA/GSFC Besselian and hashed lunar-figure corpora. Declared EclipseWise DE405/DE430 rows provide separate cross-model corroboration for named 2027 solar and 2026 lunar products.
5.2.0Adaptive eclipse cartographyPartialSpherical mesh closure, antimeridian splitting, polar and near-singular topology, convergence reporting, public exports, and REST serialization are exercised. A non-converged preview must remain visibly non-converged. No dense published duration-contour oracle is claimed.
5.2.1Frame-explicit house-boundary geometryDocumentedGreat-circle planes, Placidus semi-arc event curves, exact cusp incidences, southern/high-latitude cases, effective fallback, sidereal labels, immutable vessels, exports, and REST serialization are exercised. This is geometry and transport evidence, not an external claim that every house doctrine is physically validated.
5.2.2Mean and true lunar-node framesValidatedThe raw mean-node argument is bound to ERFA/IERS faom03; the true-frame conversion is checked through IAU 2000A nutation, and the true node is checked by northbound zero-latitude crossing and common-frame invariants. Swiss fixture agreement is secondary corroboration.
5.2.2Proper25 plus retained PDS asteroid-family membershipValidatedSource counts, metadata hashes, aliases, overlaps, deterministic display-primary selection, bounded REST transport, and annotation refresh are checked. Catalog membership is evidence of source admission, not proof of genetic relation.
5.2.3Installed small-body manifest readinessDocumentedMetadata-only, complete, partial, and explicitly configured discovery modes are exercised with facade and /ready behavior. A wheel-shaped install confirms that packaged metadata without BSP shards is not reported as an installed ephemeris.

Current catalog facts

These counts name different products and must not be collapsed:

  • Position-capable asteroid ephemeris: 1,382 bodies in 56 external Type-13 SPK shards when that catalog is installed.
  • Asteroid-family membership catalog: 342 admitted families, 200,726 unique numbered asteroids, and 221,095 many-to-many membership rows.

Family membership does not imply that a matching position shard is installed. A position-capable asteroid does not imply family membership.

Primary release records