Appendix: reproducibility steps and the ATL

Appendix: reproducibility steps and the ATL DataPack schema — This appendix pins down “who runs what where, and which log/output must appear.” In a real release, paths/file names/hashes below must be finalized in the reproducibility bundle. Recommended required outputs: (1) UNLOCK_checklist.txt, (2) omega_nogo.json, (3) an RSL summary table (CSV), and (4) a QA report (MD/PDF).

This appendix pins down “who runs what where, and which log/output must appear.” In a real release, paths/file names/hashes below must be finalized in the reproducibility bundle.

This appendix pins down “who runs what where, and which log/output must appear.” In a real release, paths/file names/hashes below must be finalized in the reproducibility bundle.

(Example) execution steps

# 0) Environment setup (example): Python 3.11 + requirements.txt
python -V
pip install -r requirements.txt

# 1) Verify data integrity
sha256sum -c checksums/sha256sum.txt

# 2) Verify prereg thresholds (Omega-NoGo) are fixed
cat config/constraints.yml

# 3) Run hard gates PASS/FAIL
python tests/tests_hardgate.py --constraints config/constraints.yml --results_dir results/

# 4) Check outputs
cat results/UNLOCK_checklist.txt

Recommended required outputs: (1) UNLOCK_checklist.txt, (2) omega_nogo.json, (3) an RSL summary table (CSV), and (4) a QA report (MD/PDF). Without these, the release is “narrative” rather than “reproducible.”

ATL DataPack v0.9 (schema stub): file/field/codebook schema

This appendix defines the minimum data modules (files/fields) required to make predictions P1–P5 executable. Important: file names/fields/units here must be fixed by preregistration before release and checksum-sealed after release.

{

}

Recommended use of an additional field basin_type. For the P3 contrast (including the Indian Ocean), assign each RSL point a basin_type. Recommended values: PACIFIC, ATLANTIC, INDIAN. (basin is the geographic basin name, while basin_type is the mechanism-class label.)

Extension modules (optional): supporting P6/P8 (ATL DataPack v0.2 draft)

P6 (spatiotemporal propagation) and P8 (magnetic stripes) can require more complex data composition than P1–P5. Therefore, minimal schemas are separated as optional extension modules (the core compile/hard-gate can run without them).

{

}

Cross-validation extension modules (optional): supporting P9/P10/P11/P12 (ATL DataPack v0.3 draft)

The modules below are not mandatory hard gates for C1–C3, but are included for independent cross-validation of “event-like” claims.

{

}

Minimum codebook/provenance requirements (common to all modules).

• docs/codebook.md: field definitions, units, missing-value rules, QC rules (PASS/FAIL).
• docs/provenance.md: raw-data sources/access date, cleaning rules, exclusion criteria (pre-registered).
• checksums/sha256sum.txt: SHA256 hashes of all files.

ATL DataPack v0.8 draft (v1.34): hydro/climate/friction/isotope extension modules

This extension schema is not for the base mechanism (C1–C3), but for locking mandatory gates of additional variants (V-SLIP / V-HOLO / V-COUPLED) into data.

{

(A) Mechanism / hydro / climate / kinematics modules

(B) Resource / sediment / discovery-bias modules

}