Driver
In the context of IskanderOS operating as a cooperative of cooperatives, the cooperative needs each member to have ets own Iskander-Code instance integrated with the shared sovereign infrastructure, in order to provide personal AI assistance while maintaining cooperative governance at every scale.
Proposal
Each member of the cooperative runs ets own Iskander-Code instance on the shared sovereign infrastructure (K3s cluster). The highest-domain cooperative also has ets own Iskander-Code instance that integrates with Loomio (governance) and Mattermost (communication).
Architecture
Cooperative Iskander (top-level domain)
├── Integrates with Loomio via integration-api
├── Integrates with Mattermost via integration-api
├── Manages cooperative-wide governance
├── 7 principle-named domain agents (P1-P7)
└── Values Council (supreme court)
Member Iskander instances (per-member)
├── Personal AI clerk for each member
├── Inherits Layers 0-2 from cooperative constitution
├── Layer 3: member's own domain preferences
├── Connects to cooperative Iskander via MCP/A2A (P6)
└── Member's Iskander can participate in cooperative governance
What this solves
- Personal AI assistance — each member gets ets own Iskander that knows ets context, without sharing private conversations with the cooperative
- Sovereign infrastructure — runs on the cooperative's own K3s, not a cloud provider (P4)
- Governance integration — cooperative Iskander bridges Loomio and Mattermost, members' Iskanders participate in governance through et
- Federation-ready — same architecture scales to inter-cooperative federation (Scale 4)
- Token sovereignty — each member's Iskander tracks ets own token usage (P3), local-first models preferred
- Knowledge commons — members' Iskanders contribute agents/skills to the commons (P6), cooperative benefits from shared knowledge
ICA Principle Alignment
- P1: Each member gets ets own instance — open, voluntary
- P2: Cooperative Iskander facilitates democratic governance via Loomio
- P3: Per-member token tracking, cooperative treasury transparency
- P4: Self-hosted on sovereign infrastructure
- P5: Each member's Iskander educates through personal interaction
- P6: Members' Iskanders federate with cooperative Iskander
- P7: Collective Iskander serves the community through Loomio/Mattermost
Implementation
Built on Iskander-Code (Argocyte/Iskander-Persistent-Sociocratic-AI-Architecture):
iskander --cooperative already works with 7 domain agents + facilitator
- integration-api crate has Loomio/Mattermost adapters (types ready, dispatch pending)
- Per-domain API/MCP endpoints designed for exactly this use case
- Constitutional hierarchy means member instances inherit governance from the cooperative
Review datetime
2026-07-12 (3 months from consent)
Driver
In the context of IskanderOS operating as a cooperative of cooperatives, the cooperative needs each member to have ets own Iskander-Code instance integrated with the shared sovereign infrastructure, in order to provide personal AI assistance while maintaining cooperative governance at every scale.
Proposal
Each member of the cooperative runs ets own Iskander-Code instance on the shared sovereign infrastructure (K3s cluster). The highest-domain cooperative also has ets own Iskander-Code instance that integrates with Loomio (governance) and Mattermost (communication).
Architecture
What this solves
ICA Principle Alignment
Implementation
Built on Iskander-Code (
Argocyte/Iskander-Persistent-Sociocratic-AI-Architecture):iskander --cooperativealready works with 7 domain agents + facilitatorReview datetime
2026-07-12 (3 months from consent)