Astrology infrastructure

Digest-bound guide

Tradition Rule Set Version provenance contract

What must a machine preserve for tradition rule-set version?

A provenance contract for Tradition Rule Set Version, separating reproducible celestial computation from interpretive and predictive claims.

Bounded answer

Preserve tradition, source edition, rule-set version, technique scope, and prohibited cross-namespace transfers. 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. 1

    Normalize the input without dropping uncertainty.

  2. 2

    Record tradition, source edition, rule-set version, technique scope, and prohibited cross-namespace transfers.

  3. 3

    Run the named deterministic operation.

  4. 4

    Bind inputs and outputs into a receipt.

  5. 5

    Verify the receipt independently before interpretation.

Expected outputs

  • Canonical manifest
  • Calculation or transformation receipt
  • Reproducibility and redaction statement

Refuse when

  • Shared vocabulary does not make two traditions’ rules interchangeable.
  • 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 tradition rule-set version?

Preserve tradition, source edition, rule-set version, technique scope, and prohibited cross-namespace transfers.

Which information must be versioned?

At minimum, preserve tradition, source edition, rule-set version, technique scope, and prohibited cross-namespace transfers, together with the canonical input and output digests.

When should an output be withheld?

Withhold it when shared vocabulary does not make two traditions’ rules interchangeable. 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

  • Shared vocabulary does not make two traditions’ rules interchangeable.
  • Reproducible astronomical arithmetic does not validate an astrological interpretation or prediction.
  • No missing number, uncertainty interval, or calculation receipt is invented.