Bounded answer
Preserve ephemeris family, file or dataset identifier, release, checksum, coverage interval, and flags. Bind those fields to one canonical input manifest and receipt before interpreting or sharing an output.
Input contract
What must be fixed first
Canonical input manifest
Named algorithm and dependency versions
Declared units and conventions
Retention and redaction policy
Procedure
Work the decision in order
- 1
Normalize the input without dropping uncertainty.
- 2
Record ephemeris family, file or dataset identifier, release, checksum, coverage interval, and flags.
- 3
Run the named deterministic operation.
- 4
Bind inputs and outputs into a receipt.
- 5
Verify the receipt independently before interpretation.
Expected outputs
- Canonical manifest
- Calculation or transformation receipt
- Reproducibility and redaction statement
Refuse when
- Naming a software library does not identify the ephemeris data it loaded.
- Required input, unit, convention, or dependency version is absent.
- An interpretive preference selects the computational convention after outputs are seen.
Questions this guide answers
What must a machine preserve for ephemeris file version?
Preserve ephemeris family, file or dataset identifier, release, checksum, coverage interval, and flags.
Which information must be versioned?
At minimum, preserve ephemeris family, file or dataset identifier, release, checksum, coverage interval, and flags, together with the canonical input and output digests.
When should an output be withheld?
Withhold it when naming a software library does not identify the ephemeris data it loaded. or when a required dependency cannot be identified.
Does determinism validate the interpretation?
No. Determinism makes the computation reproducible; interpretive or predictive validity requires a separate prospective evaluation.
What belongs in the receipt?
The operation, canonical inputs, units, assumptions, dependency versions, outputs, uncertainty treatment, and package digest.
Limits
- Naming a software library does not identify the ephemeris data it loaded.
- Reproducible astronomical arithmetic does not validate an astrological interpretation or prediction.
- No missing number, uncertainty interval, or calculation receipt is invented.