# Run 04 reconstructed equipment mass balance

Run 04 applies independently constructed equipment recipes and proxies to the fixed Run 03 plant inventory. It reports partial equipment stocks in metric tonnes per 1 GW of commissioned IT capacity. Low, base, and high use joint input constructions with fixed equipment counts. Other feasible designs could fall outside their range. Confidence in transfer from the source products to the hypothetical campus is low.

The cumulative modeled base contains about 16.92 kt of copper-grade stock, 2.48 kt of aluminum stock and named alloys, 44.28 kt of disjoint ferrous stock, and 24.0 t of elemental lithium nested within its identified host compounds. The largest incremental historical differences for copper, carbon steel, and aggregate ferrous are in B2 facility equipment. The [generated findings](build/run04/findings.md) show the engineering ranges, leading equipment contributors, replacement effects, and comparison by boundary.

The [comparison CSV](build/run04/reconciliation.csv) includes each endpoint, its display-rounding tolerance, and missing or unreported estimates. The historical source is a [truncated report excerpt](research/run04/historical_findings.md) whose original calculation inputs are unavailable. The archived material-specific envelopes and the reconstructed joint input cases have different uncertainty semantics.

The [coverage register](build/run04/coverage.json) identifies modeled scopes, residual mass budgets, and gaps. High-impact missing inputs include installed conductor route lengths and sections, equipment-specific transformer drawings and material masses, and selected battery and cooling equipment bills of materials. Civil works and unallocated offsite infrastructure remain outside the equipment boundary.

Run `python scripts/reproduce_run04.py` from the repository root to regenerate the outputs offline. Use the [scenario methodology](docs/RUN_04_METHOD.md) and [historical comparison method](research/run04/RECONCILIATION_METHOD.md) to interpret the results. The [manifest](build/run04/manifest.json) records input and output hashes. The [preservation audit](build/run04/preservation.json) compares frozen Run 03 bytes with their original Git blob IDs.
