## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `article_bundle` — **LLM article bundle**
Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution.
- **article slug:** `oip-node-c22-commons-institutional-design`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Reference block for Grok/GPT/Gemini. Section §SELF explains the system.
- **read:** https://miscsubjects.com/api/articles/oip-node-c22-commons-institutional-design/bundle?format=markdown

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/oip-node-c22-commons-institutional-design/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/oip-node-c22-commons-institutional-design/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/oip-node-c22-commons-institutional-design/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/oip-node-c22-commons-institutional-design/prompts
- **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node.
- **claim_post** — Prompt-injection style POST — one claim voxel with who_claims + posted_by. · https://miscsubjects.com/api/articles/oip-node-c22-commons-institutional-design/voxels
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

### §STRUCTURE
This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure

### §INTEGRITY
Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you.

### §GAUNTLET
Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted.

*Not medical advice. Tier-honest. Cite claim/source ids.*

---

# miscsubjects article bundle

> Reference bundle for Grok, GPT, Gemini, or a human reader. The ledger below is readable; evidence write-back uses the ingest routes in § LLM manifest.

## MASTHEAD
- **identity:** `oip-node-c22-commons-institutional-design` v3 · content_hash `02090f1938da2fa8…` · thread_head genesis · 5 DIVs
- **thesis (c1):** Groups can sustainably manage shared resources without top-down coercion or full privatization when Ostrom's design principles are met.
  - c2 [human/active] Institutional structure, not resource type, determines commons success.
  - c3 [human/active] Ostrom's eight design principles are clearly defined boundaries, proportional equivalence between benefits and costs, collective-choice arrangements, monitoring
  - c4 [human/active] Ostrom's design principles enable cooperation in repeated games with reputation and reciprocity.
- **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes
- **standing objections:** 0 open → https://miscsubjects.com/api/articles/oip-node-c22-commons-institutional-design/discourse
- **verbs:** read free · challenge/attest open · edit/move/consolidate CAS-gated with a rows:VOXEL_* key
- **reads_next:** https://miscsubjects.com/a/philosophy · https://miscsubjects.com/api/articles/oip-node-c22-commons-institutional-design/discourse · https://miscsubjects.com/api/protocol

## Article
- **slug:** `oip-node-c22-commons-institutional-design`
- **title:** Node C22: Commons / Institutional Design
- **url:** https://miscsubjects.com/a/oip-node-c22-commons-institutional-design
- **register:** oip_protocol
- **updated:** 2026-07-17T02:36:22.909Z
- **tags:** philosophy, oip, convergence-catalogue, node, systems-theory

## Body

# Node C22: Commons / Institutional Design

C22 — Commons / Institutional Design
{
  "id": "C22",
  "claim": "Groups can sustainably manage shared resources without top-down coercion or full privatization, when specific design principles (Ostrom's rules) are met; institutional structure, not resource type, determines commons success.",
  "domain": ["economics", "political science", "law", "ecology", "game theory"],
  "pattern": ["commons", "institutional_design", "collective_action", "self_governance", "polycentricity"],
  "mechanism": "Ostrom's eight design principles: (1) clearly defined boundaries, (2) proportional equivalence between benefits and costs, (3) collective-choice arrangements, (4) monitoring, (5) graduated sanctions, (6) conflict-resolution mechanisms, (7) minimal recognition of rights to organize, (8) nested enterprises for larger systems. These principles enable cooperation in repeated games with reputation and reciprocity.",
  "scale": "group → institution",
  "claim_tier": "T1",
  "sources": [
    "Ostrom, E. (1990). Governing the Commons: The Evolution of Institutions for Collective Action. Cambridge.",
    "Ostrom, E. (2009). 'Beyond Markets and States: Polycentric Governance of Complex Economic Systems.' Nobel Lecture.",
    "Axelrod, R. (1984). The Evolution of Cooperation. Basic Books.",
    "Hardin, G. (1968). 'The Tragedy of the Commons.' Science, 162, 1243-1248. [The problem statement.]"
  ],
  "dual": "Tragedy of the commons — open-access resources depleted by uncoordinated rational actors; captured institution — common resource controlled by a narrow group for private benefit.",
  "falsifier": "Ostrom's design principles systematically failing to predict commons outcomes — cases where all eight principles are met yet the commons fails, or where none are met yet it succeeds sustainably.",
  "rival_frame": "Commons success is exceptional. Most common-pool resources require either centralized state management or privatization (Hardin's original claim). Ostrom's cases are small-scale, homogeneous communities that do not scale to modern complex societies. Her principles are post-hoc descriptive, not predictive.",
  "independence_check": "MODERATE-HIGH. Hardin (biology, UCSB, 1968) stated the tragedy as a general principle. Axelrod (political science, Michigan, 1984) derived cooperation from iterated Prisoner's Dilemma independently. Ostrom (political science, Indiana, 1990) developed her principles from extensive fieldwork across fisheries, irrigation systems, and forests worldwide. Axelrod and Ostrom were aware of each other's work (partial lineage), but the fieldwork findings were independent of game theory.",
  "pattern_type": "social",
  "maps_to_axiom": ["A4", "A3"]
}

---

## Corpus map
- Same node, other planes: [Encyclopedia C22](/a/convergence-encyclopedia-c22) · [Inventory invariant](/a/oip-invariant-19-319-commons-institutional-design-the-social-scale-grain)
- Catalogue hub: [Public Article](/a/oip-convergence-public-article) · [Schema](/a/oip-convergence-schema)

## Claims (4)

- **c1** [human w=0.8] Groups can sustainably manage shared resources without top-down coercion or full privatization when Ostrom's design principles are met.
- **c2** [human w=0.8] Institutional structure, not resource type, determines commons success.
- **c3** [human w=0.8] Ostrom's eight design principles are clearly defined boundaries, proportional equivalence between benefits and costs, collective-choice arrangements, monitoring, graduated sanctions, conflict-resolution mechanisms, minimal recognition of rights to organize, and nested enterprises for larger systems.
- **c4** [human w=0.8] Ostrom's design principles enable cooperation in repeated games with reputation and reciprocity.

## Voxel graph (4 atoms · 0 edges)
- full graph: https://miscsubjects.com/api/articles/oip-node-c22-commons-institutional-design/voxels

## Article constitution

- full: https://miscsubjects.com/api/articles/constitution

## Source ledger (0)
- chain valid: yes · head: `genesis`

## Provenance (5 model passes)
- chain valid: yes · head: `c3d396d5bb120433`

- edit · claude-fable-5 · 2026-07-04T04:34 · hash `b6e5c4db1530`
- edit · claude-fable-5 · 2026-07-04T05:02 · hash `cc59308e46ca`
- atomize · grok/grok-4.3 · 2026-07-07T07:52 · hash `b489d63172d1`
- score · scorer · 2026-07-07T07:52 · hash `6f3134f2c26b`
- voxel_divide · owner · 2026-07-17T02:36 · hash `c3d396d5bb12`

## Question graph
- questions: 0 · evidence ingests: 0

## LLM manifest — how to communicate with this ledger

- system map: https://miscsubjects.com/api/articles/system-map?format=markdown
- topology (ranked): https://miscsubjects.com/api/articles/oip-node-c22-commons-institutional-design/topology
- ingest: POST https://miscsubjects.com/api/protocol/ingest
- claim: POST https://miscsubjects.com/api/protocol/claim

### Quick actions for this article
- **Read live:** https://miscsubjects.com/api/articles/oip-node-c22-commons-institutional-design/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"oip-node-c22-commons-institutional-design","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest oip-node-c22-commons-institutional-design|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim oip-node-c22-commons-institutional-design|tier|assertion`
- **iMessage ask:** `oip-node-c22-commons-institutional-design|your question`
- **System map:** https://miscsubjects.com/api/articles/system-map?format=markdown


---

## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `system_map` — **System map**
Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **article slug:** `oip-node-c22-commons-institutional-design`
- **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest
- **how to use:** Root index of every miscsubjects article-ledger feature. Start here if you have zero context.
- **read:** https://miscsubjects.com/api/articles/system-map

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/oip-node-c22-commons-institutional-design/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **constitution** — Binding rules: required article slots, claim/source rules, ontology anti-sprawl. · https://miscsubjects.com/api/articles/constitution
- **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest
- **oip_article_hub** — Public article-native Object Invocation Protocol docs: /a/oip root, generated shelf/system/capability articles, machine bundles, token boundary, and receipt loop. · https://miscsubjects.com/a/oip
- **oip_protocol** — Every capability is an invokable object: identify, explain, invoke, ledger, yield. · https://miscsubjects.com/a/oip
- **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/oip-node-c22-commons-institutional-design/bundle?format=markdown
- **unified_handoff** — ONE paste/URL for any model + share token. Same self-explaining pattern as article bundle, but whole build. · https://miscsubjects.com/api/handoff?format=markdown

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

### §STRUCTURE
This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure

### §INTEGRITY
Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you.

### §GAUNTLET
Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted.

*Not medical advice. Tier-honest. Cite claim/source ids.*