Shipping Reproducible Results

Ship an evidence-bearing result, not merely code that once ran. The package must connect the approved question to immutable inputs, an executable workflow, generated outputs, validation evidence, and an explicit handoff boundary.

Freeze the result contract

Before packaging, record:

• the approved question, population, unit of analysis, time window, and exclusions;
• the exact claims and acceptance criteria being delivered;
• which outputs are authoritative and which are exploratory;
• the source snapshot or retrieval contract, including access limitations;
• the intended execution environment and supported operating scope.

Do not silently expand a validated result from a sample to a population, from retrospective analysis to prospective use, or from one environment to another.

Build the provenance chain

Make each authoritative output traceable through: