A rerunnable record identifies the method, code, environment, inputs, configuration, operator, raw outputs, and acceptance rule precisely enough for another authorized person to attempt the same run. Matching run records are necessary but insufficient evidence for scientific reproducibility.
Test whether a new operator can execute the same boundary
Give an authorized operator the ledger row and no oral context. They should be able to find the code, provision the stated environment, obtain the approved input, run the command or protocol, and locate the resulting artifacts. Every undocumented credential, manual edit, hidden notebook state, or missing dependency becomes a gap in the record, even if the original operator remembers it.
Compare conditions before comparing outputs. Hardware, provider version, dependency resolution, random state, dataset snapshot, and external services may differ. Record those differences and use the original acceptance rule. An exact numerical match may be unreasonable for some stochastic systems, while a deterministic pipeline should explain any divergence rather than hiding it inside a broad tolerance.
Report the rerun as evidence, not certification
The acceptance report should show what was attempted, by whom, with which versions, which steps completed, where outputs differ, and which artifacts support the comparison. A missing source is a documentation failure. An environment that cannot be recreated is an operability finding. A completed run outside tolerance is a result that the research owner must interpret.
A ledger improves inspectability and makes repeated work easier to detect. It cannot establish scientific validity, generalize a result beyond tested conditions, decide research misconduct, or replace domain review. Those boundaries should appear beside any statement that an experiment was rerun or that its evidence was recovered.
Where the service stops
Reality Contact, LLC implements evidence organization and retrieval, but does not certify scientific validity, reproducibility, research integrity, regulatory compliance, safety, authorship, or the correctness of any experimental conclusion. The buyer approves the record schema and storage boundary, verifies scientific interpretations, controls access and retention, and decides which evidence supports the next experiment, publication, or funding choice. This is technical record organization and implementation; it does not replace legal, medical, scientific, safety, compliance, or professional advice. A complete ledger improves traceability but does not certify that a result is valid, reproducible, safe, ethical, or suitable for publication or regulation.
Sources: NIST information quality and reproducibility standards; NIH Data Management and Sharing Policy.