Derivations and Reproducibility
A v9 Derivation records how an artifact was computationally produced.
inputs
+ transform
+ parameters
+ toolchain/policies
→ outputs
This is build lineage, not epistemic authority.
EPISTEMIC PROVENANCE != BUILD PROVENANCE
Exact-input rule
A deterministic derivation must declare every input that can affect output, or eliminate that variability.
Typical inputs include:
- source snapshot/commitment;
- schemas;
- transform version;
- configuration;
- policy;
- random seed;
- locale when relevant;
- external datasets.
A strong deterministic build must not read unpinned mutable network state.
Change pruning
An implementation may rebuild an artifact after source bytes change and discover that the resulting logical commitment is unchanged.
source bytes changed
↓
recompute
↓
same logical commitment
↓
no logical downstream invalidation required
This is an optimization; the normative requirement is that declared commitments remain correct.