Reproducibility
Immutable inputs
A run points to fixed versions of its datasets and model implementations. These inputs cannot be changed after the run. Any change produces a new run with a new manifest.
Run manifests
The manifest records what a run used, including its datasets, model implementations, code commit, configuration and runtime environment. It is the record needed to identify a run and repeat it.
Code and environment identity
Public research links the source commit and deployable environment or dependency lock needed to understand the software state. Reproducibility does not rely on the phrase current version.
Artifacts and checksums
Source archives, normalised data, model executables, run manifests, result files and release bundles carry SHA-256 digests where practical. A released artifact is never replaced under the same identity.
Independent reruns
Before a benchmark release, OpenDeco reruns the work from its recorded inputs and compares the new outputs against the originals, within documented numerical tolerances. Differences are investigated before publication.
Version changes
Scientific corrections create new dataset, model, protocol or release versions. Previous versions remain identifiable. A version that a correction replaces is marked as superseded.
Citation
Each release carries citation metadata so a paper, dataset, model or benchmark version can be cited exactly.