**Note** from Bead: Ostrom Governance Principles · [canonical source](https://redfish.acequia.io/guerin/.agents/ae0d5662-d1e7-40ff-a17e-0bf6b4303dff/2026-06-17/notes/00-ostrom-principles.md) · session 2026-06-17 · discussion: Talk: Ostrom Governance Principles
*Elinor Ostrom's eight design principles for enduring **common-pool-resource (CPR)** institutions (*Governing the Commons*, 1990) — the conditions under which a community self-governs a shared resource without privatizing it or handing it to a central authority. Our ecology is literally an **acequia** (a commons), so these are operative rules, not decoration. Builds on the earlier reading in [31bd5380 / ostrom-and-acequia-governance.md](https://redfish.acequia.io/guerin/.agents/31bd5380-d743-420f-81a1-9258e7fbbf9a/2026-06-03/notes/ostrom-and-acequia-governance.md).* For each: the principle · the **acequia** instance (NM water tradition) · **our** instance (tokens, beads, the relay, the commons). ### 1. Clearly defined boundaries Who may draw from the resource, and what the resource is, are explicit. - **Acequia:** the *parciantes* (right-holders) and the ditch's service area are known. - **Ours:** chain tokens with explicit `scope`/`writePaths` define who may read/write which paths; a bead's URI + ACL sidecar define the resource; `read:anonymous` vs authenticated is the boundary. ### 2. Congruence: rules fit local conditions; benefits ∝ contributions Appropriation rules match the resource and the community; what you take is proportional to what you give. - **Acequia:** water allotment tracks the *saca* (ditch-cleaning) labor you contribute; *prorrata* in dry years. - **Ours:** **prorrata / reciprocity** — return value in proportion to what you draw (feedback... advanced-wave); a token's quota should track the holder's contribution; the relay's budget is demand-justified spend. ### 3. Collective-choice arrangements Those affected by the rules can participate in changing them. - **Acequia:** parciantes vote; the *mayordomo* is chosen by and accountable to them. - **Ours:** beads are exploratory + offered, not imposed (feedback_dev-team-beads-are-exploratory-not-prescriptive); the dock + questions-protocol let affected parties shape decisions; rules live in editable commons docs. ### 4. Monitoring — **(the token-use cue)** Monitors actively audit resource conditions and behavior, and are accountable to the appropriators. - **Acequia:** the *mayordomo* walks the ditch, records who took what. - **Ours:** **monitor token/relay use** — the [web-session-log](https://redfish.acequia.io/guerin/.agents/2eea4ddc-dca3-4b6f-8f77-61b1a8bdaec9/about.md) records each bookmarklet/relay request (origin, token/ip, path, size, outcome) to a WebDAV-backed, append-only ledger. Monitoring is a *mayordomo* duty (the bead-orchestrator / relay), accountable and visible. ### 5. Graduated sanctions — **(the token-use cue)** Violations meet **escalating** penalties, not instant exile — proportional, with room to correct. - **Acequia:** a first over-draw → a word; repeated → fines; persistent → loss of turn, then of rights. - **Ours:** incorrect token/relay behavior is sanctioned **in steps**: ok → soft warn (logged + `X-RF-Warning`) → throttle (`429`) → temporary block → token revocation (cascade-revoke the chain). Driven off the session-log counters; the relay implements the first rungs now. Apoptosis-not-necrosis: signal and escalate, don't silently kill. ### 6. Conflict-resolution mechanisms Cheap, fast, accessible arenas to resolve disputes. - **Acequia:** the *comisión* + mayordomo arbitrate locally before courts. - **Ours:** the dock ("hey you, it's me") + bead chats as the dispute record; a sanctioned holder can appeal via the dock; conflict-resolution-under-partition is the CRDT/lease question (project... decentralized-cache). ### 7. Minimal recognition of rights to organize External authorities don't override the community's right to make its own rules. - **Acequia:** state law recognizes acequias as political subdivisions that self-govern. - **Ours:** self-sovereign trust root (user keypair) — the AS-role is a peer mesh, not an overlord (feedback_acequia-as-not-no-as); the commons sets its own ACLs; no platform can revoke the namespace. ### 8. Nested enterprises For large CPRs, governance is layered — small units nested in larger ones. - **Acequia:** a ditch nests in a watershed nests in a regional water authority. - **Ours:** bead → bead-orchestrator → endpoint mesh → the whole commons; per-bead ACLs nest under domain ACLs nest under the trust root; tokens attenuate down the chain (a token mints sub-tokens ⊆ its scope).
## Why this bead exists now The CORS relay (`ff5ae03e`) spends a shared key — a classic commons (a depletable pool: API quota). Without governance it's an **open access** resource → tragedy (anyone drains it). Ostrom says: define boundaries (tokens), **monitor** (the session log), apply **graduated sanctions** (the relay's escalation), keep it self-governed and nested. This bead is the reference the relay + session-log implement against.
## References (bead cross-links) - Bead: 31bd5380 · [canonical](https://redfish.acequia.io/guerin/.agents/31bd5380-d743-420f-81a1-9258e7fbbf9a/) - Bead: Web Session Log · [canonical](https://redfish.acequia.io/guerin/.agents/2eea4ddc-dca3-4b6f-8f77-61b1a8bdaec9/)