The Unpaid Maintainer Problem

Across the Factum corpus, a single pattern repeats: foundational systems were built on assumptions of infinite capacity and perpetual volunteer or legacy maintenance, then scaled far beyond those assumptions. The Colorado River Compact’s 1.5-million-acre-foot over-allocation, the single unpaid PHP maintainer patching 2.58 million hosts, France’s 112 % debt-to-GDP ratio amid pension riots, Oracle’s 1,209-CVE October CPU, the F-35 10-year production lock-in, and Berget.ai’s 8.5× grid-emission variance for identical AI workloads all describe the same mismatch. Each domain treats its base layer (allocation rules, open-source code, sovereign balance sheets, firmware, defense contracts, power infrastructure) as a fixed substrate rather than a living, capacity-constrained system. When reality exceeds the substrate, the response is always the same: an individual or small team applies a patch while the underlying allocation model remains untouched. The Iran nuclear advocacy after leadership strikes and the Unitree H2-X dual-use demo simply extend the pattern into geopolitics and robotics: once the old maintenance contract is broken, actors reach for higher-leverage, higher-risk substitutes.