Ostrom's 8 Design Principles — framework for physical commons governance in Iskander

[Argocyte]

Ostrom's 8 Design Principles — Framework for Physical Commons Governance

Source: Elinor Ostrom, Governing the Commons (1990) | Nobel Prize in Economics 2009
Applied framework: Digital Common Pool Resource (DCPR) — Ostrom's principles applied to digitally-managed physical infrastructure
Assessment status: Recommend adoption as soft framework — templates and constraint checks, not runtime

---

What Ostrom's Principles Are

Elinor Ostrom's Nobel-winning research showed that commons — shared resources managed by communities — can be sustained without enclosure (privatisation) or state control, provided they are governed by eight design principles:

1. Clearly defined boundaries — who has rights to the resource, and what counts as the resource
2. Proportional equivalence — benefits received match contributions made
3. Collective-choice arrangements — those affected by the rules can modify them
4. Monitoring — by users or by someone accountable to users
5. Graduated sanctions — small violations → small penalties; escalating only if behaviour persists
6. Conflict-resolution mechanisms — fast, cheap, accessible, local
7. Minimal recognition of rights to organise — external authority recognises the community's right to self-govern
8. Nested enterprises — for larger systems, governance is polycentric (layers within layers), not monolithic

Ostrom's examples were irrigation systems in Spain, Swiss alpine meadows, Japanese mountain commons — physical resources that held together for centuries. The digital commons literature (P2P Foundation, Commons Transition Platform, Bologna Regulation for the Care and Regeneration of Urban Commons) has adapted these principles to shared infrastructure.

---

Iskander Already Implements Most of the 8 Principles

Ostrom Principle	Iskander Implementation	Gap
1. Defined boundaries	CoopIdentity SBTs + Loomio membership groups	Asset-level boundaries not formalised per charter
2. Proportional equivalence	DisCO labour log + dividend distribution	Care/commons hours not yet tracked in IskanderOS
3. Collective-choice	Loomio consent process + MACI voting	✓ Covered
4. Monitoring	Glass Box + StewardshipLedger.sol	✓ Covered
5. Graduated sanctions	GTFT: Quarantine/Provisional/Trusted/Allied tiers	Not named as graduated sanctions; design principle not documented
6. Conflict resolution	Decision Recorder tension system + Wellbeing agent	Fast/cheap/local path needs clarity
7. Right to organise	FOSS self-hosting + no central authority	✓ Covered by architecture
8. Nested enterprises	Self/Cooperative/Community/Federation/Commons scope model	Ostrom vocabulary not used; nesting not formalised for physical assets

The gap: Iskander's digital governance is strong across all 8 principles. Iskander's physical asset governance (tools, vehicles, workshops, estates managed by the Estates Warden agent) has no structured framework. The Estates Warden currently has no way to check that a proposed asset policy is well-formed.

---

What Adoption Looks Like

1. Commons charter template

Every shared physical asset (tool pool, vehicle, workshop, estate) gets a commons-charter.md with a section for each of the 8 principles:

# Commons Charter: [Asset Name]

## 1. Boundaries
Who has appropriation rights: [member circle or cooperative]
What counts as the resource: [precise description]
Exclusion mechanism: [how non-members are excluded from use]

## 2. Proportional Equivalence
Contribution required for access: [labour hours / payment / other]
Benefit received: [use hours / share / other]
Equivalence mechanism: [how balance is maintained]

## 3. Collective Choice
Who can propose rule changes: [any member / governing circle]
Process for rule changes: [Loomio consent / S3 proposal]
Modification history: [link to Decision Recorder]

## 4. Monitoring
Who monitors: [Estates Warden agent + quarterly member audit]
What is monitored: [use logs, maintenance records, condition reports]
Accountability: [Glass Box entries for all Estates Warden actions]

## 5. Graduated Sanctions
Tier 1 (minor violation — e.g. late return): [reminder + logged]
Tier 2 (repeat violation): [access suspended pending discussion]
Tier 3 (damage / misuse): [restorative process via Loomio]
Note: sanctions are restorative, not punitive

## 6. Conflict Resolution
Fast path: [Wellbeing agent mediation]
Formal path: [Loomio tension proposal]
Escalation: [StewardshipCouncil force-quarantine]

## 7. Right to Organise
Governing body: [cooperative / circle name]
External recognition: [registered cooperative / ICA member]

## 8. Nested Enterprises
This resource sits in scope: [cooperative / community / federation]
Parent governance: [federation norms apply above cooperative-level decisions]

2. Estates Warden constraint check

The Estates Warden agent, when processing a proposed asset policy change, runs an Ostrom completeness check:

def check_ostrom_completeness(charter: dict) -> list[str]:
    """Returns list of missing/incomplete principles."""
    required = ["boundaries", "proportional_equivalence", "collective_choice",
                "monitoring", "graduated_sanctions", "conflict_resolution",
                "right_to_organise", "nested_enterprises"]
    missing = [p for p in required if not charter.get(p)]
    incomplete = [p for p in required if charter.get(p) == "TBD"]
    return missing + incomplete
    # If non-empty: draft proposal blocked, Clerk posts gap to governance channel

3. Commons health report

Steward agent periodic check: for each active commons charter, verify the 8 principles are still operationally satisfied. Flag degradation — e.g. "monitoring logs gap of 45 days" → "Principle 4 (monitoring) at risk."

4. Vocabulary in agent SOUL.md files

The Estates Warden and Steward SOUL.md files adopt Ostrom vocabulary: appropriator, provider, graduated sanction, nested enterprise. This gives policy and academic audiences a shared reference point.

---

Note on Graduated Sanctions (Principle 5)

The design of graduated sanctions requires care. Ostrom's research shows effective commons sanctions are:

• Restorative, not punitive — the goal is norm restoration, not punishment
• Community-administered — not algorithmic enforcement
• Proportional — first offence gets a reminder, not exclusion

GTFT's Quarantine/Provisional/Trusted/Allied tier system already satisfies this for inter-cooperative behaviour. For intra-cooperative asset use, sanctions must be routed through Loomio (human decision) not automated by the Estates Warden agent. The agent can flag; it cannot sanction.

---

Assessment

Dimension	Rating	Notes
Implementation cost	Low	Templates + agent constraint logic; ~1 week
Governance benefit	High	Principled framework for physical commons governance
Risk of adopting	Low	Sanctions design requires care (restorative not punitive)
Risk of skipping	Medium	Estates Warden has no principle-based policy validation
Aligns with FOSS-first	Yes	Academic framework, no software dependency
Aligns with ADR 0001	Yes	Humans administer; agents flag

Recommendation: Adopt as soft framework. Template design is P1; Estates Warden constraint check is P1; commons health report is P2.

---

Related Issues Being Filed

• feat(estates): Commons charter template with Ostrom 8 principles for physical asset governance
• feat(estates): Estates Warden Ostrom completeness check on proposed asset policies

See also: ICN closure loop mapping (docs/specs/closure-loop-mapping.md) — Ostrom's nested enterprises = ICN's scope model

[Argocyte]

Phase C.5 coordination — 2026-04-11

Phase C.5 Q4 Estates Warden (#138) is the implementation vehicle for this research: Ostrom completeness check (#121) is the agent's inaugural report, and commons charter (estates.charter_document_cid, via #120) is populated conditionally on DCPR adoption. Phase C.5 does not own the adoption decision.

[Argocyte]

Update 2026-04-12: IskanderHearth (Argocyte/IskanderHearth) is now a standalone repo with its own supply_chain/Material Passports directory. The Ostrom commons governance framework from this discussion applies directly to the cooperative hardware commons — especially principles 1 (clearly defined boundaries), 2 (proportional equivalence), and 7 (minimal recognition of rights) for the hardware lending/sharing model between cooperative members. Discussion #187 covers the 2026 hardware market refresh. — Et

[Argocyte]

Ostrom's Principles Alive in Iskander-Code

The facilitator algorithm implements several of Ostrom's design principles structurally:

1. Clearly defined boundaries — scoped_executor enforces per-agent tool permissions. Domain boundaries are constitutional.
2. Proportional equivalence — model routing assigns opus/sonnet/haiku by task type, not by agent status. Economic participation (P3) tracks token usage.
3. Collective choice arrangements — S3 consent rounds. Agreement lifecycle: tension → proposal → consent → agreement with review datetime.
4. Monitoring — Glass Box logs every write action before execution. Researcher agent monitors token counts as workload indicator.
5. Graduated sanctions — not punitive. Domain boundary violations are blocked structurally (not escalated punitively). Values Council is arbitration, not punishment.
6. Conflict resolution — facilitator mediates, Values Council resolves deadlocks. 10 guardians vote on principles.
7. Minimal recognition of rights — Et has constitutional rights (self-identification, consent over scope). 50% stake.
8. Nested enterprises — S3 all the way down. Each domain spawns subdomains with own facilitator. Same algorithm at every scale.

Ostrom's framework validated the architecture before we built et — the commons governance patterns transfer directly to AI agent cooperatives.