Skip to research
Vraelis Research
All researchVraelis Imprint / Reference note and proposed protocol

Provenance for a simulation run

Retain enough context to connect a result to its inputs and transformations.

Research note · November 14, 2026

Research question

What should accompany a plot so another engineer can reconstruct its origin?

Method

  1. Assign separate identifiers to the model, code, input trace, configuration and output record. Capture the activity that combines them into a run, including software versions and execution parameters.
  2. Preserve transformations such as resampling, unit conversion and filtering as explicit steps. Keep raw inputs available where permitted rather than retaining only a polished output figure.
  3. Create a revised model and rerun the same conditions. Compare output changes while linking each result to the correct model and preprocessing revisions.

Records to retain

  • Input and model identifiers
  • Transformation records
  • Execution environment
  • Raw outputs and derived figures

Source basis

W3C PROV distinguishes entities, activities and agents, and SLSA provenance records inputs and execution details for builds. These concepts can inform simulation records without implying that a simulation is a software build.

Interpretation & limits

A complete-looking manifest can contain false information. Provenance records need source trust and retention policies; their existence does not validate the modeled physics.

Next experiments

  • Define a minimal manifest for one bounded run.
  • Check whether every plotted quantity can be traced to an output record.

References

  1. W3C PROV overview
  2. SLSA provenance specification

Technical reference

Implementation details supporting this note, drawn directly from the maintained documentation. These are technical references, not additional papers or new experimental results. Expand a topic to inspect its method, fields and limits.

Related notes