# Neutral Governance Converts Rivalry Into Shared Infrastructure ## Claim When a neutral third party — not any single competing company — owns the governance of shared infrastructure, direct competitors will co-fund and co-build it rather than duplicate it separately. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds when the infrastructure is genuinely foundational and non-differentiating (security response, base platforms) and no single funder can credibly claim control over governance decisions. - Breaks down if one contributor is perceived to have outsized influence over governance — the moment neutrality looks compromised, the coalition's rationale collapses. - Requires the neutral body to have actual operational teeth (staffing, process, confidentiality controls), not just a shared brand — a coalition with no working mechanism doesn't convert rivalry into anything. ## Evidence The Linux Foundation launched Akrites specifically because AI-driven vulnerability scanning was surfacing findings faster than any single maintainer or company could triage — in one measured month, only about one in seven of 530 reported vulnerabilities had a confirmed patch. Rather than each AI lab or cloud provider building its own separate response pipeline, the presenter frames Akrites as following the same pattern as CNCF's Kubernetes donation and Alpha Omega: competitors fund shared infrastructure once a neutral foundation holds its governance. > [!quote] > "The success of this effort will be measured in patch deployment and not publication." ## Links - [[3. Resources/Permanent Notes/Maintainer Attention Is the Scarce Resource in Open Source]] — because applies-in; neutral-governance coordination is one response to the scarce-attention problem this note already names - [[3. Resources/Permanent Notes/In-Kind Labor Hides How Dependent a Commons Is on a Single Backer]] — because contrasts; that note flags a risk this pattern is meant to avoid — a commons that looks neutral but is actually dependent on one funder - [[3. Resources/MOCs/Open Source Governance MOC]] — because applies-in; another data point in the vault's running catalog of neutral-foundation governance patterns ## Tests / falsifiers - If Akrites' patch-deployment rate over its first year measurably beats the pre-Akrites baseline (1-in-7 confirmed-patch rate), that's direct evidence the neutral-governance structure works operationally, not just rhetorically. - If a founding member is later shown to have effective veto power over Akrites' triage or disclosure decisions, the "neutral" framing fails and the pattern reduces to one company's infrastructure wearing a foundation's name. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Readwise/Articles/Akrites Explained Open Source's New Emergency Team]] — the video's full account of Akrites' design, the AI-scanning volume problem it responds to, and the CNCF/Alpha Omega precedents cited.