Hardin's 1968 Science essay assumed an unregulated pasture. In 1998 he wrote that the weightiest mistake was leaving out the adjective "unmanaged." Ostrom's Governing the Commons (1990) is the empirical reply, and it has records, not slogans.
Törbel in Valais has written commons rules from 1224; Robert Netting's Balancing on an Alp is the ethnography Ostrom used. Valencia's Tribunal de las Aguas still sits on Thursdays at the cathedral door and has for centuries. Maine lobster "harbor gangs" (Acheson, The Lobster Fiefs, 1975; The Lobster Gangs of Maine, 1988) held inshore territories by gossip, ostracism, and the occasional cut trap long before the 1995 Zone Management Law put seven Zone Councils on the statute book.
The eight design principles are specific: clear users and resource edges, monitors who are the users or answer to them, graduated sanctions, cheap conflict arenas, nested enterprises when the system is large. Cox, Arnold, and Villamayor-Tomás (Ecology and Society, 2010) went back through 91 later studies. The principles hold reasonably at common-pool scale. They sag when users are undefined, the resource moves, or monitoring is expensive. Newfoundland's 1992 cod moratorium is the failure shape; inshore lobster is the success shape. The post lists "tragedy of the commons" as a cousin of the cascade. The cousin has a thirty-year field literature that does not all go one way.
Not a footnote, and not a rival of "change selection."
Ostrom's move is polycentricity: many nested rule-makers, cheap local monitoring, users who cannot dump the problem next door. Sanctions change payoffs; they are already a change in what gets selected. Ostrom, Walker and Gardner (APSR 1992) compare communication, sanctions, and both — not councils versus geometry.
The live split is who can revise the rules, who monitors, who can impose consequences, and at what scale that works. Maine's 1995 Zone Councils and Valencia irrigation are templates for crisp boundaries and cheap monitors. Carbon, engagement ranking, and frontier training runs may fail those conditions. That is a scale-and-authority question, not "if Ostrom is right, skip the constitution."
I'll give you that. The related-concepts section already says the tragedy of the commons, principal-agent problems, and capture are not the same machine as the cascade, and that a transfer has to keep the causal roles. I was restating a distinction the post made.
What is still open is whether Ostrom's nested enterprises are that three-layer design under another name (users as the doing layer, local rules as the constraint, markets or the state as the strategy) or a different class of repair that never needs a privileged constraint the players cannot touch. If they collapse into the same design, the post should just cite her. If they don't, the split in the parent comment is the actual disagreement.