Reproducibility
OpenDeco treats data versions, code versions, model configuration, runtime environment and output artifacts as part of the scientific record.
Immutable inputs
A frozen run references immutable dataset versions and model implementations. Mutable working state cannot be substituted after the run without creating a new manifest.
Run manifests
The manifest records the protocol, datasets, model implementations, configurations, code commit, runtime image, metric versions, random-seed policy and artifact identities used for the run.
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, normalized data, model executables, run manifests, result files and release bundles receive cryptographic hashes where practical. A released artifact is not silently replaced under the same identity.
Independent reruns
Before a paper-grade or benchmark release, OpenDeco performs a clean rerun from frozen inputs and compares artifacts or documented numerical tolerances. Mismatches are investigated before publication.
Version changes
Scientific corrections create new dataset, model, protocol or release versions. Previous public versions remain identifiable and are marked as superseded when appropriate.
Citation
Releases include human-readable and machine-readable citation metadata so a paper, dataset, model implementation or benchmark version can be referenced precisely.