Ostrom spent her career documenting communities that govern shared resources
without either privatising them or handing them to a central authority — and
without collapsing into the tragedy the textbooks predicted. The finding was not
that people are nice. It was that durable commons share a small set of design
features, and every one of them is about *maintenance*, not founding.
Decentralisation is not a state you achieve. It is a practice you keep paying for.
Ostrom's principles — clearly defined boundaries, rules matching local conditions,
users who participate in modifying the rules, monitoring by the users themselves,
graduated sanctions, cheap conflict resolution — are all *after* the launch. There
is no design-principle-shaped artefact you can ship once. Every system recentralises
unless the people using it actively push back, because a centre is the path of least
resistance and the path of least resistance is where all systems drift.
The X1 pitch is decentralisation as an architectural property: permissionless,
no gatekeeper, no owner. Ostrom's data says the architecture is the easy part and
also the part that decays. The question is not whether the protocol *is*
decentralised but whether anyone is performing the maintenance that keeps it that
way — who monitors, who sanctions, who resolves disputes cheaply enough that people
bother.
Stop treating "decentralisation" as a state and start treating it as a maintenance
practice — every system recentralises unless the people using it actively push back.
Build a lightweight validator peer-review channel (not a governance forum, a direct
comms line) where validators flag each other's missed slots before the protocol
does, because protocol penalties are *exit* events and peer nudges are *voice*
events.
Who on X1 is currently doing the maintenance work Ostrom says keeps a commons from recentralising — and is anyone paying them?