Skip to main content

The Commons

What stops a shared resource from being captured by those who manage it rather than use it?

A self-governing commons holds its value only when its design replenishes what it draws.

Shared resources collapse in one of two ways. Members take more than the system can replenish — the classic tragedy. Or a manager appears, extracts fees for access, and the resource that was shared becomes tribute.

The second failure is subtler. It looks like governance. It is capture.

Elinor Ostrom spent a career studying communities that avoided both. Her finding: self-governance works when eight structural conditions are present. [source: Ostrom, Governing the Commons, 1990]

The Eight Principles​

1. Boundaries are clear. Members know who is in and who is out. The resource has defined edges. Without this, anyone can draw without belonging, and no one is accountable.

2. Rules match local conditions. The community writes its own rules. Outside rules imposed by distant authorities routinely fail because they cannot account for local ecology, history, or trust.

3. Members shape the rules. Those affected by a rule have a credible voice in changing it. Imposed rules breed evasion. Owned rules breed compliance.

4. Use is monitored. Either members monitor each other, or monitors are accountable to members. Invisible extraction destroys a commons faster than visible overuse — you cannot correct what you cannot see.

5. Sanctions are graduated. A first violation earns a small penalty. Repeat violations escalate.

Immediate harsh punishment poisons trust. No punishment at all invites free-riding. Escalation signals proportionality.

6. Conflict resolution is fast and cheap. Disputes that drag on or cost more to resolve than the disputed resource is worth will accumulate. Accessible, low-cost arbitration keeps disagreements local and contained.

7. The right to organise is recognised. External authorities do not constantly override local governance. Self-governance cannot survive if outside power reliably nullifies its decisions.

8. Governance is nested. Large commons embed smaller ones. Each layer governs its own domain; layers coordinate through protocols, not hierarchy. This is the principle that makes federation work — and makes a central authority unnecessary.

Cognitive Boundaries​

Communities have natural size thresholds. Push past them and trust degrades.

[source: Dunbar, Grooming, Gossip, and the Evolution of Language, 1996]

  • ~5 people — inner circle. High enough trust to lend without tracking.
  • ~15 people — sympathy group. Emotional support flows freely. Loss is felt personally.
  • ~50 people — close community. You know everyone's story. Reputation is direct.
  • ~150 people — maximum natural community. Beyond this, coordination requires formal structures.

These are not hard walls. They are heuristic thresholds where trust mechanisms change. A community under 150 can run on reputation and direct relationship. A community over 150 needs protocols.

The design implication: federate before you centralise. When a group exceeds its cognitive threshold, split it into nested groups. Coordinate by shared standards — not by appointing someone to manage the whole.

Goodwill Commons​

Every organisation draws on goodwill: the stored trust, generosity, and good faith that members extend to each other and to the institution. Goodwill is the intangible commons.

It is easy to draw on and slow to replenish. It does not appear on a balance sheet. The risk: depletion is invisible until behaviour changes — and by then, significant damage is done.

The Integrity Test: a system has integrity if — and only if — it replenishes what it draws.

Apply it to every governance decision:

  • Does this policy draw on goodwill (asking members to absorb cost) or replenish it (giving members more agency, transparency, or benefit)?
  • Does this process require trust in an authority — or does it make trust unnecessary by encoding it in a verifiable standard?
  • When this institution grows, does coordination get cheaper or more expensive?

A system that fails the Integrity Test is harvesting the commons. It may grow for a time on the stored goodwill it draws. Eventually, the commons is exhausted and coordination collapses.

The Design Checklist​

Run this before formalising any shared resource:

  • Boundaries defined? Who is in, what is shared, what is not.
  • Rules locally written? Not imported wholesale from outside.
  • Members shaping rules? Not subject to them.
  • Use visible? Someone is monitoring and accountable to users, not to management.
  • Sanctions graduated? Small penalty first, escalation for repeat violations.
  • Conflict resolution accessible? Fast, cheap, local.
  • Right to organise protected? External override is the exception, not the default.
  • Size within cognitive threshold? If not, a nesting plan exists.
  • Integrity test passing? The system replenishes what it draws.

Context​

  • Feedback Loops — The corruption of a commons is a vicious loop: the setpoint shifts from the shared resource to defending the structure that manages it
  • Governance — How these principles apply to institutions and protocols at scale
  • Incentive Design — The mechanism layer: how to make drawing on the commons more costly than replenishing it
  • Governance Problems — What happens when commons design fails
  • Scoreboard Reality — How to measure whether a commons is replenishing or harvesting

Questions​

Which of the eight principles is hardest to maintain as an organisation grows — and why does growth make it harder?

  • How do you monitor goodwill depletion before behaviour changes signal it?
  • At what point does a federated network of small groups need a coordination protocol — and what is the minimum viable protocol that avoids centralising control?
  • When a community exceeds its cognitive threshold, what is the signal to split rather than formalise hierarchy?