Built to Last: Stewardship and the Digital Commons

The infrastructure we forget to maintain

We know how to think about a bridge. Someone builds it, someone owns it, and someone is responsible for inspecting and repairing it for the decades it carries traffic. We are far worse at thinking this way about digital infrastructure, the shared software, data, and platforms that increasingly carry public life. We celebrate the launch and forget the upkeep, and then act surprised when a critical system decays, gets captured by a single vendor, or quietly stops being maintained at all. This primer is about treating digital infrastructure the way we treat physical infrastructure: as something that must be governed and stewarded to last, not just built.

The argument is that the hard problem of public-interest technology is not invention but persistence, and that the discipline of keeping shared digital assets alive, accountable, and openly governed over time is its own form of infrastructure work, as essential as the code itself and far more neglected.

What a digital commons is

A digital commons is a shared digital resource, open-source software, open data, an open standard, a public platform, that many institutions can use, contribute to, and depend on, held under rules of access and contribution rather than owned outright by one party. Examples are everywhere in public life: the open-source components beneath government services, the shared data standards that let health systems exchange records, the public platforms that deliver identity, payments, and information at population scale.

The promise of a commons is that its value compounds. Many parties build on the same foundation, improvements made by one benefit all, and no single owner can lock everyone else in or shut the resource down. That promise is real. But it depends entirely on something that does not happen automatically: someone has to steward the commons, or it decays into the digital equivalent of an unmaintained bridge.

Why these assets decay

The failure mode is consistent and worth naming plainly. A great deal of attention goes to launching new digital public goods and very little to the unglamorous labor of keeping them running: the security patching, the dependency management, the documentation, the community governance, the steady maintenance that determines whether a system is trustworthy five years on. That work is often invisible, under-resourced, and carried by a small number of contributors.

The result is a structural mismatch. Many institutions consume shared digital infrastructure without contributing to its upkeep, which is legal but shifts the entire maintenance burden onto a few, and over time risks the very services everyone depends on. Surveys of organizations maintaining open-source projects for public-interest aims find that the top challenge, named by the overwhelming majority, is resourcing for sustainability. And there is a quieter capture risk: when a shared resource has only one real maintainer, that maintainer becomes its de facto owner, and a project that is open in license can become single-vendor in practice, which raises the fair question of whether it is still genuinely a public good at all.

Stewardship is the discipline

The remedy is to treat stewardship as a designed discipline rather than an afterthought. The practices are increasingly well understood: clear contribution policies, funded maintenance and security rather than volunteer goodwill, defined rules about who governs a project and how authority transfers when people move on, and custodians that are explicitly chartered and legally empowered to govern in the public interest. The common thread is that durability is something you build into the arrangements at the outset, not something you hope for after launch.

This is the heart of what I have called governed knowledge infrastructure, here in its most literal form. A digital commons keeps producing public value only when its stewardship, who maintains it, who is accountable, who may use and contribute to it, and how it survives the departure of any one party, is settled before the system becomes load-bearing. The investment a society makes in shared digital infrastructure deserves the same commitment to upkeep as the roads and bridges that connect communities, because it has become just as essential and is just as prone to failure when neglected.

What this means for public-interest infrastructure

Treating digital infrastructure as a commons to be stewarded changes the measure of success. The question is not whether a public-interest system launches and works on day one, but whether it remains secure, open, maintained, and accountable across the years and the personnel changes that follow. That favors investment in the stewardship layer, funded maintenance, clear governance, chartered custodians, over the recurring temptation to celebrate the launch and let the upkeep fend for itself.

This is the Foundation's central concern in its most concrete technical form, and it is the through-line of this series. The other primers take up the specific fronts: how public-interest innovation differs from commercial, how open source functions as infrastructure, how governance and procurement protect the public stake, how open standards prevent lock-in, and how AI built for the public interest must be held accountable. This is the frame beneath them all. The hard part of public-interest technology was never building it. It is building it to last, and that is a question of stewardship.

References

1. United Nations Office for Digital and Emerging Technologies. UN Open Source Week 2025. The invisible labor of open-source maintainers; security patching, governance, dependency management, and the need for policy and funding to support maintenance, not just development. https://www.un.org/digital-emerging-technologies/content/open-source-week-2025

2. Dries Buytaert. Funding Open Source like public infrastructure (2026). Institutions consuming open source without contributing shift maintenance costs onto a few; the digital foundation of public services needs the investment of roads and bridges. https://dri.es/funding-open-source-like-public-infrastructure

3. Public Digital. Digital public goods. ~500 active open-source projects with social objectives; 94% of surveyed partners named resourcing for sustainability as their top challenge; single-vendor custody and the need for chartered custodians. https://public.digital/pd-insights/signals/signals-5/digital-public-goods

4. Digital Public Goods Alliance. Our policies to unlock the promise of digital public goods (2025). Funded maintenance, permanent funds for critical software, contribution policies, and clear rules on project duration and transfer. https://www.digitalpublicgoods.net/blog/our-policies-to-unlock-the-promise-of-digital-public-goods

5. Linux Foundation Europe. Building Digital Public Infrastructure Through Open Source: Key Insights from UN Open Source Week 2025. Open Source Program Offices and avoiding proprietary dependency at scale. https://linuxfoundation.eu/newsroom/building-digital-public-infrastructure-through-open-source-key-insights-from-un-open-source-week-2025