Reproducibility Package
Downloading and interpreting the reproducibility package: what files it contains, what the manifest covers, when the download is enabled, and how provisional export is disclosed.
A reproducibility package is a single ZIP file that combines the canonical server-generated reproducibility bundle with browser-captured figure exports and a short package note describing how the ZIP was assembled.
What is included
The package contains two layers of files.
Canonical core files
These files are generated on the server and are covered by the manifest's bundle hash:
| File | Contents |
|---|---|
fig_ir.json | Canonical figure specification |
stats_meta.json | Statistical metadata and test output |
version_snapshot.json | Application, ruleset, and stats engine versions |
plotly.json | Plotly figure specification |
preprocess_report.json | Preprocessing steps applied before rendering |
raw.csv | Original uploaded data |
processed.csv | Data after preprocessing |
statistical_results.csv | Statistical results table when available |
methods_summary.md | Auto-generated methods summary when available |
README.md | Bundle usage notes |
manifest.json | File inventory and integrity metadata |
repro.py | Python re-render helper |
repro.R | R re-render helper |
Some optional files are omitted when the current figure does not produce them. When that happens, the omission is recorded in manifest.json.
Supplemental package files
These files are added in the browser when you download the package:
| File | Contents |
|---|---|
exports/figure.png | PNG captured from the live browser render |
exports/figure.svg | SVG captured from the live browser render |
PACKAGE_NOTES.md | Snapshot metadata, omitted-file notes, and SHA-256 checksums for the supplemental exports |
The supplemental files are intentionally not part of the canonical manifest bundle hash. PACKAGE_NOTES.md records their checksums separately and explains that they were captured from the browser render at package build time.
How to download
The reproducibility package is downloaded from the Figure tab of the figure view.
The download button becomes available when:
- A reproducibility bundle artifact already exists for the figure
- The figure plot has finished rendering in the current browser session
- There are no pending figure edits that must still be committed or discarded
The button is disabled when:
- A reproducibility bundle has not yet been generated for the figure
- The plot is not yet ready in the Figure tab
- The figure is mid-edit and the current changes are still uncommitted
Integrity verification
manifest.json records the canonical core inventory and bundle hash. This lets collaborators verify that the server generated files still match the bundle that Licklider created.
The browser-captured PNG and SVG files are not covered by that canonical bundle hash. Instead, their SHA-256 values are written into PACKAGE_NOTES.md.
This split is deliberate:
- The canonical core stays stable and machine-checkable
- The exported images preserve what you saw in the browser when the package was downloaded
Export guard and provisional downloads
Licklider checks export eligibility before packaging the ZIP. If claim-bearing export is already allowed, the package downloads normally.
If claim-bearing export is still blocked but provisional export is allowed, Licklider can still assemble the package as a provisional reproducibility package. In that case, the package is downloadable, but the audit trail records that unresolved figure-safety issues remained at export time.
This means the package is useful for traceability and review, but it should not be treated as clean claim-bearing output until the unresolved checks have been addressed.
In a future update, the Project Audit report is expected to be available for inclusion in the reproducibility package so that project-level statistical consistency can be preserved alongside figure-level provenance.