# The Inverse Commons Raymond argued that open source is an "inverse commons" where the grass grows taller when it's grazed upon -- code gains value through use, unlike traditional commons resources that deplete. This is half right and dangerously half wrong. The code itself does behave like an inverse commons. More users means more bug reports, more edge cases discovered, more platforms tested. The software improves through consumption. But the human capacity to manage that consumption is a traditional commons -- rivalrous and depletable. Every issue filed, every support question asked, every PR submitted, consumes maintainer attention that can't be replenished by adding more users. More grazing doesn't grow this grass. It tramples it. This split creates the central sustainability paradox in open source: success makes the code more valuable and the maintainer more overwhelmed at the same time. A project with 10 users and 10,000 users ships the same code, but the maintainer of the second project is drowning in demand the first never faces. The inverse commons of code and the traditional commons of attention pull in opposite directions. Ostrom's design principles -- clear boundaries, graduated sanctions, local autonomy -- apply to the attention side, not the code side. The code doesn't need governance; it's non-rivalrous. The attention does. Defining who can make demands on maintainer time, setting contribution standards that reduce review cost, and creating legitimate ways to say "no" are all commons governance applied to the resource that actually depletes. <!-- atomicity: 1 idea ✓ --> ## Why This Matters Anyone designing open source sustainability programs needs to stop treating the entire system as an inverse commons. The code is. The people aren't. Fund the people, govern the attention, and stop assuming that more usage automatically benefits everyone involved. ## Links - [[3. Resources/Permanent Notes/The Maker-Taker Frame Confuses Two Different Scarcities]] — evidence-for: abundant replicable code and scarce human attention cannot be governed as one contribution ledger - [[3. Resources/Permanent Notes/Stewardship Invests in Contributor Capacity Not Just Cash]] — extends: when code is abundant but attention is scarce, stewardship must grow human capacity rather than merely add resources to the abundant side - [[3. Resources/Permanent Notes/Open Source Projects Are Not Communities by Default]] — evidence-for: open access can concentrate costs on a maintainer core without creating reciprocal membership obligations. - [[3. Resources/Permanent Notes/Maintainer Attention Is the Scarce Resource in Open Source]] — evidence-for: human review and coordination, not replicable code, set the binding limit on the commons - [[3. Resources/Permanent Notes/The Stadium Is the Dominant Open Source Pattern]] — applies-in: abundant users surrounding a small contributor core is the participation shape produced by the inverted scarcity - [[3. Resources/Permanent Notes/Maintenance Is Most of the Work but Gets No Prestige]] — applies-in: scarce maintenance labor remains undervalued even as the code it sustains can be copied without limit - [[3. Resources/Permanent Notes/Ostrom-Theology Crossover - Commons Governance in Faith and Code]] — extends: governance must manage the scarce human capacity around an abundant digital resource - [[3. Resources/Literature Notes/The Maintainer's Burden - Open Source Beyond the Bazaar - Literature Note]] — evidence-for: the source documents the human maintenance burden that the inverse-commons model explains - [[3. Resources/MOCs/Commons & Community Governance MOC]] — cluster context for governance of abundant resources with scarce stewardship capacity - [[3. Resources/Permanent Notes/Coerced Contribution Kills the Commons]] — contrasts: governing harmful accumulation does not justify coercing participation or treating contribution itself as a duty - [[3. Resources/Permanent Notes/WordPress Stores AI API Keys in a Layer Its Own Security Team Says It Cannot Encrypt]] — applies-in: commercial hosts can extract value from shared AI infrastructure while the scarce maintenance burden of closing its security gap remains concentrated upstream. - [[3. Resources/MOCs/Open Source Governance MOC]] — applies-in: the MOC lists this note under Created. ## Source - [[3. Resources/Literature Notes/The Maintainer's Burden - Open Source Beyond the Bazaar - Literature Note]] - [[3. Resources/Readwise/Books/Working in Public]] - [[3. Resources/Readwise/Books/The Cathedral & the Bazaar]] - [[3. Resources/Readwise/Books/Confronting Our Freedom|Confronting Our Freedom]] - [[3. Resources/Literature Notes/Red Hat's Commitment to Open Source - Upholding Values and Sustainability]] — Red Hat's argument that downstream repackaging can starve the paid maintenance that keeps the commons productive