Thermodynamics of Future Capacity: Data, Code, and Reproducibility Package

This dataset and code release accompanies the manuscript “Thermodynamics of Future Capacity.” It provides the source data, available analysis/simulation and plotting code, model parameters, validation records, and provenance information supporting the quantitative results and Figures 1–4. The study introduces future capacity as an operational measure of how many distinct terminal outcomes can be separately realized from a common initial preparation under finite time, reliability, and physical-resource constraints. The deposited materials cover three complementary stochastic models: a fixed-stiffness moving harmonic trap used to examine resource- and reliability-dependent admission of terminal futures; a multiwell system used to distinguish first-passage accessibility from terminal possession; and a seven-state continuous-time Markov network used to examine how network architecture and declared cost conventions reshape finite-time future multiplicity. The release includes figure-source data, raw and processed numerical records, parameters, available computational and plotting scripts, conditional-envelope and consistency tests, first-passage and terminal-probability data, stationary and wiring-cost sensitivity analyses, and SHA-256 integrity records. In particular, the Figure 4 archive preserves the complete refined continuous-time Markov-chain dataset containing 655,746 protocol records. A historical provenance limitation is explicitly documented for the multiwell calculation associated with Figure 3: the archived numerical outputs and subsequent population, first-passage, and flux-consistency analyses are preserved, but the original Step 5F/5G trajectory solver and its original convergence study were not retained at execution time. Consequently, this component supports archived-output verification rather than solver-level regeneration. No reconstructed code is represented as the original historical solver. This release is version 1.0. Subsequent substantive corrections or additions should be issued as new repository versions so that the exact data and code associated with this release remain permanently identifiable and citable.