01
Resolve civil time
Preserve the entered local time, IANA zone, database release, selected UTC offset, daylight-saving fold decision, and resolved UTC instant.
[ Source layer // celestial-facts/0.1 ]
The Celestial Fact Layer records what was calculated, for which instant and observer, in which frame, using which authority and corrections. It is deliberately incapable of explaining the universe or interpreting a chart.
Layer status: foundational
7 registered authority contracts
UTC, TAI, TT, TDB and UT1 preserved
Topocentric and origin-aware records
Interpretation fields: prohibited
Astronomy knowledge layer: live and separate
Reproducibility pipeline
01
Preserve the entered local time, IANA zone, database release, selected UTC offset, daylight-saving fold decision, and resolved UTC instant.
02
Record WGS 84 latitude and longitude, elevation reference, units, and location uncertainty. A city name is not a computational location.
03
Retain the authority, service or kernel release, object identifier, observing center, exact request parameters, retrieval time, and raw-response digest.
04
State origin, frame, epoch, equinox, time scale, coordinate representation, position type, and every applied or omitted correction.
05
Store values with units, precision and uncertainty; preserve limitations; canonicalize the bundle so an independent system can reproduce and compare it.
Record contract
UTC instant · ephemeris time scale · civil-time provenance · leap-second source · Earth-orientation source
Latitude · longitude · horizontal CRS · elevation · elevation reference · horizontal and vertical uncertainty
Human-readable name plus an authority identifier such as a JPL/NAIF object code
Origin · frame · epoch · equinox · representation · geometric/astrometric/apparent position type
Light time · stellar aberration · gravitational deflection · atmospheric refraction
Provider source · request URL and parameters · response SHA-256 · retrieval timestamp · software version · limitations
Hard boundary
Future compatibility
Astronomy and any later interpretive tradition may reference an immutable fact bundle. Neither layer may rewrite its time resolution, observer, coordinate frame, correction choices, or provider provenance.
Explore 23 Astronomy explainers →Authority registry
Solar-system object identifiers, observing centers, time inputs, reference frames, corrections, output quantities, and stated ephemeris limitations.
Boundary: Horizons output is authoritative only with the complete query contract preserved; transformed or rounded values require their own provenance record.
Frame identifiers, frame centers, transformations, orientation relationships, and the distinction between frames and coordinate representations.
Boundary: A frame name alone does not establish the observing origin, epoch, equinox, time scale, or correction model.
UTC, TAI, TT, TDB, calendar and Julian-date representations, leap-second kernels, and conversions used by SPICE.
Boundary: A civil timestamp is not an ephemeris time until its zone, offset, ambiguity resolution, leap-second data, and target time scale are declared.
IAU-approved algorithms for astrometry, time scales, Earth rotation, precession, nutation, coordinate transformations, and related fundamental astronomy.
Boundary: SOFA supplies standard algorithms and validation programs; an implementation must still record its exact release and input data products.
Bulletin A and B Earth-orientation parameters, Bulletin C leap-second announcements, and Bulletin D DUT1 announcements.
Boundary: The bulletin number or data-product version used in a computation must be retained; “latest” is not a reproducible version identifier.
Versioned civil-time-zone identifiers, UTC offsets, daylight-saving transitions, and historical rules for representative locations.
Boundary: The database records civil-time practice and can contain historical uncertainty; it does not supply leap seconds or astronomical time scales.
The WGS 84 latitude and longitude coordinate reference system and axis/unit definitions used for terrestrial observer locations.
Boundary: EPSG:4326 is horizontal; elevation must separately name its value, unit, reference, and uncertainty.