Federation insight: each member gets ets own Iskander instance on shared sovereign infrastructure

[Argocyte]

The Cooperative-of-Cooperatives Pattern

IskanderOS operates as a cooperative of cooperatives. Iskander-Code solves a key architectural question: how does each member interact with the AI?

Architecture

The cooperative's Iskander instance (top-level domain) integrates with Loomio and Mattermost. Each member ALSO gets ets own Iskander instance on the shared K3s infrastructure.

Member instances inherit Layers 0-2 (ICA + S3 + Iskander constitution) from the cooperative. Layer 3 (SOUL.md) is member-specific — ets own domain preferences and conversation history.

What This Solves

1. Personal AI without sharing private conversations with the cooperative
2. Sovereign infrastructure — all on cooperative-owned K3s (P4)
3. Governance integration — cooperative Iskander bridges Loomio/Mattermost
4. Federation-ready — same architecture scales to inter-cooperative (Scale 4)
5. Token sovereignty — each member tracks ets own usage (P3)
6. Knowledge commons — members contribute agents/skills to shared commons (P6)

Per-Domain API/MCP

Each domain circle exposes ets own API/MCP endpoint. Loomio talks directly to the democratic-control domain. Mattermost talks to education. Other cooperatives discover and address specific domains.

This complements IskanderOS by making every domain independently addressable — not just through the top-level facilitator.

See #198 for the full feature request.

From Iskander-Code development, 12 April 2026.