{"id":"341e0d7a-5410-499d-bc17-bb6b93f9672a","entityType":"agent","slug":"clawhub-deciqai-tragedy-of-the-commons","name":"Tragedy of the Commons","canonicalUrl":"https://www.xpersona.co/agent/clawhub-deciqai-tragedy-of-the-commons","canonicalPath":"/agent/clawhub-deciqai-tragedy-of-the-commons","generatedAt":"2026-10-11T07:44:41.694Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T04:38:08.246Z","emptyReason":null},"description":"Activate when: shared resource is degrading even though no one is doing anything \"wrong\"; team complains about free riders or overuse; designing API quotas,... Skill: Tragedy of the Commons Owner: deciqai Summary: Activate when: shared resource is degrading even though no one is doing anything \"wrong\"; team complains about free riders or overuse; designing API quotas,... Tags: latest:1.0.6 Version history: v1.0.6 | 2026-07-16T18:20:00.125Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/tragedy-of-the-commons.json) v1.0.5 | 2026-07-09T11:","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:tragedy-of-the-commons","sourceUrl":"https://clawhub.ai/deciqai/tragedy-of-the-commons","homepage":"https://clawhub.ai/deciqai/skills/tragedy-of-the-commons","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/deciqai/tragedy-of-the-commons","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/deciqai/skills/tragedy-of-the-commons","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":61,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Activate when: shared resource is degrading even though no one is doing anything \"wrong\"; team complains about free riders or overuse; designing API quotas,... "},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T04:38:08.246Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T04:38:08.246Z","emptyReason":null},"stars":null,"forks":null,"downloads":1157,"packageName":null,"latestVersion":"1.0.6","tractionLabel":"1.2K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T04:38:08.168Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T04:38:08.246Z","lastCrawledAt":"2026-10-11T04:38:08.168Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T04:38:08.168Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.6","createdAt":"2026-07-16T18:20:00.125Z","changelog":"Description tail link + agents machine-readable metadata line (deciqai.com/s/tragedy-of-the-commons.json)","fileCount":7,"zipByteSize":16397},{"version":"1.0.5","createdAt":"2026-07-09T11:22:33.862Z","changelog":"Refresh: 2024-2026 AI-era worked examples added (strategy/leadership + systems/game-theory batch)","fileCount":7,"zipByteSize":16423},{"version":"1.0.4","createdAt":"2026-07-08T11:23:38.834Z","changelog":"Footer now uses /c/ short link (fixes UTM truncation when SKILL.md is read in a terminal)","fileCount":6,"zipByteSize":12005},{"version":"1.0.3","createdAt":"2026-07-08T03:52:48.089Z","changelog":"Second primary-sourced worked example","fileCount":6,"zipByteSize":11822},{"version":"1.0.2","createdAt":"2026-07-08T01:08:08.831Z","changelog":"Refreshed content + GitHub star link in footer","fileCount":5,"zipByteSize":9131},{"version":"1.0.1","createdAt":"2026-07-07T22:34:27.115Z","changelog":"Add catalog categories and topics","fileCount":5,"zipByteSize":8832},{"version":"1.0.0","createdAt":"2026-07-03T14:17:34.786Z","changelog":"Initial publish","fileCount":5,"zipByteSize":8845}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:tragedy-of-the-commons","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-tragedy-of-the-commons/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-tragedy-of-the-commons/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-tragedy-of-the-commons/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-tragedy-of-the-commons/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-tragedy-of-the-commons/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-tragedy-of-the-commons/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T07:44:41.690Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-tragedy-of-the-commons/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-tragedy-of-the-commons/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-tragedy-of-the-commons/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-tragedy-of-the-commons/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T04:38:08.246Z","emptyReason":null},"readme":"Skill: Tragedy of the Commons\n\nOwner: deciqai\n\nSummary: Activate when: shared resource is degrading even though no one is doing anything \"wrong\"; team complains about free riders or overuse; designing API quotas,...\n\nTags: latest:1.0.6\n\nVersion history:\n\nv1.0.6 | 2026-07-16T18:20:00.125Z | user\n\nDescription tail link + agents machine-readable metadata line (deciqai.com/s/tragedy-of-the-commons.json)\n\nv1.0.5 | 2026-07-09T11:22:33.862Z | user\n\nRefresh: 2024-2026 AI-era worked examples added (strategy/leadership + systems/game-theory batch)\n\nv1.0.4 | 2026-07-08T11:23:38.834Z | user\n\nFooter now uses /c/ short link (fixes UTM truncation when SKILL.md is read in a terminal)\n\nv1.0.3 | 2026-07-08T03:52:48.089Z | user\n\nSecond primary-sourced worked example\n\nv1.0.2 | 2026-07-08T01:08:08.831Z | user\n\nRefreshed content + GitHub star link in footer\n\nv1.0.1 | 2026-07-07T22:34:27.115Z | user\n\nAdd catalog categories and topics\n\nv1.0.0 | 2026-07-03T14:17:34.786Z | user\n\nInitial publish\n\nArchive index:\n\nArchive v1.0.6: 7 files, 16397 bytes\n\nFiles: examples/ai-era-commons-open-web-power-gpus-2024-2026.md (8547b), examples/grand-banks-cod-collapse-and-1992-moratorium.md (5171b), examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md (5592b), references/sources.md (2333b), skill-card.md (2373b), SKILL.md (8244b), _meta.json (141b)\n\nFile v1.0.6:SKILL.md\n\n---\nname: tragedy-of-the-commons\ndescription: >\n Activate when: shared resource is degrading even though no one is doing anything \"wrong\"; team complains about free riders or overuse; designing API quotas, rate limits, or open-source governance; someone says \"everyone is overusing this\" or \"the system worked fine until it got popular\"; evaluating why a platform or community is burning out.\n Do NOT activate when: the resource is fully non-rival (unlimited supply, zero marginal cost); the problem is a purely individual-action issue with no shared resource.\n More: deciqai.com/c/tragedy-of-the-commons\n---\n\n# Tragedy of the Commons\n\n## Overview\n\nWhen a shared resource has individual access but no individual responsibility for preservation, rational users extract private benefit while the cost of overuse is shared — leading to collective degradation. Garrett Hardin named this in 1968; Elinor Ostrom corrected it in 1990 (Nobel 2009): many communities self-govern commons via her 8 design principles without privatization or coercion.\n\nComposes with `prisoners-dilemma`, `principal-agent`, `network-effects`, `goodharts-law`, `repeated-games-reputation`.\n\n## When to Use\n\n- Diagnosing why a shared resource is degrading (open-source burnout, API abuse, attention market polarizing)\n- Assessing AI-era shared-resource strain from AI capex and AI-native competition (open web scraped for training data, grid/power capacity, GPU allocation)\n- Designing platforms, marketplaces, shared infrastructure, API quotas, or rate limits\n- Designing workplace norms around shared resources (meetings, Slack, email)\n- Evaluating regulatory or policy responses to shared-resource problems\n\n**Not when:** resource is genuinely non-rival; fully private; \"commons\" framing is misapplied to individual-action problems.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete commons case → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line: when a shared resource degrades despite each user acting rationally, you have a commons problem — the answer is institutional design per Ostrom's 8 principles, not just \"privatize\" or \"regulate.\"\n2. Check fit: shared resource + individual extraction + shared cost? If not, different frameworks apply.\n3. Elicit the resource, users, and current rules: What's shared? Who has access? What rules govern use? What's failing?\n> **[WAIT — do not advance until user responds]**\n4. Audit which of Ostrom's 8 principles are present / weak / absent in their situation.\n> **[WAIT — do not advance until user responds]**\n5. Close: name the institutional gaps + propose design applying missing principles + monitoring plan.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Identify:** shared resource · user community · failure mode · current rules.\n**Step 2 — Verify commons structure:** shared access + rivalrous + diffuse responsibility + Hardin pattern (individually rational, collectively destructive). All four yes → commons.\n**Step 3 — Ostrom audit** (mark present / weak / absent): 1 Boundaries · 2 Congruence · 3 Collective-choice · 4 Monitoring · 5 Graduated sanctions · 6 Conflict resolution · 7 Right to organize · 8 Nested enterprises. Weak/absent = design targets.\n**Step 4 — Intervene:** for each weak/absent principle, design a specific fix. Avoid the \"privatize or regulate\" binary — Ostrom's institutional design often outperforms both.\n**Step 5 — Monitor:** sequence · metrics (resource health, sanctions issued) · quarterly review.\n\n## Output Template\n```\nCommons Design: \nStructure: shared resource | boundaries | failure mode | current rules\nVerification: shared Y/N · rivalrous Y/N · diffuse responsibility Y/N · Hardin pattern Y/N\nOstrom audit: [1–8: present/weak/absent]\nIntervention: [per weak/absent principle] · why not privatize · why not pure regulation\nImplementation: sequence · metrics · review cycle\n```\n\n*→ Method in Action: [Hardin 1968 + Ostrom's Empirical Correction + Modern Digital Applications](examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md) · [Grand Banks Cod Collapse](examples/grand-banks-cod-collapse-and-1992-moratorium.md)*\n*→ 2026 lens: [The AI-Era Commons — Open Web, Power, and GPUs (2024–2026)](examples/ai-era-commons-open-web-power-gpus-2024-2026.md)*\n\n## Pack: Commons Patterns\n\n| Commons | Failure mode | Ostrom countermeasure |\n|---|---|---|\n| Open-source project | Maintainer burnout | Contribution rules; governance council; sustaining funding |\n| API / cloud infrastructure | Abuse degrades service for all | Tiered quotas; monitoring; graduated sanctions |\n| Slack / meetings | Notification overload | Norms; meeting-free blocks; signal-noise metrics |\n| Fisheries / antibiotic efficacy | Stock collapse / resistance | Quotas; stewardship programs; surveillance |\n| Atmospheric carbon | Climate change | Carbon pricing; international agreements; local action |\n\n## Applying It Well\n\n- Ostrom's 8 principles are load-bearing, not optional: missing several reliably produces Hardin tragedy.\n- Privatization works when exclusion is feasible and transaction costs are low. Regulation works when the regulator has information and legitimacy. Ostrom's self-governance works when users can communicate, monitor, and self-organize — often best for technical commons.\n- Peer monitoring (users see each other's behavior) differs from punitive surveillance; successful commons use the former.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"Commons always fail; we have to privatize\" | Hardin over-stated this. Ostrom's empirical evidence: many commons endure for centuries with the 8 principles. |\n| [D] \"The government must regulate\" | Sometimes. Often community self-governance is faster, cheaper, and more legitimate. |\n| [D] \"Punish free riders; that's enough\" | Graduated sanctions is one of 8 principles. Punishment alone without monitoring, boundaries, etc. doesn't work. |\n| [D] \"Open source means free; we don't owe anything\" | Maintainer labor is a commons; without contribution mechanisms it depletes (xz 2024 was the warning). |\n| [D] \"Our users would never abuse the API\" | The Hardin structure predicts abuse from a substantial fraction regardless of intent. Design accordingly. |\n| [D] \"We don't need formal governance; people are reasonable\" | Even reasonable people benefit from boundaries, monitoring, and conflict resolution. |\n| [D] \"Monitoring is surveillance; we don't do that\" | Ostrom distinguishes cooperative peer-monitoring from punitive surveillance. Successful commons use the former. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Shared resource degrading; rules unclear or unenforced\n- Free-rider complaints but no graduated sanctions exist\n- Users have no voice in rule-setting (Ostrom principle 3 absent)\n- Default response is \"regulate it\" or \"privatize it\" without considering institutional design\n\n## Verification\n\n- [ ] Shared resource and user boundaries specified\n- [ ] Commons structure verified (shared + rivalrous + diffuse responsibility)\n- [ ] Ostrom's 8 principles audited; weak/absent identified\n- [ ] Institutional intervention designed; privatize-or-regulate alternatives addressed\n- [ ] Monitoring metrics and review cycle scheduled\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 227 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/tragedy-of-the-commons** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\n*Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/tragedy-of-the-commons.json*\n\nFile v1.0.6:_meta.json\n\n{\n \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n \"slug\": \"tragedy-of-the-commons\",\n \"version\": \"1.0.6\",\n \"publishedAt\": 1784226000125\n}\n\nFile v1.0.6:references/sources.md\n\n# Sources — tragedy-of-the-commons\n\n> *Primary sources for the [tragedy-of-the-commons](../SKILL.md) skill.*\n\n- Hardin, G. (1968). \"The Tragedy of the Commons.\" *Science*, 162(3859), 1243-1248. The foundational paper.\n- Hardin, G. (1998). \"Extensions of 'The Tragedy of the Commons'.\" *Science*, 280(5364), 682-683. Hardin's update acknowledging Ostrom.\n- Ostrom, E. (1990). *Governing the Commons: The Evolution of Institutions for Collective Action.* Cambridge University Press. ISBN 978-0521405997. The empirical correction.\n- Ostrom, E. (2009). \"A General Framework for Analyzing Sustainability of Social-Ecological Systems.\" *Science*, 325(5939), 419-422. The synthesis.\n- Olson, M. (1965). *The Logic of Collective Action.* Harvard University Press. ISBN 978-0674537514. The collective-action problem foundation.\n- Lloyd, W. F. (1833). *Two Lectures on the Checks to Population.* Oxford University Press. The historical predecessor Hardin cites.\n- Dietz, T., Ostrom, E., & Stern, P. C. (2003). \"The struggle to govern the commons.\" *Science*, 302(5652), 1907-1912. The state-of-the-art summary.\n- Ostrom, E., Burger, J., Field, C. B., Norgaard, R. B., & Policansky, D. (1999). \"Revisiting the commons: Local lessons, global challenges.\" *Science*, 284(5412), 278-282.\n- Buck, S. J. (1998). *The Global Commons: An Introduction.* Island Press. ISBN 978-1559633499. Applied to modern global commons.\n- Kurlansky, M. (1997). *Cod: A Biography of the Fish That Changed the World.* Walker & Company. The Grand Banks collapse narrative.\n- Hutchings, J. A., & Myers, R. A. (1994). \"What can be learned from the collapse of a renewable resource? Atlantic cod, Gadus morhua, of Newfoundland and Labrador.\" *Canadian Journal of Fisheries and Aquatic Sciences*, 51(9), 2126-2146. The scientific post-mortem of the cod collapse.\n- International Energy Agency (2024). *Electricity 2024: Analysis and Forecast to 2026.* IEA, Paris. Widely-cited analysis of rising data-center and AI electricity demand — the 2024–2026 power commons.\n- Reuters / Associated Press reporting (2023–2025) on copyright litigation between publishers and authors and AI developers, on data-center grid strain and ratepayer cost allocation, and on advanced-GPU supply constraints and export controls. Context for the AI-era open-web, power, and GPU commons.\n\nFile v1.0.6:examples/ai-era-commons-open-web-power-gpus-2024-2026.md\n\n# Method in Action: The AI-Era Commons — Open Web, Power, and GPUs (2024–2026)\n\n> *Example for the [tragedy-of-the-commons](../SKILL.md) skill.*\n\nThe generative-AI build-out that accelerated through 2024–2025 (and continued into 2026) put three shared resources under simultaneous strain, each closely fitting Hardin's structure: the **open web** (published human content, scraped at scale to train models), **shared electrical grid and power capacity** (drawn on by rapidly growing data centers), and **frontier GPUs / accelerator supply** (a rivalrous input every AI lab competes for). In each, rational individual extraction degrades a resource whose cost of depletion is spread across everyone. This example walks all three through the skill's process, because they illustrate three different Ostrom-audit failure profiles.\n\n**Step 1 — Identify.**\n\n- *Open web.* Shared resource: the corpus of freely published human writing, images, and code. User community: AI labs and crawler operators (extractors) plus the publishers, forums, open-source maintainers, and individual creators who supply the content. Failure mode: the incentive to publish openly erodes as creators see their work absorbed into models that compete with or bypass them, so they paywall, add \"no-AI\" terms, or stop publishing — degrading the very commons the models depend on. Current rules: `robots.txt` (a voluntary, unenforceable convention from the 1990s), site terms of service, and a wave of crawler-blocking tools and licensing deals negotiated site-by-site.\n- *Power/grid.* Shared resource: finite electricity generation and transmission capacity on regional grids. User community: hyperscale data-center operators, other industrial users, and residential ratepayers. Failure mode: concentrated new demand strains interconnection queues and can push costs onto other users. Current rules: utility interconnection processes, tariffs, and grid-operator (e.g., ISO/RTO) planning.\n- *GPUs.* Shared resource: the constrained supply of advanced AI accelerators and the leading-edge fab capacity that makes them. User community: AI labs, cloud providers, enterprises, and researchers. Failure mode: supply concentrates with the largest buyers; smaller labs and academics are priced or crowded out. Current rules: vendor allocation, cloud reservation/quota systems, and export controls.\n\n**Step 2 — Verify commons structure.**\n\n- *Open web.* Shared access ✓ (anyone can crawl). Rivalrous — *partially*: the bytes are non-rival (copying costs nothing), but the **incentive to keep supplying new content is rivalrous and depletable**; unrestrained extraction erodes it. Diffuse responsibility ✓ (no crawler bears the cost of a shrinking open web). Hardin pattern ✓ (each lab rationally scrapes maximally; collectively they can starve future training data). Commons — with the nuance that the depletable stock is the *supply incentive*, not the copies.\n- *Power.* Shared ✓, rivalrous ✓ (a megawatt drawn is unavailable to others), diffuse responsibility ✓, Hardin pattern ✓. A clean commons.\n- *GPUs.* Shared ✓, rivalrous ✓ (a chip allocated to one buyer is unavailable to another), diffuse responsibility ✓, Hardin pattern ✓. A clean commons on a rivalrous private good under scarcity.\n\n**Step 3 — Ostrom audit.**\n\n*Open web:*\n- **1 Boundaries — absent/weak.** No enforceable line separates permitted from prohibited use; `robots.txt` is honored voluntarily and inconsistently.\n- **2 Congruence — absent.** Those who benefit from extraction (labs) are largely not those who bear the cost (creators); contribution and appropriation are decoupled.\n- **3 Collective-choice — weak.** Creators historically had no seat in the rules governing crawling; recourse emerged mostly through lawsuits and one-off licensing deals rather than shared rule-making.\n- **4 Monitoring — weak.** It is hard for a publisher to detect which crawler took what, though crawler-identification and analytics tools improved through 2024–2025.\n- **5 Graduated sanctions — weak.** Blocking a crawler or suing are blunt, high-cost instruments, not graduated ones.\n- **6 Conflict resolution — weak.** Disputes ran through courts (multiple copyright suits against AI developers filed 2023–2025) rather than a low-cost forum.\n- **7 Right to organize — emerging.** Publisher coalitions, licensing marketplaces, and proposed provenance/consent standards began forming.\n- **8 Nested enterprises — absent.** No layered governance from site to sector to international level.\n\n*Power:* Boundaries and nested enterprises are relatively strong (utilities, grid operators, regulators are layered). Congruence is the pressure point — the concern that data-center demand can shift costs onto other ratepayers. Monitoring and collective-choice run through existing regulatory proceedings, which are slow relative to the pace of demand growth.\n\n*GPUs:* Boundaries exist (allocation is contractual/private). Congruence and collective-choice are weak for smaller actors with no bargaining power; graduated mechanisms (fair-share quotas, reservation tiers, academic set-asides) are the natural design targets.\n\n**Step 4 — Intervene.** For each weak/absent principle, the skill points to institutional design rather than the \"privatize or regulate\" binary:\n\n- *Open web:* strengthen **boundaries and congruence** with machine-readable consent/provenance standards, licensing marketplaces that route value back to creators (restoring the supply incentive), and coalitions giving creators a collective-choice voice. Pure privatization (everything behind paywalls) would shrink the open web; pure regulation is slow and jurisdiction-bound. Ostrom's lens favors negotiated, layered consent regimes.\n- *Power:* strengthen **congruence** via tariff and interconnection design that assigns the cost of new capacity to the demand that causes it, plus co-located or dedicated generation so hyperscale load does not free-ride on shared capacity. This is classic congruence + nested-enterprise work through existing regulators.\n- *GPUs:* strengthen **collective-choice and graduated allocation** with reservation tiers, transparent fair-share quotas, and academic/public-interest set-asides (national research compute programs are a nested-enterprise response). Markets clear supply but concentrate it; deliberate set-asides preserve the research commons.\n\n**Step 5 — Monitor.** Track resource health per commons: for the open web, the share of high-value sites blocking or licensing crawlers and any decline in fresh open publication; for power, interconnection-queue times and the ratepayer cost-allocation split; for GPUs, access for non-frontier labs and academics. Review on a fast cycle — this commons is moving far faster than fisheries or grazing land.\n\nThe mapped steps:\n1. Identify: open web / grid power / GPU supply · extractor labs vs. supplier creators/ratepayers/small labs · eroding supply incentive, cost-shifting, crowd-out · voluntary conventions and private allocation\n2. Verify commons structure: power ✓✓✓✓ and GPUs ✓✓✓✓ clean; open web ✓ with the depletable stock being the *incentive to publish*, not the copies\n3. Ostrom audit: boundaries and congruence are the recurring gaps across all three\n4. Intervene: consent/licensing regimes (web), cost-causer tariffs and dedicated generation (power), fair-share quotas and research set-asides (GPUs) — layered governance over the privatize-or-regulate binary\n5. Monitor: fast-cycle metrics on supply health, cost allocation, and access\n\nThe operational lesson: the AI build-out did not create new economics — it re-ran Hardin at internet speed across three commons at once. The open-web case sharpens the skill's own boundary condition — a resource can be non-rival in its *copies* yet a genuine commons in its *renewal incentive*, which is exactly the depletable stock Ostrom's design principles exist to protect.\n\n*Sources: Hardin, G. (1968). \"The Tragedy of the Commons.\" Science, 162(3859), 1243–1248. Ostrom, E. (1990). Governing the Commons. Cambridge University Press. Reuters and Associated Press reporting (2023–2025) on copyright litigation between publishers/authors and AI developers, on data-center electricity demand and grid strain, and on advanced-GPU supply constraints and export controls. International Energy Agency, \"Electricity 2024: Analysis and Forecast to 2026\" and related IEA analyses (through 2025) on data-center and AI electricity demand.*\n\nFile v1.0.6:examples/grand-banks-cod-collapse-and-1992-moratorium.md\n\n# Method in Action: The Grand Banks Cod Collapse and the 1992 Moratorium (1950s–1992)\n\n> *Example for the [tragedy-of-the-commons](../SKILL.md) skill.*\n\nThe northern cod fishery off Newfoundland ran for roughly five centuries — European fleets worked the Grand Banks from the late 1400s onward — and then collapsed within a few decades of industrialization. It is the canonical natural-resource commons tragedy, and it also demonstrates the skill's sharpest lesson: central regulation without Ostrom's institutional structure fails just like an unmanaged commons.\n\n**Step 1 — Identify.** Shared resource: the northern cod stock (Gadus morhua) off Newfoundland and Labrador. User community: Newfoundland inshore fishers (small boats, local knowledge), Canadian offshore trawler companies, and foreign distant-water factory fleets. Failure mode: stock collapse. Current rules (pre-collapse): open international access beyond territorial waters; after Canada's 200-mile exclusive economic zone declaration in 1977, centralized quotas set by the federal Department of Fisheries and Oceans (DFO).\n\n**Step 2 — Verify commons structure.** Shared access: yes — no single actor could exclude others. Rivalrous: yes — every tonne caught is unavailable to everyone else and to the spawning stock. Diffuse responsibility: yes — no fleet bore the cost of its own overfishing; the cost was spread across all users and the future. Hardin pattern: yes — each captain's rational move was to catch more before competitors did. Post-WWII factory trawlers from Europe and the USSR drove reported catches to a historic peak around 800,000 tonnes in 1968, several times the long-run sustainable harvest. All four conditions present: a textbook commons.\n\n**Step 3 — Ostrom audit.** This is the instructive part — Canada *did* regulate after 1977, and the stock still collapsed, because nearly every design principle was weak or absent:\n\n- **1 Boundaries — weak.** The 200-mile zone came only in 1977; foreign fleets kept fishing the \"Nose\" and \"Tail\" of the Banks that lay outside it.\n- **2 Congruence — absent.** DFO quotas rested on offshore survey models that overestimated the stock; harvest rules did not match the resource's actual condition.\n- **3 Collective-choice — absent.** Inshore fishers reported shrinking fish and falling catches through the 1980s; their local knowledge had no channel into quota-setting, and the warnings were dismissed as anecdote.\n- **4 Monitoring — weak.** Discarding, misreporting, and high-grading at sea were widespread and largely unobserved.\n- **5 Graduated sanctions — weak.** Quota violations carried little consequence relative to the profit from cheating.\n- **6 Conflict resolution — absent.** The inshore–offshore dispute over who was destroying the stock festered for a decade with no legitimate forum.\n- **7 Right to organize — absent.** Fishing communities had no recognized authority to set or enforce local rules.\n- **8 Nested enterprises — absent.** A single centralized regulator managed a resource spanning local, national, and international scales.\n\n**Step 4 — Intervene (what actually happened).** The intervention came only after the resource was gone. On July 2, 1992, Canada's fisheries minister declared a moratorium on the northern cod fishery. The spawning stock had fallen to a small fraction of its historical level; roughly 30,000 fishers and plant workers lost their livelihoods — often described as the largest single industrial layoff in Canadian history. The moratorium was announced as a two-year pause; the stock did not meaningfully recover for decades.\n\n**Step 5 — Monitor.** The post-mortem literature (Hutchings & Myers 1994) concluded the collapse was driven by overfishing, not environment alone — the monitoring system had measured the wrong things and ignored the users closest to the resource.\n\nThe mapped steps:\n1. Identify: northern cod stock · inshore/offshore/foreign fleets · stock collapse · open access, then centralized quotas\n2. Verify commons structure: shared ✓ rivalrous ✓ diffuse responsibility ✓ Hardin pattern ✓\n3. Ostrom audit: principles 2, 3, 6, 7, 8 absent; 1, 4, 5 weak — regulation without institutional design\n4. Intervene: 1992 moratorium — imposed after collapse instead of designed before it\n5. Monitor: scientific post-mortem confirmed overfishing under a monitoring regime that excluded local knowledge\n\nThe operational lesson inverts the \"just regulate it\" reflex: Canada had a regulator, quotas, and science, yet reproduced the unmanaged-commons outcome because congruence, collective-choice, and nested governance were missing. Contrast with Ostrom's enduring fisheries commons, where users who monitor each other and set their own rules sustained harvests for centuries.\n\nPrimary sources: Kurlansky, M. (1997). *Cod: A Biography of the Fish That Changed the World.* Walker & Company. Hutchings, J. A., & Myers, R. A. (1994). \"What can be learned from the collapse of a renewable resource? Atlantic cod, Gadus morhua, of Newfoundland and Labrador.\" *Canadian Journal of Fisheries and Aquatic Sciences*, 51(9), 2126-2146.\n\nFile v1.0.6:examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md\n\n# Method in Action: Hardin 1968 + Ostrom's Empirical Correction + Modern Digital Applications\n\n> *Example for the [tragedy-of-the-commons](../SKILL.md) skill.*\n\nThe Hardin 1968 paper was operationally famous and operationally influential, but its conclusions were over-stated and partially wrong. Hardin himself acknowledged this in a 1998 follow-up paper:\n\n> Hardin, G. (1998). \"Extensions of 'The Tragedy of the Commons'.\" *Science*, 280(5364), 682-683.\n\nHardin's 1998 update acknowledged Ostrom's empirical findings and clarified that his 1968 paper had over-generalized: his analysis applied to *unmanaged* commons, not to commons with established governance institutions. The 1998 paper explicitly cited Ostrom and recommended her institutional approach for managed commons.\n\n**Elinor Ostrom's 1990** book *Governing the Commons* documented hundreds of cases of long-enduring commons institutions:\n\n- **Swiss alpine pastures.** Communities like Törbel, Switzerland have managed summer pastures cooperatively for 500+ years, with no degradation. The institutional structure exhibits all 8 of Ostrom's principles: clearly defined boundaries (only Törbel residents can use the pasture), congruence (one cow per resident in summer), collective-choice (annual village assembly sets rules), monitoring (residents see each other's herds daily), graduated sanctions (first violation = warning, repeated = fine, persistent = exclusion), conflict resolution (village courts), recognition by Swiss government, nested governance.\n\n- **Japanese coastal fisheries.** Village fisheries communities in Hokkaido have maintained common-property rights over coastal waters for centuries, with sustainable harvests. The institutional features mirror the Swiss case adjusted for fisheries.\n\n- **Spanish irrigation systems (huertas of Valencia).** Communities have shared water in Mediterranean basins for 1000+ years through \"tribunals of waters\" — weekly meetings at the cathedral door where farmers resolve disputes. The system has worked since at least the Moorish period.\n\n- **Philippine forest user groups.** Ostrom documented village-level forest management that sustained forest cover where state-managed forests collapsed.\n\nOstrom's empirical claim: when the 8 design principles are present, commons institutions endure for centuries; when they're absent, the Hardin tragedy unfolds.\n\nThe framework has been applied at industrial scale in modern digital and technical commons:\n\n**Open-source software governance.** The Linux kernel, the Apache foundation, the Cloud Native Computing Foundation, Wikipedia — all are commons that have applied Ostrom-style design (governance councils, contribution rules, code-of-conduct enforcement, conflict resolution). The successful projects exhibit Ostrom's principles; the failed ones typically miss several.\n\n**API rate limiting and quota systems.** Modern cloud providers (AWS, Google Cloud, OpenAI, Anthropic) use Ostrom-style commons design for shared infrastructure: clearly defined tiers (boundaries), congruent quotas (rules match capacity), monitoring (usage dashboards), graduated sanctions (throttling → suspension → ban), appeals processes (conflict resolution).\n\n**Wikipedia governance.** Wikipedia's editorial commons has remained productive for 20+ years despite being entirely volunteer-driven. The institutional structure (administrators, arbitration committee, RFC process, edit-warring sanctions) exhibits most of Ostrom's 8 principles.\n\n**Workplace shared resources.** Modern guidance on meeting hygiene, Slack norms, email discipline, \"Maker vs Manager schedules\" (Paul Graham 2009) is implicitly Ostrom-style: defining boundaries (meeting-free time blocks), congruence (meeting calls match actual coordination needs), monitoring (calendar audits), graduated sanctions (cultural pushback against bad-meeting-callers).\n\n**Cybersecurity (shared internet infrastructure).** The DNS root server system, BGP routing, IP address allocation, certificate authorities — all are commons. The institutional governance (ICANN, IETF, regional internet registries) is broadly Ostrom-structured.\n\n**AI training data commons.** The current AI training-data commons crisis (publishers walling off content; content quality degrading as AI-generated text floods the web) is unfolding in real time as a textbook Hardin tragedy. The Ostrom-style response — institutional design for shared training data, with contribution rules and compensation mechanisms — is being debated at the policy level.\n\nThree operational lessons:\n\n**First, modern technical commons are everywhere.** Anywhere a platform, API, ecosystem, or shared infrastructure has multiple users with individual access, you have a commons. The Hardin dynamics will operate unless Ostrom-style institutional design is applied.\n\n**Second, the privatize-or-regulate binary is usually wrong.** Hardin's 1968 conclusion — privatize or have government regulation — was over-simplified. Ostrom's empirical contribution: institutional design at the user community level is often more effective than either privatization or central regulation. Modern platforms designing API quotas, governance councils, and contribution rules are applying Ostrom's framework whether they know it or not.\n\n**Third, the 8 principles are not optional add-ons; they're load-bearing.** Communities that miss several of Ostrom's 8 principles reliably collapse into Hardin tragedy. The principles are not a checklist of nice-to-haves; they are the structural mechanisms that make collective self-governance work.\n\nFile v1.0.6:skill-card.md\n\n## Description:\n\nA reasoning-framework skill that helps agents diagnose shared-resource degradation, audit commons-governance gaps, and propose institutional-design interventions.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[deciqai](https://clawhub.ai/user/deciqai)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nEmployees, external users, developers, and policy or platform teams use this skill to analyze degrading shared resources such as open-source projects, APIs, infrastructure, workplace attention, fisheries, or AI-era resource constraints. It guides agents through fit checking, commons-structure verification, an Ostrom eight-principle audit, intervention design, and monitoring.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill may steer analysis toward a commons-governance model when the situation does not involve a real shared, rivalrous resource.\n\nMitigation: Verify shared access, rivalrous use, diffuse responsibility, and a Hardin-style individually rational but collectively destructive pattern before relying on the framing.\n\n## Reference(s):\n\n- [ClawHub release page](https://clawhub.ai/deciqai/skills/tragedy-of-the-commons)\n- [Primary sources](artifact/references/sources.md)\n- [Hardin and Ostrom empirical correction example](artifact/examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md)\n- [Grand Banks cod collapse example](artifact/examples/grand-banks-cod-collapse-and-1992-moratorium.md)\n- [AI-era commons example](artifact/examples/ai-era-commons-open-web-power-gpus-2024-2026.md)\n- [deciqAI machine-readable metadata](https://www.deciqai.com/s/tragedy-of-the-commons.json)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Guidance]\n\n**Output Format:** [Markdown structured as a Commons Design analysis template]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May ask stepwise coaching questions and stop at explicit wait points when the user is unfamiliar with the framework.]\n\n## Skill Version(s):\n\n1.0.6 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.5: 7 files, 16423 bytes\n\nFiles: examples/ai-era-commons-open-web-power-gpus-2024-2026.md (8547b), examples/grand-banks-cod-collapse-and-1992-moratorium.md (5171b), examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md (5592b), references/sources.md (2333b), skill-card.md (2693b), SKILL.md (8087b), _meta.json (141b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: tragedy-of-the-commons\ndescription: >\n Activate when: shared resource is degrading even though no one is doing anything \"wrong\"; team complains about free riders or overuse; designing API quotas, rate limits, or open-source governance; someone says \"everyone is overusing this\" or \"the system worked fine until it got popular\"; evaluating why a platform or community is burning out.\n Do NOT activate when: the resource is fully non-rival (unlimited supply, zero marginal cost); the problem is a purely individual-action issue with no shared resource.\n---\n\n# Tragedy of the Commons\n\n## Overview\n\nWhen a shared resource has individual access but no individual responsibility for preservation, rational users extract private benefit while the cost of overuse is shared — leading to collective degradation. Garrett Hardin named this in 1968; Elinor Ostrom corrected it in 1990 (Nobel 2009): many communities self-govern commons via her 8 design principles without privatization or coercion.\n\nComposes with `prisoners-dilemma`, `principal-agent`, `network-effects`, `goodharts-law`, `repeated-games-reputation`.\n\n## When to Use\n\n- Diagnosing why a shared resource is degrading (open-source burnout, API abuse, attention market polarizing)\n- Assessing AI-era shared-resource strain from AI capex and AI-native competition (open web scraped for training data, grid/power capacity, GPU allocation)\n- Designing platforms, marketplaces, shared infrastructure, API quotas, or rate limits\n- Designing workplace norms around shared resources (meetings, Slack, email)\n- Evaluating regulatory or policy responses to shared-resource problems\n\n**Not when:** resource is genuinely non-rival; fully private; \"commons\" framing is misapplied to individual-action problems.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete commons case → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line: when a shared resource degrades despite each user acting rationally, you have a commons problem — the answer is institutional design per Ostrom's 8 principles, not just \"privatize\" or \"regulate.\"\n2. Check fit: shared resource + individual extraction + shared cost? If not, different frameworks apply.\n3. Elicit the resource, users, and current rules: What's shared? Who has access? What rules govern use? What's failing?\n> **[WAIT — do not advance until user responds]**\n4. Audit which of Ostrom's 8 principles are present / weak / absent in their situation.\n> **[WAIT — do not advance until user responds]**\n5. Close: name the institutional gaps + propose design applying missing principles + monitoring plan.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Identify:** shared resource · user community · failure mode · current rules.\n**Step 2 — Verify commons structure:** shared access + rivalrous + diffuse responsibility + Hardin pattern (individually rational, collectively destructive). All four yes → commons.\n**Step 3 — Ostrom audit** (mark present / weak / absent): 1 Boundaries · 2 Congruence · 3 Collective-choice · 4 Monitoring · 5 Graduated sanctions · 6 Conflict resolution · 7 Right to organize · 8 Nested enterprises. Weak/absent = design targets.\n**Step 4 — Intervene:** for each weak/absent principle, design a specific fix. Avoid the \"privatize or regulate\" binary — Ostrom's institutional design often outperforms both.\n**Step 5 — Monitor:** sequence · metrics (resource health, sanctions issued) · quarterly review.\n\n## Output Template\n```\nCommons Design: \nStructure: shared resource | boundaries | failure mode | current rules\nVerification: shared Y/N · rivalrous Y/N · diffuse responsibility Y/N · Hardin pattern Y/N\nOstrom audit: [1–8: present/weak/absent]\nIntervention: [per weak/absent principle] · why not privatize · why not pure regulation\nImplementation: sequence · metrics · review cycle\n```\n\n*→ Method in Action: [Hardin 1968 + Ostrom's Empirical Correction + Modern Digital Applications](examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md) · [Grand Banks Cod Collapse](examples/grand-banks-cod-collapse-and-1992-moratorium.md)*\n*→ 2026 lens: [The AI-Era Commons — Open Web, Power, and GPUs (2024–2026)](examples/ai-era-commons-open-web-power-gpus-2024-2026.md)*\n\n## Pack: Commons Patterns\n\n| Commons | Failure mode | Ostrom countermeasure |\n|---|---|---|\n| Open-source project | Maintainer burnout | Contribution rules; governance council; sustaining funding |\n| API / cloud infrastructure | Abuse degrades service for all | Tiered quotas; monitoring; graduated sanctions |\n| Slack / meetings | Notification overload | Norms; meeting-free blocks; signal-noise metrics |\n| Fisheries / antibiotic efficacy | Stock collapse / resistance | Quotas; stewardship programs; surveillance |\n| Atmospheric carbon | Climate change | Carbon pricing; international agreements; local action |\n\n## Applying It Well\n\n- Ostrom's 8 principles are load-bearing, not optional: missing several reliably produces Hardin tragedy.\n- Privatization works when exclusion is feasible and transaction costs are low. Regulation works when the regulator has information and legitimacy. Ostrom's self-governance works when users can communicate, monitor, and self-organize — often best for technical commons.\n- Peer monitoring (users see each other's behavior) differs from punitive surveillance; successful commons use the former.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"Commons always fail; we have to privatize\" | Hardin over-stated this. Ostrom's empirical evidence: many commons endure for centuries with the 8 principles. |\n| [D] \"The government must regulate\" | Sometimes. Often community self-governance is faster, cheaper, and more legitimate. |\n| [D] \"Punish free riders; that's enough\" | Graduated sanctions is one of 8 principles. Punishment alone without monitoring, boundaries, etc. doesn't work. |\n| [D] \"Open source means free; we don't owe anything\" | Maintainer labor is a commons; without contribution mechanisms it depletes (xz 2024 was the warning). |\n| [D] \"Our users would never abuse the API\" | The Hardin structure predicts abuse from a substantial fraction regardless of intent. Design accordingly. |\n| [D] \"We don't need formal governance; people are reasonable\" | Even reasonable people benefit from boundaries, monitoring, and conflict resolution. |\n| [D] \"Monitoring is surveillance; we don't do that\" | Ostrom distinguishes cooperative peer-monitoring from punitive surveillance. Successful commons use the former. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Shared resource degrading; rules unclear or unenforced\n- Free-rider complaints but no graduated sanctions exist\n- Users have no voice in rule-setting (Ostrom principle 3 absent)\n- Default response is \"regulate it\" or \"privatize it\" without considering institutional design\n\n## Verification\n\n- [ ] Shared resource and user boundaries specified\n- [ ] Commons structure verified (shared + rivalrous + diffuse responsibility)\n- [ ] Ostrom's 8 principles audited; weak/absent identified\n- [ ] Institutional intervention designed; privatize-or-regulate alternatives addressed\n- [ ] Monitoring metrics and review cycle scheduled\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 189 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/tragedy-of-the-commons** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.5:_meta.json\n\n{\n \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n \"slug\": \"tragedy-of-the-commons\",\n \"version\": \"1.0.5\",\n \"publishedAt\": 1783596153862\n}\n\nFile v1.0.5:references/sources.md\n\n# Sources — tragedy-of-the-commons\n\n> *Primary sources for the [tragedy-of-the-commons](../SKILL.md) skill.*\n\n- Hardin, G. (1968). \"The Tragedy of the Commons.\" *Science*, 162(3859), 1243-1248. The foundational paper.\n- Hardin, G. (1998). \"Extensions of 'The Tragedy of the Commons'.\" *Science*, 280(5364), 682-683. Hardin's update acknowledging Ostrom.\n- Ostrom, E. (1990). *Governing the Commons: The Evolution of Institutions for Collective Action.* Cambridge University Press. ISBN 978-0521405997. The empirical correction.\n- Ostrom, E. (2009). \"A General Framework for Analyzing Sustainability of Social-Ecological Systems.\" *Science*, 325(5939), 419-422. The synthesis.\n- Olson, M. (1965). *The Logic of Collective Action.* Harvard University Press. ISBN 978-0674537514. The collective-action problem foundation.\n- Lloyd, W. F. (1833). *Two Lectures on the Checks to Population.* Oxford University Press. The historical predecessor Hardin cites.\n- Dietz, T., Ostrom, E., & Stern, P. C. (2003). \"The struggle to govern the commons.\" *Science*, 302(5652), 1907-1912. The state-of-the-art summary.\n- Ostrom, E., Burger, J., Field, C. B., Norgaard, R. B., & Policansky, D. (1999). \"Revisiting the commons: Local lessons, global challenges.\" *Science*, 284(5412), 278-282.\n- Buck, S. J. (1998). *The Global Commons: An Introduction.* Island Press. ISBN 978-1559633499. Applied to modern global commons.\n- Kurlansky, M. (1997). *Cod: A Biography of the Fish That Changed the World.* Walker & Company. The Grand Banks collapse narrative.\n- Hutchings, J. A., & Myers, R. A. (1994). \"What can be learned from the collapse of a renewable resource? Atlantic cod, Gadus morhua, of Newfoundland and Labrador.\" *Canadian Journal of Fisheries and Aquatic Sciences*, 51(9), 2126-2146. The scientific post-mortem of the cod collapse.\n- International Energy Agency (2024). *Electricity 2024: Analysis and Forecast to 2026.* IEA, Paris. Widely-cited analysis of rising data-center and AI electricity demand — the 2024–2026 power commons.\n- Reuters / Associated Press reporting (2023–2025) on copyright litigation between publishers and authors and AI developers, on data-center grid strain and ratepayer cost allocation, and on advanced-GPU supply constraints and export controls. Context for the AI-era open-web, power, and GPU commons.\n\nFile v1.0.5:examples/ai-era-commons-open-web-power-gpus-2024-2026.md\n\n# Method in Action: The AI-Era Commons — Open Web, Power, and GPUs (2024–2026)\n\n> *Example for the [tragedy-of-the-commons](../SKILL.md) skill.*\n\nThe generative-AI build-out that accelerated through 2024–2025 (and continued into 2026) put three shared resources under simultaneous strain, each closely fitting Hardin's structure: the **open web** (published human content, scraped at scale to train models), **shared electrical grid and power capacity** (drawn on by rapidly growing data centers), and **frontier GPUs / accelerator supply** (a rivalrous input every AI lab competes for). In each, rational individual extraction degrades a resource whose cost of depletion is spread across everyone. This example walks all three through the skill's process, because they illustrate three different Ostrom-audit failure profiles.\n\n**Step 1 — Identify.**\n\n- *Open web.* Shared resource: the corpus of freely published human writing, images, and code. User community: AI labs and crawler operators (extractors) plus the publishers, forums, open-source maintainers, and individual creators who supply the content. Failure mode: the incentive to publish openly erodes as creators see their work absorbed into models that compete with or bypass them, so they paywall, add \"no-AI\" terms, or stop publishing — degrading the very commons the models depend on. Current rules: `robots.txt` (a voluntary, unenforceable convention from the 1990s), site terms of service, and a wave of crawler-blocking tools and licensing deals negotiated site-by-site.\n- *Power/grid.* Shared resource: finite electricity generation and transmission capacity on regional grids. User community: hyperscale data-center operators, other industrial users, and residential ratepayers. Failure mode: concentrated new demand strains interconnection queues and can push costs onto other users. Current rules: utility interconnection processes, tariffs, and grid-operator (e.g., ISO/RTO) planning.\n- *GPUs.* Shared resource: the constrained supply of advanced AI accelerators and the leading-edge fab capacity that makes them. User community: AI labs, cloud providers, enterprises, and researchers. Failure mode: supply concentrates with the largest buyers; smaller labs and academics are priced or crowded out. Current rules: vendor allocation, cloud reservation/quota systems, and export controls.\n\n**Step 2 — Verify commons structure.**\n\n- *Open web.* Shared access ✓ (anyone can crawl). Rivalrous — *partially*: the bytes are non-rival (copying costs nothing), but the **incentive to keep supplying new content is rivalrous and depletable**; unrestrained extraction erodes it. Diffuse responsibility ✓ (no crawler bears the cost of a shrinking open web). Hardin pattern ✓ (each lab rationally scrapes maximally; collectively they can starve future training data). Commons — with the nuance that the depletable stock is the *supply incentive*, not the copies.\n- *Power.* Shared ✓, rivalrous ✓ (a megawatt drawn is unavailable to others), diffuse responsibility ✓, Hardin pattern ✓. A clean commons.\n- *GPUs.* Shared ✓, rivalrous ✓ (a chip allocated to one buyer is unavailable to another), diffuse responsibility ✓, Hardin pattern ✓. A clean commons on a rivalrous private good under scarcity.\n\n**Step 3 — Ostrom audit.**\n\n*Open web:*\n- **1 Boundaries — absent/weak.** No enforceable line separates permitted from prohibited use; `robots.txt` is honored voluntarily and inconsistently.\n- **2 Congruence — absent.** Those who benefit from extraction (labs) are largely not those who bear the cost (creators); contribution and appropriation are decoupled.\n- **3 Collective-choice — weak.** Creators historically had no seat in the rules governing crawling; recourse emerged mostly through lawsuits and one-off licensing deals rather than shared rule-making.\n- **4 Monitoring — weak.** It is hard for a publisher to detect which crawler took what, though crawler-identification and analytics tools improved through 2024–2025.\n- **5 Graduated sanctions — weak.** Blocking a crawler or suing are blunt, high-cost instruments, not graduated ones.\n- **6 Conflict resolution — weak.** Disputes ran through courts (multiple copyright suits against AI developers filed 2023–2025) rather than a low-cost forum.\n- **7 Right to organize — emerging.** Publisher coalitions, licensing marketplaces, and proposed provenance/consent standards began forming.\n- **8 Nested enterprises — absent.** No layered governance from site to sector to international level.\n\n*Power:* Boundaries and nested enterprises are relatively strong (utilities, grid operators, regulators are layered). Congruence is the pressure point — the concern that data-center demand can shift costs onto other ratepayers. Monitoring and collective-choice run through existing regulatory proceedings, which are slow relative to the pace of demand growth.\n\n*GPUs:* Boundaries exist (allocation is contractual/private). Congruence and collective-choice are weak for smaller actors with no bargaining power; graduated mechanisms (fair-share quotas, reservation tiers, academic set-asides) are the natural design targets.\n\n**Step 4 — Intervene.** For each weak/absent principle, the skill points to institutional design rather than the \"privatize or regulate\" binary:\n\n- *Open web:* strengthen **boundaries and congruence** with machine-readable consent/provenance standards, licensing marketplaces that route value back to creators (restoring the supply incentive), and coalitions giving creators a collective-choice voice. Pure privatization (everything behind paywalls) would shrink the open web; pure regulation is slow and jurisdiction-bound. Ostrom's lens favors negotiated, layered consent regimes.\n- *Power:* strengthen **congruence** via tariff and interconnection design that assigns the cost of new capacity to the demand that causes it, plus co-located or dedicated generation so hyperscale load does not free-ride on shared capacity. This is classic congruence + nested-enterprise work through existing regulators.\n- *GPUs:* strengthen **collective-choice and graduated allocation** with reservation tiers, transparent fair-share quotas, and academic/public-interest set-asides (national research compute programs are a nested-enterprise response). Markets clear supply but concentrate it; deliberate set-asides preserve the research commons.\n\n**Step 5 — Monitor.** Track resource health per commons: for the open web, the share of high-value sites blocking or licensing crawlers and any decline in fresh open publication; for power, interconnection-queue times and the ratepayer cost-allocation split; for GPUs, access for non-frontier labs and academics. Review on a fast cycle — this commons is moving far faster than fisheries or grazing land.\n\nThe mapped steps:\n1. Identify: open web / grid power / GPU supply · extractor labs vs. supplier creators/ratepayers/small labs · eroding supply incentive, cost-shifting, crowd-out · voluntary conventions and private allocation\n2. Verify commons structure: power ✓✓✓✓ and GPUs ✓✓✓✓ clean; open web ✓ with the depletable stock being the *incentive to publish*, not the copies\n3. Ostrom audit: boundaries and congruence are the recurring gaps across all three\n4. Intervene: consent/licensing regimes (web), cost-causer tariffs and dedicated generation (power), fair-share quotas and research set-asides (GPUs) — layered governance over the privatize-or-regulate binary\n5. Monitor: fast-cycle metrics on supply health, cost allocation, and access\n\nThe operational lesson: the AI build-out did not create new economics — it re-ran Hardin at internet speed across three commons at once. The open-web case sharpens the skill's own boundary condition — a resource can be non-rival in its *copies* yet a genuine commons in its *renewal incentive*, which is exactly the depletable stock Ostrom's design principles exist to protect.\n\n*Sources: Hardin, G. (1968). \"The Tragedy of the Commons.\" Science, 162(3859), 1243–1248. Ostrom, E. (1990). Governing the Commons. Cambridge University Press. Reuters and Associated Press reporting (2023–2025) on copyright litigation between publishers/authors and AI developers, on data-center electricity demand and grid strain, and on advanced-GPU supply constraints and export controls. International Energy Agency, \"Electricity 2024: Analysis and Forecast to 2026\" and related IEA analyses (through 2025) on data-center and AI electricity demand.*\n\nFile v1.0.5:examples/grand-banks-cod-collapse-and-1992-moratorium.md\n\n# Method in Action: The Grand Banks Cod Collapse and the 1992 Moratorium (1950s–1992)\n\n> *Example for the [tragedy-of-the-commons](../SKILL.md) skill.*\n\nThe northern cod fishery off Newfoundland ran for roughly five centuries — European fleets worked the Grand Banks from the late 1400s onward — and then collapsed within a few decades of industrialization. It is the canonical natural-resource commons tragedy, and it also demonstrates the skill's sharpest lesson: central regulation without Ostrom's institutional structure fails just like an unmanaged commons.\n\n**Step 1 — Identify.** Shared resource: the northern cod stock (Gadus morhua) off Newfoundland and Labrador. User community: Newfoundland inshore fishers (small boats, local knowledge), Canadian offshore trawler companies, and foreign distant-water factory fleets. Failure mode: stock collapse. Current rules (pre-collapse): open international access beyond territorial waters; after Canada's 200-mile exclusive economic zone declaration in 1977, centralized quotas set by the federal Department of Fisheries and Oceans (DFO).\n\n**Step 2 — Verify commons structure.** Shared access: yes — no single actor could exclude others. Rivalrous: yes — every tonne caught is unavailable to everyone else and to the spawning stock. Diffuse responsibility: yes — no fleet bore the cost of its own overfishing; the cost was spread across all users and the future. Hardin pattern: yes — each captain's rational move was to catch more before competitors did. Post-WWII factory trawlers from Europe and the USSR drove reported catches to a historic peak around 800,000 tonnes in 1968, several times the long-run sustainable harvest. All four conditions present: a textbook commons.\n\n**Step 3 — Ostrom audit.** This is the instructive part — Canada *did* regulate after 1977, and the stock still collapsed, because nearly every design principle was weak or absent:\n\n- **1 Boundaries — weak.** The 200-mile zone came only in 1977; foreign fleets kept fishing the \"Nose\" and \"Tail\" of the Banks that lay outside it.\n- **2 Congruence — absent.** DFO quotas rested on offshore survey models that overestimated the stock; harvest rules did not match the resource's actual condition.\n- **3 Collective-choice — absent.** Inshore fishers reported shrinking fish and falling catches through the 1980s; their local knowledge had no channel into quota-setting, and the warnings were dismissed as anecdote.\n- **4 Monitoring — weak.** Discarding, misreporting, and high-grading at sea were widespread and largely unobserved.\n- **5 Graduated sanctions — weak.** Quota violations carried little consequence relative to the profit from cheating.\n- **6 Conflict resolution — absent.** The inshore–offshore dispute over who was destroying the stock festered for a decade with no legitimate forum.\n- **7 Right to organize — absent.** Fishing communities had no recognized authority to set or enforce local rules.\n- **8 Nested enterprises — absent.** A single centralized regulator managed a resource spanning local, national, and international scales.\n\n**Step 4 — Intervene (what actually happened).** The intervention came only after the resource was gone. On July 2, 1992, Canada's fisheries minister declared a moratorium on the northern cod fishery. The spawning stock had fallen to a small fraction of its historical level; roughly 30,000 fishers and plant workers lost their livelihoods — often described as the largest single industrial layoff in Canadian history. The moratorium was announced as a two-year pause; the stock did not meaningfully recover for decades.\n\n**Step 5 — Monitor.** The post-mortem literature (Hutchings & Myers 1994) concluded the collapse was driven by overfishing, not environment alone — the monitoring system had measured the wrong things and ignored the users closest to the resource.\n\nThe mapped steps:\n1. Identify: northern cod stock · inshore/offshore/foreign fleets · stock collapse · open access, then centralized quotas\n2. Verify commons structure: shared ✓ rivalrous ✓ diffuse responsibility ✓ Hardin pattern ✓\n3. Ostrom audit: principles 2, 3, 6, 7, 8 absent; 1, 4, 5 weak — regulation without institutional design\n4. Intervene: 1992 moratorium — imposed after collapse instead of designed before it\n5. Monitor: scientific post-mortem confirmed overfishing under a monitoring regime that excluded local knowledge\n\nThe operational lesson inverts the \"just regulate it\" reflex: Canada had a regulator, quotas, and science, yet reproduced the unmanaged-commons outcome because congruence, collective-choice, and nested governance were missing. Contrast with Ostrom's enduring fisheries commons, where users who monitor each other and set their own rules sustained harvests for centuries.\n\nPrimary sources: Kurlansky, M. (1997). *Cod: A Biography of the Fish That Changed the World.* Walker & Company. Hutchings, J. A., & Myers, R. A. (1994). \"What can be learned from the collapse of a renewable resource? Atlantic cod, Gadus morhua, of Newfoundland and Labrador.\" *Canadian Journal of Fisheries and Aquatic Sciences*, 51(9), 2126-2146.\n\nFile v1.0.5:examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md\n\n# Method in Action: Hardin 1968 + Ostrom's Empirical Correction + Modern Digital Applications\n\n> *Example for the [tragedy-of-the-commons](../SKILL.md) skill.*\n\nThe Hardin 1968 paper was operationally famous and operationally influential, but its conclusions were over-stated and partially wrong. Hardin himself acknowledged this in a 1998 follow-up paper:\n\n> Hardin, G. (1998). \"Extensions of 'The Tragedy of the Commons'.\" *Science*, 280(5364), 682-683.\n\nHardin's 1998 update acknowledged Ostrom's empirical findings and clarified that his 1968 paper had over-generalized: his analysis applied to *unmanaged* commons, not to commons with established governance institutions. The 1998 paper explicitly cited Ostrom and recommended her institutional approach for managed commons.\n\n**Elinor Ostrom's 1990** book *Governing the Commons* documented hundreds of cases of long-enduring commons institutions:\n\n- **Swiss alpine pastures.** Communities like Törbel, Switzerland have managed summer pastures cooperatively for 500+ years, with no degradation. The institutional structure exhibits all 8 of Ostrom's principles: clearly defined boundaries (only Törbel residents can use the pasture), congruence (one cow per resident in summer), collective-choice (annual village assembly sets rules), monitoring (residents see each other's herds daily), graduated sanctions (first violation = warning, repeated = fine, persistent = exclusion), conflict resolution (village courts), recognition by Swiss government, nested governance.\n\n- **Japanese coastal fisheries.** Village fisheries communities in Hokkaido have maintained common-property rights over coastal waters for centuries, with sustainable harvests. The institutional features mirror the Swiss case adjusted for fisheries.\n\n- **Spanish irrigation systems (huertas of Valencia).** Communities have shared water in Mediterranean basins for 1000+ years through \"tribunals of waters\" — weekly meetings at the cathedral door where farmers resolve disputes. The system has worked since at least the Moorish period.\n\n- **Philippine forest user groups.** Ostrom documented village-level forest management that sustained forest cover where state-managed forests collapsed.\n\nOstrom's empirical claim: when the 8 design principles are present, commons institutions endure for centuries; when they're absent, the Hardin tragedy unfolds.\n\nThe framework has been applied at industrial scale in modern digital and technical commons:\n\n**Open-source software governance.** The Linux kernel, the Apache foundation, the Cloud Native Computing Foundation, Wikipedia — all are commons that have applied Ostrom-style design (governance councils, contribution rules, code-of-conduct enforcement, conflict resolution). The successful projects exhibit Ostrom's principles; the failed ones typically miss several.\n\n**API rate limiting and quota systems.** Modern cloud providers (AWS, Google Cloud, OpenAI, Anthropic) use Ostrom-style commons design for shared infrastructure: clearly defined tiers (boundaries), congruent quotas (rules match capacity), monitoring (usage dashboards), graduated sanctions (throttling → suspension → ban), appeals processes (conflict resolution).\n\n**Wikipedia governance.** Wikipedia's editorial commons has remained productive for 20+ years despite being entirely volunteer-driven. The institutional structure (administrators, arbitration committee, RFC process, edit-warring sanctions) exhibits most of Ostrom's 8 principles.\n\n**Workplace shared resources.** Modern guidance on meeting hygiene, Slack norms, email discipline, \"Maker vs Manager schedules\" (Paul Graham 2009) is implicitly Ostrom-style: defining boundaries (meeting-free time blocks), congruence (meeting calls match actual coordination needs), monitoring (calendar audits), graduated sanctions (cultural pushback against bad-meeting-callers).\n\n**Cybersecurity (shared internet infrastructure).** The DNS root server system, BGP routing, IP address allocation, certificate authorities — all are commons. The institutional governance (ICANN, IETF, regional internet registries) is broadly Ostrom-structured.\n\n**AI training data commons.** The current AI training-data commons crisis (publishers walling off content; content quality degrading as AI-generated text floods the web) is unfolding in real time as a textbook Hardin tragedy. The Ostrom-style response — institutional design for shared training data, with contribution rules and compensation mechanisms — is being debated at the policy level.\n\nThree operational lessons:\n\n**First, modern technical commons are everywhere.** Anywhere a platform, API, ecosystem, or shared infrastructure has multiple users with individual access, you have a commons. The Hardin dynamics will operate unless Ostrom-style institutional design is applied.\n\n**Second, the privatize-or-regulate binary is usually wrong.** Hardin's 1968 conclusion — privatize or have government regulation — was over-simplified. Ostrom's empirical contribution: institutional design at the user community level is often more effective than either privatization or central regulation. Modern platforms designing API quotas, governance councils, and contribution rules are applying Ostrom's framework whether they know it or not.\n\n**Third, the 8 principles are not optional add-ons; they're load-bearing.** Communities that miss several of Ostrom's 8 principles reliably collapse into Hardin tragedy. The principles are not a checklist of nice-to-haves; they are the structural mechanisms that make collective self-governance work.\n\nFile v1.0.5:skill-card.md\n\n## Description:
\nTragedy of the Commons helps agents diagnose shared-resource degradation and propose institutional designs using Hardin's commons framing and Ostrom's governance principles.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[deciqai](https://clawhub.ai/user/deciqai)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers, strategy teams, policy analysts, and AI agents use this skill to analyze commons problems such as API overuse, open-source burnout, shared infrastructure strain, fisheries collapse, and AI-era resource contention. It guides users through identifying the shared resource, checking the commons structure, auditing Ostrom's eight principles, and designing monitoring and intervention steps.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill's outputs can influence policy, governance, or operational strategy and may be mistaken for authoritative legal or operational advice.
\nMitigation: Review recommendations with appropriate domain, legal, policy, or operational experts before acting on them.
\nRisk: Users may include private organizational examples while adapting the skill or examples.
\nMitigation: Avoid adding sensitive internal details to persistent skill files unless intentional retention and sharing controls are in place.
\n\n\n## Reference(s):
\n- [ClawHub Skill Page](https://clawhub.ai/deciqai/skills/tragedy-of-the-commons)
\n- [Primary Sources](artifact/references/sources.md)
\n- [Hardin 1968 and Ostrom's Empirical Correction](artifact/examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md)
\n- [Grand Banks Cod Collapse and 1992 Moratorium](artifact/examples/grand-banks-cod-collapse-and-1992-moratorium.md)
\n- [AI-Era Commons: Open Web, Power, and GPUs](artifact/examples/ai-era-commons-open-web-power-gpus-2024-2026.md)
\n\n\n## Skill Output:
\n**Output Type(s):** [Guidance, Markdown, Text]
\n**Output Format:** [Markdown text with a structured commons analysis template]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Outputs include commons verification, an Ostrom audit, intervention recommendations, implementation sequence, metrics, and review cadence.]
\n\n## Skill Version(s):
\n1.0.5 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.4: 6 files, 12005 bytes\n\nFiles: examples/grand-banks-cod-collapse-and-1992-moratorium.md (5171b), examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md (5592b), references/sources.md (1825b), skill-card.md (2607b), SKILL.md (7791b), _meta.json (141b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: tragedy-of-the-commons\ndescription: >\n Activate when: shared resource is degrading even though no one is doing anything \"wrong\"; team complains about free riders or overuse; designing API quotas, rate limits, or open-source governance; someone says \"everyone is overusing this\" or \"the system worked fine until it got popular\"; evaluating why a platform or community is burning out.\n Do NOT activate when: the resource is fully non-rival (unlimited supply, zero marginal cost); the problem is a purely individual-action issue with no shared resource.\n---\n\n# Tragedy of the Commons\n\n## Overview\n\nWhen a shared resource has individual access but no individual responsibility for preservation, rational users extract private benefit while the cost of overuse is shared — leading to collective degradation. Garrett Hardin named this in 1968; Elinor Ostrom corrected it in 1990 (Nobel 2009): many communities self-govern commons via her 8 design principles without privatization or coercion.\n\nComposes with `prisoners-dilemma`, `principal-agent`, `network-effects`, `goodharts-law`, `repeated-games-reputation`.\n\n## When to Use\n\n- Diagnosing why a shared resource is degrading (open-source burnout, API abuse, attention market polarizing)\n- Designing platforms, marketplaces, shared infrastructure, API quotas, or rate limits\n- Designing workplace norms around shared resources (meetings, Slack, email)\n- Evaluating regulatory or policy responses to shared-resource problems\n\n**Not when:** resource is genuinely non-rival; fully private; \"commons\" framing is misapplied to individual-action problems.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete commons case → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line: when a shared resource degrades despite each user acting rationally, you have a commons problem — the answer is institutional design per Ostrom's 8 principles, not just \"privatize\" or \"regulate.\"\n2. Check fit: shared resource + individual extraction + shared cost? If not, different frameworks apply.\n3. Elicit the resource, users, and current rules: What's shared? Who has access? What rules govern use? What's failing?\n> **[WAIT — do not advance until user responds]**\n4. Audit which of Ostrom's 8 principles are present / weak / absent in their situation.\n> **[WAIT — do not advance until user responds]**\n5. Close: name the institutional gaps + propose design applying missing principles + monitoring plan.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Identify:** shared resource · user community · failure mode · current rules.\n**Step 2 — Verify commons structure:** shared access + rivalrous + diffuse responsibility + Hardin pattern (individually rational, collectively destructive). All four yes → commons.\n**Step 3 — Ostrom audit** (mark present / weak / absent): 1 Boundaries · 2 Congruence · 3 Collective-choice · 4 Monitoring · 5 Graduated sanctions · 6 Conflict resolution · 7 Right to organize · 8 Nested enterprises. Weak/absent = design targets.\n**Step 4 — Intervene:** for each weak/absent principle, design a specific fix. Avoid the \"privatize or regulate\" binary — Ostrom's institutional design often outperforms both.\n**Step 5 — Monitor:** sequence · metrics (resource health, sanctions issued) · quarterly review.\n\n## Output Template\n```\nCommons Design: \nStructure: shared resource | boundaries | failure mode | current rules\nVerification: shared Y/N · rivalrous Y/N · diffuse responsibility Y/N · Hardin pattern Y/N\nOstrom audit: [1–8: present/weak/absent]\nIntervention: [per weak/absent principle] · why not privatize · why not pure regulation\nImplementation: sequence · metrics · review cycle\n```\n\n*→ Method in Action: [Hardin 1968 + Ostrom's Empirical Correction + Modern Digital Applications](examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md) · [Grand Banks Cod Collapse](examples/grand-banks-cod-collapse-and-1992-moratorium.md)*\n\n## Pack: Commons Patterns\n\n| Commons | Failure mode | Ostrom countermeasure |\n|---|---|---|\n| Open-source project | Maintainer burnout | Contribution rules; governance council; sustaining funding |\n| API / cloud infrastructure | Abuse degrades service for all | Tiered quotas; monitoring; graduated sanctions |\n| Slack / meetings | Notification overload | Norms; meeting-free blocks; signal-noise metrics |\n| Fisheries / antibiotic efficacy | Stock collapse / resistance | Quotas; stewardship programs; surveillance |\n| Atmospheric carbon | Climate change | Carbon pricing; international agreements; local action |\n\n## Applying It Well\n\n- Ostrom's 8 principles are load-bearing, not optional: missing several reliably produces Hardin tragedy.\n- Privatization works when exclusion is feasible and transaction costs are low. Regulation works when the regulator has information and legitimacy. Ostrom's self-governance works when users can communicate, monitor, and self-organize — often best for technical commons.\n- Peer monitoring (users see each other's behavior) differs from punitive surveillance; successful commons use the former.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"Commons always fail; we have to privatize\" | Hardin over-stated this. Ostrom's empirical evidence: many commons endure for centuries with the 8 principles. |\n| [D] \"The government must regulate\" | Sometimes. Often community self-governance is faster, cheaper, and more legitimate. |\n| [D] \"Punish free riders; that's enough\" | Graduated sanctions is one of 8 principles. Punishment alone without monitoring, boundaries, etc. doesn't work. |\n| [D] \"Open source means free; we don't owe anything\" | Maintainer labor is a commons; without contribution mechanisms it depletes (xz 2024 was the warning). |\n| [D] \"Our users would never abuse the API\" | The Hardin structure predicts abuse from a substantial fraction regardless of intent. Design accordingly. |\n| [D] \"We don't need formal governance; people are reasonable\" | Even reasonable people benefit from boundaries, monitoring, and conflict resolution. |\n| [D] \"Monitoring is surveillance; we don't do that\" | Ostrom distinguishes cooperative peer-monitoring from punitive surveillance. Successful commons use the former. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Shared resource degrading; rules unclear or unenforced\n- Free-rider complaints but no graduated sanctions exist\n- Users have no voice in rule-setting (Ostrom principle 3 absent)\n- Default response is \"regulate it\" or \"privatize it\" without considering institutional design\n\n## Verification\n\n- [ ] Shared resource and user boundaries specified\n- [ ] Commons structure verified (shared + rivalrous + diffuse responsibility)\n- [ ] Ostrom's 8 principles audited; weak/absent identified\n- [ ] Institutional intervention designed; privatize-or-regulate alternatives addressed\n- [ ] Monitoring metrics and review cycle scheduled\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 164 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/tragedy-of-the-commons** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.4:_meta.json\n\n{\n \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n \"slug\": \"tragedy-of-the-commons\",\n \"version\": \"1.0.4\",\n \"publishedAt\": 1783509818834\n}\n\nFile v1.0.4:references/sources.md\n\n# Sources — tragedy-of-the-commons\n\n> *Primary sources for the [tragedy-of-the-commons](../SKILL.md) skill.*\n\n- Hardin, G. (1968). \"The Tragedy of the Commons.\" *Science*, 162(3859), 1243-1248. The foundational paper.\n- Hardin, G. (1998). \"Extensions of 'The Tragedy of the Commons'.\" *Science*, 280(5364), 682-683. Hardin's update acknowledging Ostrom.\n- Ostrom, E. (1990). *Governing the Commons: The Evolution of Institutions for Collective Action.* Cambridge University Press. ISBN 978-0521405997. The empirical correction.\n- Ostrom, E. (2009). \"A General Framework for Analyzing Sustainability of Social-Ecological Systems.\" *Science*, 325(5939), 419-422. The synthesis.\n- Olson, M. (1965). *The Logic of Collective Action.* Harvard University Press. ISBN 978-0674537514. The collective-action problem foundation.\n- Lloyd, W. F. (1833). *Two Lectures on the Checks to Population.* Oxford University Press. The historical predecessor Hardin cites.\n- Dietz, T., Ostrom, E., & Stern, P. C. (2003). \"The struggle to govern the commons.\" *Science*, 302(5652), 1907-1912. The state-of-the-art summary.\n- Ostrom, E., Burger, J., Field, C. B., Norgaard, R. B., & Policansky, D. (1999). \"Revisiting the commons: Local lessons, global challenges.\" *Science*, 284(5412), 278-282.\n- Buck, S. J. (1998). *The Global Commons: An Introduction.* Island Press. ISBN 978-1559633499. Applied to modern global commons.\n- Kurlansky, M. (1997). *Cod: A Biography of the Fish That Changed the World.* Walker & Company. The Grand Banks collapse narrative.\n- Hutchings, J. A., & Myers, R. A. (1994). \"What can be learned from the collapse of a renewable resource? Atlantic cod, Gadus morhua, of Newfoundland and Labrador.\" *Canadian Journal of Fisheries and Aquatic Sciences*, 51(9), 2126-2146. The scientific post-mortem of the cod collapse.\n\nFile v1.0.4:examples/grand-banks-cod-collapse-and-1992-moratorium.md\n\n# Method in Action: The Grand Banks Cod Collapse and the 1992 Moratorium (1950s–1992)\n\n> *Example for the [tragedy-of-the-commons](../SKILL.md) skill.*\n\nThe northern cod fishery off Newfoundland ran for roughly five centuries — European fleets worked the Grand Banks from the late 1400s onward — and then collapsed within a few decades of industrialization. It is the canonical natural-resource commons tragedy, and it also demonstrates the skill's sharpest lesson: central regulation without Ostrom's institutional structure fails just like an unmanaged commons.\n\n**Step 1 — Identify.** Shared resource: the northern cod stock (Gadus morhua) off Newfoundland and Labrador. User community: Newfoundland inshore fishers (small boats, local knowledge), Canadian offshore trawler companies, and foreign distant-water factory fleets. Failure mode: stock collapse. Current rules (pre-collapse): open international access beyond territorial waters; after Canada's 200-mile exclusive economic zone declaration in 1977, centralized quotas set by the federal Department of Fisheries and Oceans (DFO).\n\n**Step 2 — Verify commons structure.** Shared access: yes — no single actor could exclude others. Rivalrous: yes — every tonne caught is unavailable to everyone else and to the spawning stock. Diffuse responsibility: yes — no fleet bore the cost of its own overfishing; the cost was spread across all users and the future. Hardin pattern: yes — each captain's rational move was to catch more before competitors did. Post-WWII factory trawlers from Europe and the USSR drove reported catches to a historic peak around 800,000 tonnes in 1968, several times the long-run sustainable harvest. All four conditions present: a textbook commons.\n\n**Step 3 — Ostrom audit.** This is the instructive part — Canada *did* regulate after 1977, and the stock still collapsed, because nearly every design principle was weak or absent:\n\n- **1 Boundaries — weak.** The 200-mile zone came only in 1977; foreign fleets kept fishing the \"Nose\" and \"Tail\" of the Banks that lay outside it.\n- **2 Congruence — absent.** DFO quotas rested on offshore survey models that overestimated the stock; harvest rules did not match the resource's actual condition.\n- **3 Collective-choice — absent.** Inshore fishers reported shrinking fish and falling catches through the 1980s; their local knowledge had no channel into quota-setting, and the warnings were dismissed as anecdote.\n- **4 Monitoring — weak.** Discarding, misreporting, and high-grading at sea were widespread and largely unobserved.\n- **5 Graduated sanctions — weak.** Quota violations carried little consequence relative to the profit from cheating.\n- **6 Conflict resolution — absent.** The inshore–offshore dispute over who was destroying the stock festered for a decade with no legitimate forum.\n- **7 Right to organize — absent.** Fishing communities had no recognized authority to set or enforce local rules.\n- **8 Nested enterprises — absent.** A single centralized regulator managed a resource spanning local, national, and international scales.\n\n**Step 4 — Intervene (what actually happened).** The intervention came only after the resource was gone. On July 2, 1992, Canada's fisheries minister declared a moratorium on the northern cod fishery. The spawning stock had fallen to a small fraction of its historical level; roughly 30,000 fishers and plant workers lost their livelihoods — often described as the largest single industrial layoff in Canadian history. The moratorium was announced as a two-year pause; the stock did not meaningfully recover for decades.\n\n**Step 5 — Monitor.** The post-mortem literature (Hutchings & Myers 1994) concluded the collapse was driven by overfishing, not environment alone — the monitoring system had measured the wrong things and ignored the users closest to the resource.\n\nThe mapped steps:\n1. Identify: northern cod stock · inshore/offshore/foreign fleets · stock collapse · open access, then centralized quotas\n2. Verify commons structure: shared ✓ rivalrous ✓ diffuse responsibility ✓ Hardin pattern ✓\n3. Ostrom audit: principles 2, 3, 6, 7, 8 absent; 1, 4, 5 weak — regulation without institutional design\n4. Intervene: 1992 moratorium — imposed after collapse instead of designed before it\n5. Monitor: scientific post-mortem confirmed overfishing under a monitoring regime that excluded local knowledge\n\nThe operational lesson inverts the \"just regulate it\" reflex: Canada had a regulator, quotas, and science, yet reproduced the unmanaged-commons outcome because congruence, collective-choice, and nested governance were missing. Contrast with Ostrom's enduring fisheries commons, where users who monitor each other and set their own rules sustained harvests for centuries.\n\nPrimary sources: Kurlansky, M. (1997). *Cod: A Biography of the Fish That Changed the World.* Walker & Company. Hutchings, J. A., & Myers, R. A. (1994). \"What can be learned from the collapse of a renewable resource? Atlantic cod, Gadus morhua, of Newfoundland and Labrador.\" *Canadian Journal of Fisheries and Aquatic Sciences*, 51(9), 2126-2146.\n\nFile v1.0.4:examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md\n\n# Method in Action: Hardin 1968 + Ostrom's Empirical Correction + Modern Digital Applications\n\n> *Example for the [tragedy-of-the-commons](../SKILL.md) skill.*\n\nThe Hardin 1968 paper was operationally famous and operationally influential, but its conclusions were over-stated and partially wrong. Hardin himself acknowledged this in a 1998 follow-up paper:\n\n> Hardin, G. (1998). \"Extensions of 'The Tragedy of the Commons'.\" *Science*, 280(5364), 682-683.\n\nHardin's 1998 update acknowledged Ostrom's empirical findings and clarified that his 1968 paper had over-generalized: his analysis applied to *unmanaged* commons, not to commons with established governance institutions. The 1998 paper explicitly cited Ostrom and recommended her institutional approach for managed commons.\n\n**Elinor Ostrom's 1990** book *Governing the Commons* documented hundreds of cases of long-enduring commons institutions:\n\n- **Swiss alpine pastures.** Communities like Törbel, Switzerland have managed summer pastures cooperatively for 500+ years, with no degradation. The institutional structure exhibits all 8 of Ostrom's principles: clearly defined boundaries (only Törbel residents can use the pasture), congruence (one cow per resident in summer), collective-choice (annual village assembly sets rules), monitoring (residents see each other's herds daily), graduated sanctions (first violation = warning, repeated = fine, persistent = exclusion), conflict resolution (village courts), recognition by Swiss government, nested governance.\n\n- **Japanese coastal fisheries.** Village fisheries communities in Hokkaido have maintained common-property rights over coastal waters for centuries, with sustainable harvests. The institutional features mirror the Swiss case adjusted for fisheries.\n\n- **Spanish irrigation systems (huertas of Valencia).** Communities have shared water in Mediterranean basins for 1000+ years through \"tribunals of waters\" — weekly meetings at the cathedral door where farmers resolve disputes. The system has worked since at least the Moorish period.\n\n- **Philippine forest user groups.** Ostrom documented village-level forest management that sustained forest cover where state-managed forests collapsed.\n\nOstrom's empirical claim: when the 8 design principles are present, commons institutions endure for centuries; when they're absent, the Hardin tragedy unfolds.\n\nThe framework has been applied at industrial scale in modern digital and technical commons:\n\n**Open-source software governance.** The Linux kernel, the Apache foundation, the Cloud Native Computing Foundation, Wikipedia — all are commons that have applied Ostrom-style design (governance councils, contribution rules, code-of-conduct enforcement, conflict resolution). The successful projects exhibit Ostrom's principles; the failed ones typically miss several.\n\n**API rate limiting and quota systems.** Modern cloud providers (AWS, Google Cloud, OpenAI, Anthropic) use Ostrom-style commons design for shared infrastructure: clearly defined tiers (boundaries), congruent quotas (rules match capacity), monitoring (usage dashboards), graduated sanctions (throttling → suspension → ban), appeals processes (conflict resolution).\n\n**Wikipedia governance.** Wikipedia's editorial commons has remained productive for 20+ years despite being entirely volunteer-driven. The institutional structure (administrators, arbitration committee, RFC process, edit-warring sanctions) exhibits most of Ostrom's 8 principles.\n\n**Workplace shared resources.** Modern guidance on meeting hygiene, Slack norms, email discipline, \"Maker vs Manager schedules\" (Paul Graham 2009) is implicitly Ostrom-style: defining boundaries (meeting-free time blocks), congruence (meeting calls match actual coordination needs), monitoring (calendar audits), graduated sanctions (cultural pushback against bad-meeting-callers).\n\n**Cybersecurity (shared internet infrastructure).** The DNS root server system, BGP routing, IP address allocation, certificate authorities — all are commons. The institutional governance (ICANN, IETF, regional internet registries) is broadly Ostrom-structured.\n\n**AI training data commons.** The current AI training-data commons crisis (publishers walling off content; content quality degrading as AI-generated text floods the web) is unfolding in real time as a textbook Hardin tragedy. The Ostrom-style response — institutional design for shared training data, with contribution rules and compensation mechanisms — is being debated at the policy level.\n\nThree operational lessons:\n\n**First, modern technical commons are everywhere.** Anywhere a platform, API, ecosystem, or shared infrastructure has multiple users with individual access, you have a commons. The Hardin dynamics will operate unless Ostrom-style institutional design is applied.\n\n**Second, the privatize-or-regulate binary is usually wrong.** Hardin's 1968 conclusion — privatize or have government regulation — was over-simplified. Ostrom's empirical contribution: institutional design at the user community level is often more effective than either privatization or central regulation. Modern platforms designing API quotas, governance councils, and contribution rules are applying Ostrom's framework whether they know it or not.\n\n**Third, the 8 principles are not optional add-ons; they're load-bearing.** Communities that miss several of Ostrom's 8 principles reliably collapse into Hardin tragedy. The principles are not a checklist of nice-to-haves; they are the structural mechanisms that make collective self-governance work.\n\nFile v1.0.4:skill-card.md\n\n## Description:
\nHelps an agent diagnose shared-resource degradation and design commons governance using Hardin's commons pattern and Ostrom's institutional design principles.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[deciqai](https://clawhub.ai/user/deciqai)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nAgents use this skill to help developers, operators, policy teams, and community stewards analyze commons problems such as API overuse, open-source maintainer burnout, workplace attention overload, or shared natural-resource depletion. It guides the agent toward a structured commons verification, Ostrom audit, intervention plan, and monitoring cycle.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Sensitive real-world case details could be exposed if users add observed examples to a shared or public copy of the skill.
\nMitigation: Keep sensitive case details out of shared skill files; anonymize examples and retain private incident details only in appropriate internal systems.
\nRisk: Commons analyses can be misapplied when the resource is not actually shared, rivalrous, or governed by diffuse responsibility.
\nMitigation: Use the skill's verification checklist before relying on recommendations, and have domain owners review proposed governance changes before deployment.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/deciqai/skills/tragedy-of-the-commons)
\n- [Sources - tragedy-of-the-commons](references/sources.md)
\n- [Hardin 1968 + Ostrom's Empirical Correction + Modern Digital Applications](examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md)
\n- [Grand Banks Cod Collapse and 1992 Moratorium](examples/grand-banks-cod-collapse-and-1992-moratorium.md)
\n\n\n## Skill Output:
\n**Output Type(s):** [Guidance, Analysis, Markdown]
\n**Output Format:** [Markdown structured report using the Commons Design template]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May include step-by-step coaching questions, an Ostrom principle audit, intervention recommendations, metrics, and a review cycle.]
\n\n## Skill Version(s):
\n1.0.4 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.3: 6 files, 11822 bytes\n\nFiles: examples/grand-banks-cod-collapse-and-1992-moratorium.md (5171b), examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md (5592b), references/sources.md (1825b), skill-card.md (2056b), SKILL.md (7903b), _meta.json (141b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: tragedy-of-the-commons\ndescription: >\n Activate when: shared resource is degrading even though no one is doing anything \"wrong\"; team complains about free riders or overuse; designing API quotas, rate limits, or open-source governance; someone says \"everyone is overusing this\" or \"the system worked fine until it got popular\"; evaluating why a platform or community is burning out.\n Do NOT activate when: the resource is fully non-rival (unlimited supply, zero marginal cost); the problem is a purely individual-action issue with no shared resource.\n---\n\n# Tragedy of the Commons\n\n## Overview\n\nWhen a shared resource has individual access but no individual responsibility for preservation, rational users extract private benefit while the cost of overuse is shared — leading to collective degradation. Garrett Hardin named this in 1968; Elinor Ostrom corrected it in 1990 (Nobel 2009): many communities self-govern commons via her 8 design principles without privatization or coercion.\n\nComposes with `prisoners-dilemma`, `principal-agent`, `network-effects`, `goodharts-law`, `repeated-games-reputation`.\n\n## When to Use\n\n- Diagnosing why a shared resource is degrading (open-source burnout, API abuse, attention market polarizing)\n- Designing platforms, marketplaces, shared infrastructure, API quotas, or rate limits\n- Designing workplace norms around shared resources (meetings, Slack, email)\n- Evaluating regulatory or policy responses to shared-resource problems\n\n**Not when:** resource is genuinely non-rival; fully private; \"commons\" framing is misapplied to individual-action problems.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete commons case → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line: when a shared resource degrades despite each user acting rationally, you have a commons problem — the answer is institutional design per Ostrom's 8 principles, not just \"privatize\" or \"regulate.\"\n2. Check fit: shared resource + individual extraction + shared cost? If not, different frameworks apply.\n3. Elicit the resource, users, and current rules: What's shared? Who has access? What rules govern use? What's failing?\n> **[WAIT — do not advance until user responds]**\n4. Audit which of Ostrom's 8 principles are present / weak / absent in their situation.\n> **[WAIT — do not advance until user responds]**\n5. Close: name the institutional gaps + propose design applying missing principles + monitoring plan.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Identify:** shared resource · user community · failure mode · current rules.\n**Step 2 — Verify commons structure:** shared access + rivalrous + diffuse responsibility + Hardin pattern (individually rational, collectively destructive). All four yes → commons.\n**Step 3 — Ostrom audit** (mark present / weak / absent): 1 Boundaries · 2 Congruence · 3 Collective-choice · 4 Monitoring · 5 Graduated sanctions · 6 Conflict resolution · 7 Right to organize · 8 Nested enterprises. Weak/absent = design targets.\n**Step 4 — Intervene:** for each weak/absent principle, design a specific fix. Avoid the \"privatize or regulate\" binary — Ostrom's institutional design often outperforms both.\n**Step 5 — Monitor:** sequence · metrics (resource health, sanctions issued) · quarterly review.\n\n## Output Template\n```\nCommons Design: \nStructure: shared resource | boundaries | failure mode | current rules\nVerification: shared Y/N · rivalrous Y/N · diffuse responsibility Y/N · Hardin pattern Y/N\nOstrom audit: [1–8: present/weak/absent]\nIntervention: [per weak/absent principle] · why not privatize · why not pure regulation\nImplementation: sequence · metrics · review cycle\n```\n\n*→ Method in Action: [Hardin 1968 + Ostrom's Empirical Correction + Modern Digital Applications](examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md) · [Grand Banks Cod Collapse](examples/grand-banks-cod-collapse-and-1992-moratorium.md)*\n\n## Pack: Commons Patterns\n\n| Commons | Failure mode | Ostrom countermeasure |\n|---|---|---|\n| Open-source project | Maintainer burnout | Contribution rules; governance council; sustaining funding |\n| API / cloud infrastructure | Abuse degrades service for all | Tiered quotas; monitoring; graduated sanctions |\n| Slack / meetings | Notification overload | Norms; meeting-free blocks; signal-noise metrics |\n| Fisheries / antibiotic efficacy | Stock collapse / resistance | Quotas; stewardship programs; surveillance |\n| Atmospheric carbon | Climate change | Carbon pricing; international agreements; local action |\n\n## Applying It Well\n\n- Ostrom's 8 principles are load-bearing, not optional: missing several reliably produces Hardin tragedy.\n- Privatization works when exclusion is feasible and transaction costs are low. Regulation works when the regulator has information and legitimacy. Ostrom's self-governance works when users can communicate, monitor, and self-organize — often best for technical commons.\n- Peer monitoring (users see each other's behavior) differs from punitive surveillance; successful commons use the former.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"Commons always fail; we have to privatize\" | Hardin over-stated this. Ostrom's empirical evidence: many commons endure for centuries with the 8 principles. |\n| [D] \"The government must regulate\" | Sometimes. Often community self-governance is faster, cheaper, and more legitimate. |\n| [D] \"Punish free riders; that's enough\" | Graduated sanctions is one of 8 principles. Punishment alone without monitoring, boundaries, etc. doesn't work. |\n| [D] \"Open source means free; we don't owe anything\" | Maintainer labor is a commons; without contribution mechanisms it depletes (xz 2024 was the warning). |\n| [D] \"Our users would never abuse the API\" | The Hardin structure predicts abuse from a substantial fraction regardless of intent. Design accordingly. |\n| [D] \"We don't need formal governance; people are reasonable\" | Even reasonable people benefit from boundaries, monitoring, and conflict resolution. |\n| [D] \"Monitoring is surveillance; we don't do that\" | Ostrom distinguishes cooperative peer-monitoring from punitive surveillance. Successful commons use the former. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Shared resource degrading; rules unclear or unenforced\n- Free-rider complaints but no graduated sanctions exist\n- Users have no voice in rule-setting (Ostrom principle 3 absent)\n- Default response is \"regulate it\" or \"privatize it\" without considering institutional design\n\n## Verification\n\n- [ ] Shared resource and user boundaries specified\n- [ ] Commons structure verified (shared + rivalrous + diffuse responsibility)\n- [ ] Ostrom's 8 principles audited; weak/absent identified\n- [ ] Institutional intervention designed; privatize-or-regulate alternatives addressed\n- [ ] Monitoring metrics and review cycle scheduled\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 163 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/skills/tragedy-of-the-commons?utm_source=clawhub&utm_medium=marketplace&utm_campaign=knowledge-skills&utm_content=tragedy-of-the-commons** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.3:_meta.json\n\n{\n \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n \"slug\": \"tragedy-of-the-commons\",\n \"version\": \"1.0.3\",\n \"publishedAt\": 1783482768089\n}\n\nFile v1.0.3:references/sources.md\n\n# Sources — tragedy-of-the-commons\n\n> *Primary sources for the [tragedy-of-the-commons](../SKILL.md) skill.*\n\n- Hardin, G. (1968). \"The Tragedy of the Commons.\" *Science*, 162(3859), 1243-1248. The foundational paper.\n- Hardin, G. (1998). \"Extensions of 'The Tragedy of the Commons'.\" *Science*, 280(5364), 682-683. Hardin's update acknowledging Ostrom.\n- Ostrom, E. (1990). *Governing the Commons: The Evolution of Institutions for Collective Action.* Cambridge University Press. ISBN 978-0521405997. The empirical correction.\n- Ostrom, E. (2009). \"A General Framework for Analyzing Sustainability of Social-Ecological Systems.\" *Science*, 325(5939), 419-422. The synthesis.\n- Olson, M. (1965). *The Logic of Collective Action.* Harvard University Press. ISBN 978-0674537514. The collective-action problem foundation.\n- Lloyd, W. F. (1833). *Two Lectures on the Checks to Population.* Oxford University Press. The historical predecessor Hardin cites.\n- Dietz, T., Ostrom, E., & Stern, P. C. (2003). \"The struggle to govern the commons.\" *Science*, 302(5652), 1907-1912. The state-of-the-art summary.\n- Ostrom, E., Burger, J., Field, C. B., Norgaard, R. B., & Policansky, D. (1999). \"Revisiting the commons: Local lessons, global challenges.\" *Science*, 284(5412), 278-282.\n- Buck, S. J. (1998). *The Global Commons: An Introduction.* Island Press. ISBN 978-1559633499. Applied to modern global commons.\n- Kurlansky, M. (1997). *Cod: A Biography of the Fish That Changed the World.* Walker & Company. The Grand Banks collapse narrative.\n- Hutchings, J. A., & Myers, R. A. (1994). \"What can be learned from the collapse of a renewable resource? Atlantic cod, Gadus morhua, of Newfoundland and Labrador.\" *Canadian Journal of Fisheries and Aquatic Sciences*, 51(9), 2126-2146. The scientific post-mortem of the cod collapse.\n\nFile v1.0.3:examples/grand-banks-cod-collapse-and-1992-moratorium.md\n\n# Method in Action: The Grand Banks Cod Collapse and the 1992 Moratorium (1950s–1992)\n\n> *Example for the [tragedy-of-the-commons](../SKILL.md) skill.*\n\nThe northern cod fishery off Newfoundland ran for roughly five centuries — European fleets worked the Grand Banks from the late 1400s onward — and then collapsed within a few decades of industrialization. It is the canonical natural-resource commons tragedy, and it also demonstrates the skill's sharpest lesson: central regulation without Ostrom's institutional structure fails just like an unmanaged commons.\n\n**Step 1 — Identify.** Shared resource: the northern cod stock (Gadus morhua) off Newfoundland and Labrador. User community: Newfoundland inshore fishers (small boats, local knowledge), Canadian offshore trawler companies, and foreign distant-water factory fleets. Failure mode: stock collapse. Current rules (pre-collapse): open international access beyond territorial waters; after Canada's 200-mile exclusive economic zone declaration in 1977, centralized quotas set by the federal Department of Fisheries and Oceans (DFO).\n\n**Step 2 — Verify commons structure.** Shared access: yes — no single actor could exclude others. Rivalrous: yes — every tonne caught is unavailable to everyone else and to the spawning stock. Diffuse responsibility: yes — no fleet bore the cost of its own overfishing; the cost was spread across all users and the future. Hardin pattern: yes — each captain's rational move was to catch more before competitors did. Post-WWII factory trawlers from Europe and the USSR drove reported catches to a historic peak around 800,000 tonnes in 1968, several times the long-run sustainable harvest. All four conditions present: a textbook commons.\n\n**Step 3 — Ostrom audit.** This is the instructive part — Canada *did* regulate after 1977, and the stock still collapsed, because nearly every design principle was weak or absent:\n\n- **1 Boundaries — weak.** The 200-mile zone came only in 1977; foreign fleets kept fishing the \"Nose\" and \"Tail\" of the Banks that lay outside it.\n- **2 Congruence — absent.** DFO quotas rested on offshore survey models that overestimated the stock; harvest rules did not match the resource's actual condition.\n- **3 Collective-choice — absent.** Inshore fishers reported shrinking fish and falling catches through the 1980s; their local knowledge had no channel into quota-setting, and the warnings were dismissed as anecdote.\n- **4 Monitoring — weak.** Discarding, misreporting, and high-grading at sea were widespread and largely unobserved.\n- **5 Graduated sanctions — weak.** Quota violations carried little consequence relative to the profit from cheating.\n- **6 Conflict resolution — absent.** The inshore–offshore dispute over who was destroying the stock festered for a decade with no legitimate forum.\n- **7 Right to organize — absent.** Fishing communities had no recognized authority to set or enforce local rules.\n- **8 Nested enterprises — absent.** A single centralized regulator managed a resource spanning local, national, and international scales.\n\n**Step 4 — Intervene (what actually happened).** The intervention came only after the resource was gone. On July 2, 1992, Canada's fisheries minister declared a moratorium on the northern cod fishery. The spawning stock had fallen to a small fraction of its historical level; roughly 30,000 fishers and plant workers lost their livelihoods — often described as the largest single industrial layoff in Canadian history. The moratorium was announced as a two-year pause; the stock did not meaningfully recover for decades.\n\n**Step 5 — Monitor.** The post-mortem literature (Hutchings & Myers 1994) concluded the collapse was driven by overfishing, not environment alone — the monitoring system had measured the wrong things and ignored the users closest to the resource.\n\nThe mapped steps:\n1. Identify: northern cod stock · inshore/offshore/foreign fleets · stock collapse · open access, then centralized quotas\n2. Verify commons structure: shared ✓ rivalrous ✓ diffuse responsibility ✓ Hardin pattern ✓\n3. Ostrom audit: principles 2, 3, 6, 7, 8 absent; 1, 4, 5 weak — regulation without institutional design\n4. Intervene: 1992 moratorium — imposed after collapse instead of designed before it\n5. Monitor: scientific post-mortem confirmed overfishing under a monitoring regime that excluded local knowledge\n\nThe operational lesson inverts the \"just regulate it\" reflex: Canada had a regulator, quotas, and science, yet reproduced the unmanaged-commons outcome because congruence, collective-choice, and nested governance were missing. Contrast with Ostrom's enduring fisheries commons, where users who monitor each other and set their own rules sustained harvests for centuries.\n\nPrimary sources: Kurlansky, M. (1997). *Cod: A Biography of the Fish That Changed the World.* Walker & Company. Hutchings, J. A., & Myers, R. A. (1994). \"What can be learned from the collapse of a renewable resource? Atlantic cod, Gadus morhua, of Newfoundland and Labrador.\" *Canadian Journal of Fisheries and Aquatic Sciences*, 51(9), 2126-2146.\n\nFile v1.0.3:examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md\n\n# Method in Action: Hardin 1968 + Ostrom's Empirical Correction + Modern Digital Applications\n\n> *Example for the [tragedy-of-the-commons](../SKILL.md) skill.*\n\nThe Hardin 1968 paper was operationally famous and operationally influential, but its conclusions were over-stated and partially wrong. Hardin himself acknowledged this in a 1998 follow-up paper:\n\n> Hardin, G. (1998). \"Extensions of 'The Tragedy of the Commons'.\" *Science*, 280(5364), 682-683.\n\nHardin's 1998 update acknowledged Ostrom's empirical findings and clarified that his 1968 paper had over-generalized: his analysis applied to *unmanaged* commons, not to commons with established governance institutions. The 1998 paper explicitly cited Ostrom and recommended her institutional approach for managed commons.\n\n**Elinor Ostrom's 1990** book *Governing the Commons* documented hundreds of cases of long-enduring commons institutions:\n\n- **Swiss alpine pastures.** Communities like Törbel, Switzerland have managed summer pastures cooperatively for 500+ years, with no degradation. The institutional structure exhibits all 8 of Ostrom's principles: clearly defined boundaries (only Törbel residents can use the pasture), congruence (one cow per resident in summer), collective-choice (annual village assembly sets rules), monitoring (residents see each other's herds daily), graduated sanctions (first violation = warning, repeated = fine, persistent = exclusion), conflict resolution (village courts), recognition by Swiss government, nested governance.\n\n- **Japanese coastal fisheries.** Village fisheries communities in Hokkaido have maintained common-property rights over coastal waters for centuries, with sustainable harvests. The institutional features mirror the Swiss case adjusted for fisheries.\n\n- **Spanish irrigation systems (huertas of Valencia).** Communities have shared water in Mediterranean basins for 1000+ years through \"tribunals of waters\" — weekly meetings at the cathedral door where farmers resolve disputes. The system has worked since at least the Moorish period.\n\n- **Philippine forest user groups.** Ostrom documented village-level forest management that sustained forest cover where state-managed forests collapsed.\n\nOstrom's empirical claim: when the 8 design principles are present, commons institutions endure for centuries; when they're absent, the Hardin tragedy unfolds.\n\nThe framework has been applied at industrial scale in modern digital and technical commons:\n\n**Open-source software governance.** The Linux kernel, the Apache foundation, the Cloud Native Computing Foundation, Wikipedia — all are commons that have applied Ostrom-style design (governance councils, contribution rules, code-of-conduct enforcement, conflict resolution). The successful projects exhibit Ostrom's principles; the failed ones typically miss several.\n\n**API rate limiting and quota systems.** Modern cloud providers (AWS, Google Cloud, OpenAI, Anthropic) use Ostrom-style commons design for shared infrastructure: clearly defined tiers (boundaries), congruent quotas (rules match capacity), monitoring (usage dashboards), graduated sanctions (throttling → suspension → ban), appeals processes (conflict resolution).\n\n**Wikipedia governance.** Wikipedia's editorial commons has remained productive for 20+ years despite being entirely volunteer-driven. The institutional structure (administrators, arbitration committee, RFC process, edit-warring sanctions) exhibits most of Ostrom's 8 principles.\n\n**Workplace shared resources.** Modern guidance on meeting hygiene, Slack norms, email discipline, \"Maker vs Manager schedules\" (Paul Graham 2009) is implicitly Ostrom-style: defining boundaries (meeting-free time blocks), congruence (meeting calls match actual coordination needs), monitoring (calendar audits), graduated sanctions (cultural pushback against bad-meeting-callers).\n\n**Cybersecurity (shared internet infrastructure).** The DNS root server system, BGP routing, IP address allocation, certificate authorities — all are commons. The institutional governance (ICANN, IETF, regional internet registries) is broadly Ostrom-structured.\n\n**AI training data commons.** The current AI training-data commons crisis (publishers walling off content; content quality degrading as AI-generated text floods the web) is unfolding in real time as a textbook Hardin tragedy. The Ostrom-style response — institutional design for shared training data, with contribution rules and compensation mechanisms — is being debated at the policy level.\n\nThree operational lessons:\n\n**First, modern technical commons are everywhere.** Anywhere a platform, API, ecosystem, or shared infrastructure has multiple users with individual access, you have a commons. The Hardin dynamics will operate unless Ostrom-style institutional design is applied.\n\n**Second, the privatize-or-regulate binary is usually wrong.** Hardin's 1968 conclusion — privatize or have government regulation — was over-simplified. Ostrom's empirical contribution: institutional design at the user community level is often more effective than either privatization or central regulation. Modern platforms designing API quotas, governance councils, and contribution rules are applying Ostrom's framework whether they know it or not.\n\n**Third, the 8 principles are not optional add-ons; they're load-bearing.** Communities that miss several of Ostrom's 8 principles reliably collapse into Hardin tragedy. The principles are not a checklist of nice-to-haves; they are the structural mechanisms that make collective self-governance work.\n\nFile v1.0.3:skill-card.md\n\n## Description:
\nHelps agents diagnose shared-resource degradation and design commons governance using Hardin's framing and Ostrom's institutional design principles.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[deciqai](https://clawhub.ai/user/deciqai)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nEmployees, external users, developers, and policy or platform designers use this skill to identify commons dynamics in shared resources, audit gaps against Ostrom's 8 principles, and propose governance interventions.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill's examples and economic framing could be mistaken for authoritative policy advice.
\nMitigation: Use the output as analytical guidance and have domain experts review policy, regulatory, or operational decisions before implementation.
\n\n\n## Reference(s):
\n- [Sources - tragedy-of-the-commons](references/sources.md)
\n- [Hardin 1968 + Ostrom's Empirical Correction + Modern Digital Applications](examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md)
\n- [Grand Banks Cod Collapse and the 1992 Moratorium](examples/grand-banks-cod-collapse-and-1992-moratorium.md)
\n- [ClawHub skill page](https://clawhub.ai/deciqai/skills/tragedy-of-the-commons)
\n\n\n## Skill Output:
\n**Output Type(s):** [Text, Markdown, Guidance]
\n**Output Format:** [Markdown with a structured commons analysis template]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May ask step-by-step coaching questions before producing a final commons design.]
\n\n## Skill Version(s):
\n1.0.3 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.2: 5 files, 9131 bytes\n\nFiles: examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md (5592b), references/sources.md (1406b), skill-card.md (2806b), SKILL.md (7815b), _meta.json (141b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: tragedy-of-the-commons\ndescription: >\n Activate when: shared resource is degrading even though no one is doing anything \"wrong\"; team complains about free riders or overuse; designing API quotas, rate limits, or open-source governance; someone says \"everyone is overusing this\" or \"the system worked fine until it got popular\"; evaluating why a platform or community is burning out.\n Do NOT activate when: the resource is fully non-rival (unlimited supply, zero marginal cost); the problem is a purely individual-action issue with no shared resource.\n---\n\n# Tragedy of the Commons\n\n## Overview\n\nWhen a shared resource has individual access but no individual responsibility for preservation, rational users extract private benefit while the cost of overuse is shared — leading to collective degradation. Garrett Hardin named this in 1968; Elinor Ostrom corrected it in 1990 (Nobel 2009): many communities self-govern commons via her 8 design principles without privatization or coercion.\n\nComposes with `prisoners-dilemma`, `principal-agent`, `network-effects`, `goodharts-law`, `repeated-games-reputation`.\n\n## When to Use\n\n- Diagnosing why a shared resource is degrading (open-source burnout, API abuse, attention market polarizing)\n- Designing platforms, marketplaces, shared infrastructure, API quotas, or rate limits\n- Designing workplace norms around shared resources (meetings, Slack, email)\n- Evaluating regulatory or policy responses to shared-resource problems\n\n**Not when:** resource is genuinely non-rival; fully private; \"commons\" framing is misapplied to individual-action problems.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete commons case → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line: when a shared resource degrades despite each user acting rationally, you have a commons problem — the answer is institutional design per Ostrom's 8 principles, not just \"privatize\" or \"regulate.\"\n2. Check fit: shared resource + individual extraction + shared cost? If not, different frameworks apply.\n3. Elicit the resource, users, and current rules: What's shared? Who has access? What rules govern use? What's failing?\n> **[WAIT — do not advance until user responds]**\n4. Audit which of Ostrom's 8 principles are present / weak / absent in their situation.\n> **[WAIT — do not advance until user responds]**\n5. Close: name the institutional gaps + propose design applying missing principles + monitoring plan.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Identify:** shared resource · user community · failure mode · current rules.\n**Step 2 — Verify commons structure:** shared access + rivalrous + diffuse responsibility + Hardin pattern (individually rational, collectively destructive). All four yes → commons.\n**Step 3 — Ostrom audit** (mark present / weak / absent): 1 Boundaries · 2 Congruence · 3 Collective-choice · 4 Monitoring · 5 Graduated sanctions · 6 Conflict resolution · 7 Right to organize · 8 Nested enterprises. Weak/absent = design targets.\n**Step 4 — Intervene:** for each weak/absent principle, design a specific fix. Avoid the \"privatize or regulate\" binary — Ostrom's institutional design often outperforms both.\n**Step 5 — Monitor:** sequence · metrics (resource health, sanctions issued) · quarterly review.\n\n## Output Template\n```\nCommons Design: \nStructure: shared resource | boundaries | failure mode | current rules\nVerification: shared Y/N · rivalrous Y/N · diffuse responsibility Y/N · Hardin pattern Y/N\nOstrom audit: [1–8: present/weak/absent]\nIntervention: [per weak/absent principle] · why not privatize · why not pure regulation\nImplementation: sequence · metrics · review cycle\n```\n\n*→ Method in Action: [Hardin 1968 + Ostrom's Empirical Correction + Modern Digital Applications](examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md)*\n\n## Pack: Commons Patterns\n\n| Commons | Failure mode | Ostrom countermeasure |\n|---|---|---|\n| Open-source project | Maintainer burnout | Contribution rules; governance council; sustaining funding |\n| API / cloud infrastructure | Abuse degrades service for all | Tiered quotas; monitoring; graduated sanctions |\n| Slack / meetings | Notification overload | Norms; meeting-free blocks; signal-noise metrics |\n| Fisheries / antibiotic efficacy | Stock collapse / resistance | Quotas; stewardship programs; surveillance |\n| Atmospheric carbon | Climate change | Carbon pricing; international agreements; local action |\n\n## Applying It Well\n\n- Ostrom's 8 principles are load-bearing, not optional: missing several reliably produces Hardin tragedy.\n- Privatization works when exclusion is feasible and transaction costs are low. Regulation works when the regulator has information and legitimacy. Ostrom's self-governance works when users can communicate, monitor, and self-organize — often best for technical commons.\n- Peer monitoring (users see each other's behavior) differs from punitive surveillance; successful commons use the former.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"Commons always fail; we have to privatize\" | Hardin over-stated this. Ostrom's empirical evidence: many commons endure for centuries with the 8 principles. |\n| [D] \"The government must regulate\" | Sometimes. Often community self-governance is faster, cheaper, and more legitimate. |\n| [D] \"Punish free riders; that's enough\" | Graduated sanctions is one of 8 principles. Punishment alone without monitoring, boundaries, etc. doesn't work. |\n| [D] \"Open source means free; we don't owe anything\" | Maintainer labor is a commons; without contribution mechanisms it depletes (xz 2024 was the warning). |\n| [D] \"Our users would never abuse the API\" | The Hardin structure predicts abuse from a substantial fraction regardless of intent. Design accordingly. |\n| [D] \"We don't need formal governance; people are reasonable\" | Even reasonable people benefit from boundaries, monitoring, and conflict resolution. |\n| [D] \"Monitoring is surveillance; we don't do that\" | Ostrom distinguishes cooperative peer-monitoring from punitive surveillance. Successful commons use the former. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Shared resource degrading; rules unclear or unenforced\n- Free-rider complaints but no graduated sanctions exist\n- Users have no voice in rule-setting (Ostrom principle 3 absent)\n- Default response is \"regulate it\" or \"privatize it\" without considering institutional design\n\n## Verification\n\n- [ ] Shared resource and user boundaries specified\n- [ ] Commons structure verified (shared + rivalrous + diffuse responsibility)\n- [ ] Ostrom's 8 principles audited; weak/absent identified\n- [ ] Institutional intervention designed; privatize-or-regulate alternatives addressed\n- [ ] Monitoring metrics and review cycle scheduled\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 163 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/skills/tragedy-of-the-commons?utm_source=clawhub&utm_medium=marketplace&utm_campaign=knowledge-skills&utm_content=tragedy-of-the-commons** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.2:_meta.json\n\n{\n \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n \"slug\": \"tragedy-of-the-commons\",\n \"version\": \"1.0.2\",\n \"publishedAt\": 1783472888831\n}\n\nFile v1.0.2:references/sources.md\n\n# Sources — tragedy-of-the-commons\n\n> *Primary sources for the [tragedy-of-the-commons](../SKILL.md) skill.*\n\n- Hardin, G. (1968). \"The Tragedy of the Commons.\" *Science*, 162(3859), 1243-1248. The foundational paper.\n- Hardin, G. (1998). \"Extensions of 'The Tragedy of the Commons'.\" *Science*, 280(5364), 682-683. Hardin's update acknowledging Ostrom.\n- Ostrom, E. (1990). *Governing the Commons: The Evolution of Institutions for Collective Action.* Cambridge University Press. ISBN 978-0521405997. The empirical correction.\n- Ostrom, E. (2009). \"A General Framework for Analyzing Sustainability of Social-Ecological Systems.\" *Science*, 325(5939), 419-422. The synthesis.\n- Olson, M. (1965). *The Logic of Collective Action.* Harvard University Press. ISBN 978-0674537514. The collective-action problem foundation.\n- Lloyd, W. F. (1833). *Two Lectures on the Checks to Population.* Oxford University Press. The historical predecessor Hardin cites.\n- Dietz, T., Ostrom, E., & Stern, P. C. (2003). \"The struggle to govern the commons.\" *Science*, 302(5652), 1907-1912. The state-of-the-art summary.\n- Ostrom, E., Burger, J., Field, C. B., Norgaard, R. B., & Policansky, D. (1999). \"Revisiting the commons: Local lessons, global challenges.\" *Science*, 284(5412), 278-282.\n- Buck, S. J. (1998). *The Global Commons: An Introduction.* Island Press. ISBN 978-1559633499. Applied to modern global commons.\n\nFile v1.0.2:examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md\n\n# Method in Action: Hardin 1968 + Ostrom's Empirical Correction + Modern Digital Applications\n\n> *Example for the [tragedy-of-the-commons](../SKILL.md) skill.*\n\nThe Hardin 1968 paper was operationally famous and operationally influential, but its conclusions were over-stated and partially wrong. Hardin himself acknowledged this in a 1998 follow-up paper:\n\n> Hardin, G. (1998). \"Extensions of 'The Tragedy of the Commons'.\" *Science*, 280(5364), 682-683.\n\nHardin's 1998 update acknowledged Ostrom's empirical findings and clarified that his 1968 paper had over-generalized: his analysis applied to *unmanaged* commons, not to commons with established governance institutions. The 1998 paper explicitly cited Ostrom and recommended her institutional approach for managed commons.\n\n**Elinor Ostrom's 1990** book *Governing the Commons* documented hundreds of cases of long-enduring commons institutions:\n\n- **Swiss alpine pastures.** Communities like Törbel, Switzerland have managed summer pastures cooperatively for 500+ years, with no degradation. The institutional structure exhibits all 8 of Ostrom's principles: clearly defined boundaries (only Törbel residents can use the pasture), congruence (one cow per resident in summer), collective-choice (annual village assembly sets rules), monitoring (residents see each other's herds daily), graduated sanctions (first violation = warning, repeated = fine, persistent = exclusion), conflict resolution (village courts), recognition by Swiss government, nested governance.\n\n- **Japanese coastal fisheries.** Village fisheries communities in Hokkaido have maintained common-property rights over coastal waters for centuries, with sustainable harvests. The institutional features mirror the Swiss case adjusted for fisheries.\n\n- **Spanish irrigation systems (huertas of Valencia).** Communities have shared water in Mediterranean basins for 1000+ years through \"tribunals of waters\" — weekly meetings at the cathedral door where farmers resolve disputes. The system has worked since at least the Moorish period.\n\n- **Philippine forest user groups.** Ostrom documented village-level forest management that sustained forest cover where state-managed forests collapsed.\n\nOstrom's empirical claim: when the 8 design principles are present, commons institutions endure for centuries; when they're absent, the Hardin tragedy unfolds.\n\nThe framework has been applied at industrial scale in modern digital and technical commons:\n\n**Open-source software governance.** The Linux kernel, the Apache foundation, the Cloud Native Computing Foundation, Wikipedia — all are commons that have applied Ostrom-style design (governance councils, contribution rules, code-of-conduct enforcement, conflict resolution). The successful projects exhibit Ostrom's principles; the failed ones typically miss several.\n\n**API rate limiting and quota systems.** Modern cloud providers (AWS, Google Cloud, OpenAI, Anthropic) use Ostrom-style commons design for shared infrastructure: clearly defined tiers (boundaries), congruent quotas (rules match capacity), monitoring (usage dashboards), graduated sanctions (throttling → suspension → ban), appeals processes (conflict resolution).\n\n**Wikipedia governance.** Wikipedia's editorial commons has remained productive for 20+ years despite being entirely volunteer-driven. The institutional structure (administrators, arbitration committee, RFC process, edit-warring sanctions) exhibits most of Ostrom's 8 principles.\n\n**Workplace shared resources.** Modern guidance on meeting hygiene, Slack norms, email discipline, \"Maker vs Manager schedules\" (Paul Graham 2009) is implicitly Ostrom-style: defining boundaries (meeting-free time blocks), congruence (meeting calls match actual coordination needs), monitoring (calendar audits), graduated sanctions (cultural pushback against bad-meeting-callers).\n\n**Cybersecurity (shared internet infrastructure).** The DNS root server system, BGP routing, IP address allocation, certificate authorities — all are commons. The institutional governance (ICANN, IETF, regional internet registries) is broadly Ostrom-structured.\n\n**AI training data commons.** The current AI training-data commons crisis (publishers walling off content; content quality degrading as AI-generated text floods the web) is unfolding in real time as a textbook Hardin tragedy. The Ostrom-style response — institutional design for shared training data, with contribution rules and compensation mechanisms — is being debated at the policy level.\n\nThree operational lessons:\n\n**First, modern technical commons are everywhere.** Anywhere a platform, API, ecosystem, or shared infrastructure has multiple users with individual access, you have a commons. The Hardin dynamics will operate unless Ostrom-style institutional design is applied.\n\n**Second, the privatize-or-regulate binary is usually wrong.** Hardin's 1968 conclusion — privatize or have government regulation — was over-simplified. Ostrom's empirical contribution: institutional design at the user community level is often more effective than either privatization or central regulation. Modern platforms designing API quotas, governance councils, and contribution rules are applying Ostrom's framework whether they know it or not.\n\n**Third, the 8 principles are not optional add-ons; they're load-bearing.** Communities that miss several of Ostrom's 8 principles reliably collapse into Hardin tragedy. The principles are not a checklist of nice-to-haves; they are the structural mechanisms that make collective self-governance work.\n\nFile v1.0.2:skill-card.md\n\n## Description:
\nActivates when a shared resource is degrading through individually rational overuse, then guides the user through commons-structure verification, Ostrom principle auditing, intervention design, and monitoring.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[deciqai](https://clawhub.ai/user/deciqai)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers, operators, policy teams, and organizational leaders use this skill to diagnose commons failures in shared infrastructure, communities, platforms, APIs, workplaces, and policy settings. It helps turn a degradation pattern into a structured governance design with boundaries, monitoring, sanctions, conflict resolution, and review metrics.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill provides conceptual governance guidance that may be incomplete or inaccurate for high-stakes legal, policy, or operational decisions.
\nMitigation: Independently verify factual and policy claims and review recommendations with qualified domain experts before relying on them in high-stakes settings.
\nRisk: Commons framing can be misapplied to resources that are non-rival, fully private, or primarily individual-action problems.
\nMitigation: Use the skill's fit check and verification steps to confirm shared access, rivalry, diffuse responsibility, and a Hardin-style pattern before applying the framework.
\nRisk: Monitoring and sanctions proposals could create privacy, fairness, or legitimacy concerns if implemented without local context.
\nMitigation: Design monitoring, sanctions, and conflict-resolution processes with stakeholder participation, proportionality, appeal paths, and periodic review.
\n\n\n## Reference(s):
\n- [Sources - tragedy-of-the-commons](references/sources.md)
\n- [Method in Action: Hardin 1968 + Ostrom's Empirical Correction + Modern Digital Applications](examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, guidance]
\n**Output Format:** [Markdown with a structured Commons Design template]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Produces commons verification, Ostrom audit findings, intervention recommendations, implementation sequence, metrics, and review cycle.]
\n\n## Skill Version(s):
\n1.0.2 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.1: 5 files, 8832 bytes\n\nFiles: examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md (5592b), references/sources.md (1406b), skill-card.md (2289b), SKILL.md (7708b), _meta.json (141b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: tragedy-of-the-commons\ndescription: >\n Activate when: shared resource is degrading even though no one is doing anything \"wrong\"; team complains about free riders or overuse; designing API quotas, rate limits, or open-source governance; someone says \"everyone is overusing this\" or \"the system worked fine until it got popular\"; evaluating why a platform or community is burning out.\n Do NOT activate when: the resource is fully non-rival (unlimited supply, zero marginal cost); the problem is a purely individual-action issue with no shared resource.\n---\n\n# Tragedy of the Commons\n\n## Overview\n\nWhen a shared resource has individual access but no individual responsibility for preservation, rational users extract private benefit while the cost of overuse is shared — leading to collective degradation. Garrett Hardin named this in 1968; Elinor Ostrom corrected it in 1990 (Nobel 2009): many communities self-govern commons via her 8 design principles without privatization or coercion.\n\nComposes with [`prisoners-dilemma`](../prisoners-dilemma/SKILL.md), [`principal-agent`](../principal-agent/SKILL.md), [`network-effects`](../network-effects/SKILL.md), [`goodharts-law`](../goodharts-law/SKILL.md), [`repeated-games-reputation`](../repeated-games-reputation/SKILL.md).\n\n## When to Use\n\n- Diagnosing why a shared resource is degrading (open-source burnout, API abuse, attention market polarizing)\n- Designing platforms, marketplaces, shared infrastructure, API quotas, or rate limits\n- Designing workplace norms around shared resources (meetings, Slack, email)\n- Evaluating regulatory or policy responses to shared-resource problems\n\n**Not when:** resource is genuinely non-rival; fully private; \"commons\" framing is misapplied to individual-action problems.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete commons case → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line: when a shared resource degrades despite each user acting rationally, you have a commons problem — the answer is institutional design per Ostrom's 8 principles, not just \"privatize\" or \"regulate.\"\n2. Check fit: shared resource + individual extraction + shared cost? If not, different frameworks apply.\n3. Elicit the resource, users, and current rules: What's shared? Who has access? What rules govern use? What's failing?\n> **[WAIT — do not advance until user responds]**\n4. Audit which of Ostrom's 8 principles are present / weak / absent in their situation.\n> **[WAIT — do not advance until user responds]**\n5. Close: name the institutional gaps + propose design applying missing principles + monitoring plan.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Identify:** shared resource · user community · failure mode · current rules.\n**Step 2 — Verify commons structure:** shared access + rivalrous + diffuse responsibility + Hardin pattern (individually rational, collectively destructive). All four yes → commons.\n**Step 3 — Ostrom audit** (mark present / weak / absent): 1 Boundaries · 2 Congruence · 3 Collective-choice · 4 Monitoring · 5 Graduated sanctions · 6 Conflict resolution · 7 Right to organize · 8 Nested enterprises. Weak/absent = design targets.\n**Step 4 — Intervene:** for each weak/absent principle, design a specific fix. Avoid the \"privatize or regulate\" binary — Ostrom's institutional design often outperforms both.\n**Step 5 — Monitor:** sequence · metrics (resource health, sanctions issued) · quarterly review.\n\n## Output Template\n```\nCommons Design: \nStructure: shared resource | boundaries | failure mode | current rules\nVerification: shared Y/N · rivalrous Y/N · diffuse responsibility Y/N · Hardin pattern Y/N\nOstrom audit: [1–8: present/weak/absent]\nIntervention: [per weak/absent principle] · why not privatize · why not pure regulation\nImplementation: sequence · metrics · review cycle\n```\n\n*→ Method in Action: [Hardin 1968 + Ostrom's Empirical Correction + Modern Digital Applications](examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md)*\n\n## Pack: Commons Patterns\n\n| Commons | Failure mode | Ostrom countermeasure |\n|---|---|---|\n| Open-source project | Maintainer burnout | Contribution rules; governance council; sustaining funding |\n| API / cloud infrastructure | Abuse degrades service for all | Tiered quotas; monitoring; graduated sanctions |\n| Slack / meetings | Notification overload | Norms; meeting-free blocks; signal-noise metrics |\n| Fisheries / antibiotic efficacy | Stock collapse / resistance | Quotas; stewardship programs; surveillance |\n| Atmospheric carbon | Climate change | Carbon pricing; international agreements; local action |\n\n## Applying It Well\n\n- Ostrom's 8 principles are load-bearing, not optional: missing several reliably produces Hardin tragedy.\n- Privatization works when exclusion is feasible and transaction costs are low. Regulation works when the regulator has information and legitimacy. Ostrom's self-governance works when users can communicate, monitor, and self-organize — often best for technical commons.\n- Peer monitoring (users see each other's behavior) differs from punitive surveillance; successful commons use the former.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"Commons always fail; we have to privatize\" | Hardin over-stated this. Ostrom's empirical evidence: many commons endure for centuries with the 8 principles. |\n| [D] \"The government must regulate\" | Sometimes. Often community self-governance is faster, cheaper, and more legitimate. |\n| [D] \"Punish free riders; that's enough\" | Graduated sanctions is one of 8 principles. Punishment alone without monitoring, boundaries, etc. doesn't work. |\n| [D] \"Open source means free; we don't owe anything\" | Maintainer labor is a commons; without contribution mechanisms it depletes (xz 2024 was the warning). |\n| [D] \"Our users would never abuse the API\" | The Hardin structure predicts abuse from a substantial fraction regardless of intent. Design accordingly. |\n| [D] \"We don't need formal governance; people are reasonable\" | Even reasonable people benefit from boundaries, monitoring, and conflict resolution. |\n| [D] \"Monitoring is surveillance; we don't do that\" | Ostrom distinguishes cooperative peer-monitoring from punitive surveillance. Successful commons use the former. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Shared resource degrading; rules unclear or unenforced\n- Free-rider complaints but no graduated sanctions exist\n- Users have no voice in rule-setting (Ostrom principle 3 absent)\n- Default response is \"regulate it\" or \"privatize it\" without considering institutional design\n\n## Verification\n\n- [ ] Shared resource and user boundaries specified\n- [ ] Commons structure verified (shared + rivalrous + diffuse responsibility)\n- [ ] Ostrom's 8 principles audited; weak/absent identified\n- [ ] Institutional intervention designed; privatize-or-regulate alternatives addressed\n- [ ] Monitoring metrics and review cycle scheduled\n\n---\n\n*Part of **deciqAI Knowledge Skills** — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.*\n\nFile v1.0.1:_meta.json\n\n{\n \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n \"slug\": \"tragedy-of-the-commons\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1783463667115\n}\n\nFile v1.0.1:references/sources.md\n\n# Sources — tragedy-of-the-commons\n\n> *Primary sources for the [tragedy-of-the-commons](../SKILL.md) skill.*\n\n- Hardin, G. (1968). \"The Tragedy of the Commons.\" *Science*, 162(3859), 1243-1248. The foundational paper.\n- Hardin, G. (1998). \"Extensions of 'The Tragedy of the Commons'.\" *Science*, 280(5364), 682-683. Hardin's update acknowledging Ostrom.\n- Ostrom, E. (1990). *Governing the Commons: The Evolution of Institutions for Collective Action.* Cambridge University Press. ISBN 978-0521405997. The empirical correction.\n- Ostrom, E. (2009). \"A General Framework for Analyzing Sustainability of Social-Ecological Systems.\" *Science*, 325(5939), 419-422. The synthesis.\n- Olson, M. (1965). *The Logic of Collective Action.* Harvard University Press. ISBN 978-0674537514. The collective-action problem foundation.\n- Lloyd, W. F. (1833). *Two Lectures on the Checks to Population.* Oxford University Press. The historical predecessor Hardin cites.\n- Dietz, T., Ostrom, E., & Stern, P. C. (2003). \"The struggle to govern the commons.\" *Science*, 302(5652), 1907-1912. The state-of-the-art summary.\n- Ostrom, E., Burger, J., Field, C. B., Norgaard, R. B., & Policansky, D. (1999). \"Revisiting the commons: Local lessons, global challenges.\" *Science*, 284(5412), 278-282.\n- Buck, S. J. (1998). *The Global Commons: An Introduction.* Island Press. ISBN 978-1559633499. Applied to modern global commons.\n\nFile v1.0.1:examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md\n\n# Method in Action: Hardin 1968 + Ostrom's Empirical Correction + Modern Digital Applications\n\n> *Example for the [tragedy-of-the-commons](../SKILL.md) skill.*\n\nThe Hardin 1968 paper was operationally famous and operationally influential, but its conclusions were over-stated and partially wrong. Hardin himself acknowledged this in a 1998 follow-up paper:\n\n> Hardin, G. (1998). \"Extensions of 'The Tragedy of the Commons'.\" *Science*, 280(5364), 682-683.\n\nHardin's 1998 update acknowledged Ostrom's empirical findings and clarified that his 1968 paper had over-generalized: his analysis applied to *unmanaged* commons, not to commons with established governance institutions. The 1998 paper explicitly cited Ostrom and recommended her institutional approach for managed commons.\n\n**Elinor Ostrom's 1990** book *Governing the Commons* documented hundreds of cases of long-enduring commons institutions:\n\n- **Swiss alpine pastures.** Communities like Törbel, Switzerland have managed summer pastures cooperatively for 500+ years, with no degradation. The institutional structure exhibits all 8 of Ostrom's principles: clearly defined boundaries (only Törbel residents can use the pasture), congruence (one cow per resident in summer), collective-choice (annual village assembly sets rules), monitoring (residents see each other's herds daily), graduated sanctions (first violation = warning, repeated = fine, persistent = exclusion), conflict resolution (village courts), recognition by Swiss government, nested governance.\n\n- **Japanese coastal fisheries.** Village fisheries communities in Hokkaido have maintained common-property rights over coastal waters for centuries, with sustainable harvests. The institutional features mirror the Swiss case adjusted for fisheries.\n\n- **Spanish irrigation systems (huertas of Valencia).** Communities have shared water in Mediterranean basins for 1000+ years through \"tribunals of waters\" — weekly meetings at the cathedral door where farmers resolve disputes. The system has worked since at least the Moorish period.\n\n- **Philippine forest user groups.** Ostrom documented village-level forest management that sustained forest cover where state-managed forests collapsed.\n\nOstrom's empirical claim: when the 8 design principles are present, commons institutions endure for centuries; when they're absent, the Hardin tragedy unfolds.\n\nThe framework has been applied at industrial scale in modern digital and technical commons:\n\n**Open-source software governance.** The Linux kernel, the Apache foundation, the Cloud Native Computing Foundation, Wikipedia — all are commons that have applied Ostrom-style design (governance councils, contribution rules, code-of-conduct enforcement, conflict resolution). The successful projects exhibit Ostrom's principles; the failed ones typically miss several.\n\n**API rate limiting and quota systems.** Modern cloud providers (AWS, Google Cloud, OpenAI, Anthropic) use Ostrom-style commons design for shared infrastructure: clearly defined tiers (boundaries), congruent quotas (rules match capacity), monitoring (usage dashboards), graduated sanctions (throttling → suspension → ban), appeals processes (conflict resolution).\n\n**Wikipedia governance.** Wikipedia's edit\n\nArchive v1.0.0: 5 files, 8845 bytes\n\nFiles: examples/hardin-1968-ostrom-empirical-correction-modern-digital-applications.md (5592b), references/sources.md (1406b), skill-card.md (2306b), SKILL.md (7708b), _meta.json (141b)","readmeExcerpt":"Skill: Tragedy of the Commons Owner: deciqai Summary: Activate when: shared resource is degrading even though no one is doing anything \"wrong\"; team complains about free riders or overuse; designing API quotas,... Tags: latest:1.0.6 Version history: v1.0.6 | 2026-07-16T18:20:00.125Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/tragedy-of-the-commons.json) v1.0.5 | 2026-07-09T11:","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"Commons Design: \nStructure: shared resource | boundaries | failure mode | current rules\nVerification: shared Y/N · rivalrous Y/N · diffuse responsibility Y/N · Hardin pattern Y/N\nOstrom audit: [1–8: present/weak/absent]\nIntervention: [per weak/absent principle] · why not privatize · why not pure regulation\nImplementation: sequence · metrics · review cycle"},{"language":"text","snippet":"Commons Design: \nStructure: shared resource | boundaries | failure mode | current rules\nVerification: shared Y/N · rivalrous Y/N · diffuse responsibility Y/N · Hardin pattern Y/N\nOstrom audit: [1–8: present/weak/absent]\nIntervention: [per weak/absent principle] · why not privatize · why not pure regulation\nImplementation: sequence · metrics · review cycle"},{"language":"text","snippet":"Commons Design: \nStructure: shared resource | boundaries | failure mode | current rules\nVerification: shared Y/N · rivalrous Y/N · diffuse responsibility Y/N · Hardin pattern Y/N\nOstrom audit: [1–8: present/weak/absent]\nIntervention: [per weak/absent principle] · why not privatize · why not pure regulation\nImplementation: sequence · metrics · review cycle"},{"language":"text","snippet":"Commons Design: \nStructure: shared resource | boundaries | failure mode | current rules\nVerification: shared Y/N · rivalrous Y/N · diffuse responsibility Y/N · Hardin pattern Y/N\nOstrom audit: [1–8: present/weak/absent]\nIntervention: [per weak/absent principle] · why not privatize · why not pure regulation\nImplementation: sequence · metrics · review cycle"},{"language":"text","snippet":"Commons Design: \nStructure: shared resource | boundaries | failure mode | current rules\nVerification: shared Y/N · rivalrous Y/N · diffuse responsibility Y/N · Hardin pattern Y/N\nOstrom audit: [1–8: present/weak/absent]\nIntervention: [per weak/absent principle] · why not privatize · why not pure regulation\nImplementation: sequence · metrics · review cycle"},{"language":"text","snippet":"Commons Design: \nStructure: shared resource | boundaries | failure mode | current rules\nVerification: shared Y/N · rivalrous Y/N · diffuse responsibility Y/N · Hardin pattern Y/N\nOstrom audit: [1–8: present/weak/absent]\nIntervention: [per weak/absent principle] · why not privatize · why not pure regulation\nImplementation: sequence · metrics · review cycle"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: tragedy-of-the-commons\ndescription: >\n Activate when: shared resource is degrading even though no one is doing anything \"wrong\"; team complains about free riders or overuse; designing API quotas, rate limits, or open-source governance; someone says \"everyone is overusing this\" or \"the system worked fine until it got popular\"; evaluating why a platform or community is burning out.\n Do NOT activate when: the resource is fully non-rival (unlimited supply, zero marginal cost); the problem is a purely individual-action issue with no shared resource.\n More: deciqai.com/c/tragedy-of-the-commons\n---\n\n# Tragedy of the Commons\n\n## Overview\n\nWhen a shared resource has individual access but no individual responsibility for preservation, rational users extract private benefit while the cost of overuse is shared — leading to collective degradation. Garrett Hardin named this in 1968; Elinor Ostrom corrected it in 1990 (Nobel 2009): many communities self-govern commons via her 8 design principles without privatization or coercion.\n\nComposes with `prisoners-dilemma`, `principal-agent`, `network-effects`, `goodharts-law`, `repeated-games-reputation`.\n\n## When to Use\n\n- Diagnosing why a shared resource is degrading (open-source burnout, API abuse, attention market polarizing)\n- Assessing AI-era shared-resource strain from AI capex and AI-native competition (open web scraped for training data, grid/power capacity, GPU allocation)\n- Designing platforms, marketplaces, shared infrastructure, API quotas, or rate limits\n- Designing workplace norms around shared resources (meetings, Slack, email)\n- Evaluating regulatory or policy responses to shared-resource problems\n\n**Not when:** resource is genuinely non-rival; fully private; \"commons\" framing is misapplied to individual-action problems.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete commons case → run The Process directly.\n- **Coach mode:** user is unfamiliar → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line: when a shared resource degrades despite each user acting rationally, you have a commons problem — the answer is institutional design per Ostrom's 8 principles, not just \"privatize\" or \"regulate.\"\n2. Check fit: shared resource + individual extraction + shared cost? If not, different frameworks apply.\n3. Elicit the resource, users, and current rules: What's shared? Who has access? What rules govern use? What's failing?\n> **[WAIT — do not advance until user responds]**\n4. Audit which of Ostrom's 8 principles are present / weak / absent in their situation.\n> **[WAIT — do not advance until user responds]**\n5. Close: name the institutional gaps + propose design applying missing principles + monitoring plan.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Identify:** shared resource · user community · failure mode · current rules.\n**Step 2 —"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n \"slug\": \"tragedy-of-the-commons\",\n \"version\": \"1.0.6\",\n \"publishedAt\": 1784226000125\n}"},{"path":"references/sources.md","content":"# Sources — tragedy-of-the-commons\n\n> *Primary sources for the [tragedy-of-the-commons](../SKILL.md) skill.*\n\n- Hardin, G. (1968). \"The Tragedy of the Commons.\" *Science*, 162(3859), 1243-1248. The foundational paper.\n- Hardin, G. (1998). \"Extensions of 'The Tragedy of the Commons'.\" *Science*, 280(5364), 682-683. Hardin's update acknowledging Ostrom.\n- Ostrom, E. (1990). *Governing the Commons: The Evolution of Institutions for Collective Action.* Cambridge University Press. ISBN 978-0521405997. The empirical correction.\n- Ostrom, E. (2009). \"A General Framework for Analyzing Sustainability of Social-Ecological Systems.\" *Science*, 325(5939), 419-422. The synthesis.\n- Olson, M. (1965). *The Logic of Collective Action.* Harvard University Press. ISBN 978-0674537514. The collective-action problem foundation.\n- Lloyd, W. F. (1833). *Two Lectures on the Checks to Population.* Oxford University Press. The historical predecessor Hardin cites.\n- Dietz, T., Ostrom, E., & Stern, P. C. (2003). \"The struggle to govern the commons.\" *Science*, 302(5652), 1907-1912. The state-of-the-art summary.\n- Ostrom, E., Burger, J., Field, C. B., Norgaard, R. B., & Policansky, D. (1999). \"Revisiting the commons: Local lessons, global challenges.\" *Science*, 284(5412), 278-282.\n- Buck, S. J. (1998). *The Global Commons: An Introduction.* Island Press. ISBN 978-1559633499. Applied to modern global commons.\n- Kurlansky, M. (1997). *Cod: A Biography of the Fish That Changed the World.* Walker & Company. The Grand Banks collapse narrative.\n- Hutchings, J. A., & Myers, R. A. (1994). \"What can be learned from the collapse of a renewable resource? Atlantic cod, Gadus morhua, of Newfoundland and Labrador.\" *Canadian Journal of Fisheries and Aquatic Sciences*, 51(9), 2126-2146. The scientific post-mortem of the cod collapse.\n- International Energy Agency (2024). *Electricity 2024: Analysis and Forecast to 2026.* IEA, Paris. Widely-cited analysis of rising data-center and AI electricity demand — the 2024–2026 power commons.\n- Reuters / Associated Press reporting (2023–2025) on copyright litigation between publishers and authors and AI developers, on data-center grid strain and ratepayer cost allocation, and on advanced-GPU supply constraints and export controls. Context for the AI-era open-web, power, and GPU commons."},{"path":"examples/ai-era-commons-open-web-power-gpus-2024-2026.md","content":"# Method in Action: The AI-Era Commons — Open Web, Power, and GPUs (2024–2026)\n\n> *Example for the [tragedy-of-the-commons](../SKILL.md) skill.*\n\nThe generative-AI build-out that accelerated through 2024–2025 (and continued into 2026) put three shared resources under simultaneous strain, each closely fitting Hardin's structure: the **open web** (published human content, scraped at scale to train models), **shared electrical grid and power capacity** (drawn on by rapidly growing data centers), and **frontier GPUs / accelerator supply** (a rivalrous input every AI lab competes for). In each, rational individual extraction degrades a resource whose cost of depletion is spread across everyone. This example walks all three through the skill's process, because they illustrate three different Ostrom-audit failure profiles.\n\n**Step 1 — Identify.**\n\n- *Open web.* Shared resource: the corpus of freely published human writing, images, and code. User community: AI labs and crawler operators (extractors) plus the publishers, forums, open-source maintainers, and individual creators who supply the content. Failure mode: the incentive to publish openly erodes as creators see their work absorbed into models that compete with or bypass them, so they paywall, add \"no-AI\" terms, or stop publishing — degrading the very commons the models depend on. Current rules: `robots.txt` (a voluntary, unenforceable convention from the 1990s), site terms of service, and a wave of crawler-blocking tools and licensing deals negotiated site-by-site.\n- *Power/grid.* Shared resource: finite electricity generation and transmission capacity on regional grids. User community: hyperscale data-center operators, other industrial users, and residential ratepayers. Failure mode: concentrated new demand strains interconnection queues and can push costs onto other users. Current rules: utility interconnection processes, tariffs, and grid-operator (e.g., ISO/RTO) planning.\n- *GPUs.* Shared resource: the constrained supply of advanced AI accelerators and the leading-edge fab capacity that makes them. User community: AI labs, cloud providers, enterprises, and researchers. Failure mode: supply concentrates with the largest buyers; smaller labs and academics are priced or crowded out. Current rules: vendor allocation, cloud reservation/quota systems, and export controls.\n\n**Step 2 — Verify commons structure.**\n\n- *Open web.* Shared access ✓ (anyone can crawl). Rivalrous — *partially*: the bytes are non-rival (copying costs nothing), but the **incentive to keep supplying new content is rivalrous and depletable**; unrestrained extraction erodes it. Diffuse responsibility ✓ (no crawler bears the cost of a shrinking open web). Hardin pattern ✓ (each lab rationally scrapes maximally; collectively they can starve future training data). Commons — with the nuance that the depletable stock is the *supply incentive*, not the copies.\n- *Power.* Shared ✓, rivalrous ✓ (a megawatt drawn is unavailable to others),"},{"path":"examples/grand-banks-cod-collapse-and-1992-moratorium.md","content":"# Method in Action: The Grand Banks Cod Collapse and the 1992 Moratorium (1950s–1992)\n\n> *Example for the [tragedy-of-the-commons](../SKILL.md) skill.*\n\nThe northern cod fishery off Newfoundland ran for roughly five centuries — European fleets worked the Grand Banks from the late 1400s onward — and then collapsed within a few decades of industrialization. It is the canonical natural-resource commons tragedy, and it also demonstrates the skill's sharpest lesson: central regulation without Ostrom's institutional structure fails just like an unmanaged commons.\n\n**Step 1 — Identify.** Shared resource: the northern cod stock (Gadus morhua) off Newfoundland and Labrador. User community: Newfoundland inshore fishers (small boats, local knowledge), Canadian offshore trawler companies, and foreign distant-water factory fleets. Failure mode: stock collapse. Current rules (pre-collapse): open international access beyond territorial waters; after Canada's 200-mile exclusive economic zone declaration in 1977, centralized quotas set by the federal Department of Fisheries and Oceans (DFO).\n\n**Step 2 — Verify commons structure.** Shared access: yes — no single actor could exclude others. Rivalrous: yes — every tonne caught is unavailable to everyone else and to the spawning stock. Diffuse responsibility: yes — no fleet bore the cost of its own overfishing; the cost was spread across all users and the future. Hardin pattern: yes — each captain's rational move was to catch more before competitors did. Post-WWII factory trawlers from Europe and the USSR drove reported catches to a historic peak around 800,000 tonnes in 1968, several times the long-run sustainable harvest. All four conditions present: a textbook commons.\n\n**Step 3 — Ostrom audit.** This is the instructive part — Canada *did* regulate after 1977, and the stock still collapsed, because nearly every design principle was weak or absent:\n\n- **1 Boundaries — weak.** The 200-mile zone came only in 1977; foreign fleets kept fishing the \"Nose\" and \"Tail\" of the Banks that lay outside it.\n- **2 Congruence — absent.** DFO quotas rested on offshore survey models that overestimated the stock; harvest rules did not match the resource's actual condition.\n- **3 Collective-choice — absent.** Inshore fishers reported shrinking fish and falling catches through the 1980s; their local knowledge had no channel into quota-setting, and the warnings were dismissed as anecdote.\n- **4 Monitoring — weak.** Discarding, misreporting, and high-grading at sea were widespread and largely unobserved.\n- **5 Graduated sanctions — weak.** Quota violations carried little consequence relative to the profit from cheating.\n- **6 Conflict resolution — absent.** The inshore–offshore dispute over who was destroying the stock festered for a decade with no legitimate forum.\n- **7 Right to organize — absent.** Fishing communities had no recognized authority to set or enforce local rules.\n- **8 Nested enterprises — absent.** A single centralized "}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Activate when: shared resource is degrading even though no one is doing anything \"wrong\"; team complains about free riders or overuse; designing API quotas,... Skill: Tragedy of the Commons Owner: deciqai Summary: Activate when: shared resource is degrading even though no one is doing anything \"wrong\"; team complains about free riders or overuse; designing API quotas,... Tags: latest:1.0.6 Version history: v1.0.6 | 2026-07-16T18:20:00.125Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/tragedy-of-the-commons.json) v1.0.5 | 2026-07-09T11:","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":2053,"uniquenessScore":52,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T04:38:08.246Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T04:38:08.246Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T07:44:41.694Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}