miscsubjectsAI governance
Evidence review · grain

COMMONS / INSTITUTIONAL DESIGN

bundle · json · system map · manifest

Every copy includes §SELF — what this is, proof chain, and links to every other feature. No context required.

§SELF — this page explains the system
## §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:** `human_page` — **Human article page**
Rendered article with claims, sources, copy widgets, ask prompts.
- **article slug:** `convergence-c22`
- **contains:** rendered article, copy widgets, claims, sources, ask prompts
- **how to use:** Use Copy for LLM or Copy system map — both paste without context.
- **read:** https://miscsubjects.com/a/convergence-c22

### 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/convergence-c22/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)
- **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/convergence-c22/bundle?format=markdown
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/convergence-c22/prompts
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/convergence-c22/topology

### 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.*

System notes

Institutional design determines commons success; resource type does not.

Hardin's state-or-privatization dichotomy for commons governance is false; self-governing institutions can and do emerge without centralized coercion.

Ostrom's eight design principles are operational predictors of commons survival: clear boundaries, cost-benefit matching, user participation, monitoring, graduated sanctions, conflict resolution, minimal recognition rights, and nested governance.

Axelrod's tit-for-tat tournament and Ostrom's fieldwork converge on the same mechanism: cooperation survives when rules make defection more expensive than cooperation.

Scale is the hardest limit to Ostrom's principles: they work in small, homogeneous, face-to-face groups but fail at global scale where boundaries, monitoring, and graduated sanctions are impossible.

Evidence · 5 sources · swipe →chain · verify chain · provenance
Evidence ledger 7 · tier-ranked · API
system
Institutional design determines commons success; resource type does not.
sources: ostrom-1990
system
Hardin's state-or-privatization dichotomy for commons governance is false; self-governing institutions can and do emerge without centralized coercion.
sources: ostrom-1990
system
Ostrom's eight design principles are operational predictors of commons survival: clear boundaries, cost-benefit matching, user participation, monitoring, graduated sanctions, conflict resolution, minimal recognition rights, and nested governance.
sources: ostrom-1990
system
Axelrod's tit-for-tat tournament and Ostrom's fieldwork converge on the same mechanism: cooperation survives when rules make defection more expensive than cooperation.
system
Scale is the hardest limit to Ostrom's principles: they work in small, homogeneous, face-to-face groups but fail at global scale where boundaries, monitoring, and graduated sanctions are impossible.
sources: ostrom-1990
2 more ranked claims
speculative0.60
Darwinian selection operates on institutional rules: groups with good rules outcompete groups with bad rules, and rules replicate across neighboring groups through institutional evolution.
sources: darwin-1859
speculative0.55
Cybernetic feedback and Ashby's law of requisite variety apply to commons governance: monitoring and sanctions are feedback loops, and institutional design must generate regulatory variety matching environmental complexity.
Ask this article · 8 suggested prompts

Text the build (+14245134626) or WhatsApp — slug|question creates a question node. Paste evidence with ingest slug|q:NODE_ID|your paste.

What does the ledger say about this (system tier): "Institutional design determines commons success; resource type does not."?
ask convergence-c22 claim c1 · paste includes §SELF
What does the ledger say about this (system tier): "Hardin's state-or-privatization dichotomy for commons governance is false; self-governing institutions can and do emerge without centralized…"?
ask convergence-c22 claim c2 · paste includes §SELF
What does the ledger say about this (system tier): "Ostrom's eight design principles are operational predictors of commons survival: clear boundaries, cost-benefit matching, user participation…"?
ask convergence-c22 claim c3 · paste includes §SELF
What does the ledger say about this (system tier): "Axelrod's tit-for-tat tournament and Ostrom's fieldwork converge on the same mechanism: cooperation survives when rules make defection more …"?
ask convergence-c22 claim c4 · paste includes §SELF
What does the ledger say about this (system tier): "Scale is the hardest limit to Ostrom's principles: they work in small, homogeneous, face-to-face groups but fail at global scale where bound…"?
ask convergence-c22 claim c6 · paste includes §SELF
What does the ledger say about this (speculative tier): "Darwinian selection operates on institutional rules: groups with good rules outcompete groups with bad rules, and rules replicate across nei…"?
ask convergence-c22 claim c5 · paste includes §SELF
What can you answer from your catalogue about COMMONS / INSTITUTIONAL DESIGN — and what remains open or unverified?
ask convergence-c22 gaps · paste includes §SELF
What are the strongest objections or counter-evidence on record against COMMONS / INSTITUTIONAL DESIGN?
ask convergence-c22 objections · paste includes §SELF
convergence-c22 · posted 2026-07-04 · updated 2026-07-17 · 5 prior revisions · owner
Ledger API & provenance
Provenance · 1 model pass · tokens/cost unrecorded · 1 model
chain head 59c2a177353f90b9
voxel_divide owner · 2026-07-17 02:35 · tokens unrecorded · 59c2a177353f
verify chain →
Live ledger · 49 payloads · 2 turns
recent activity · inspect
JCI_CLASSIFY jci · HTTP 200 · 2026-07-28 20:49
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 20:49
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 20:25
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 19:08
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 15:29
JCI_TRAFFIC jci · HTTP 200 · 2026-07-28 15:29
view full ledger & cards →
REST + ledger
read GET /api/articles/convergence-c22 · GET /api/articles/convergence-c22?format=post (the editable body)
create/replace POST /api/articles/convergence-c22 · PUT /api/articles/convergence-c22 (replace, keeps revision) · PATCH /api/articles/convergence-c22 (merge)
delete DELETE /api/articles/convergence-c22
writes need header x-terminal-key
LLM bundle GET /api/articles/convergence-c22/bundle?format=markdown — body + claims + sources + provenance + manifest
post claim POST /api/protocol/claim · iMessage claim convergence-c22|tier|assertion
system map GET /api/articles/system-map?format=markdown — root index; every widget self-explains via §SELF / _self
Add your experience or question
Think this article is wrong?
Dispute this article in Claim Audit →