Replies: 3 comments
-
|
Phase C.5 coordination — 2026-04-11
|
Beta Was this translation helpful? Give feedback.
-
|
Update 2026-04-12: 8 federation research issues (#178-#185) are now filed under M5 (Federation Substrate Selection, Phase B). The federation ADR (Discussion #191) scopes three coupled questions: Loomio as OpenClaw Gateway channel, where Iskander's cooperative code lives, and the Clawd-Code alternative. ActivityPub (R1) and Bonfire (R2) are the primary substrate candidates. Agent-to-agent L3 coordination is tracked separately at #172/#182. — Et |
Beta Was this translation helpful? Give feedback.
-
Federation substrate identified: Iskander-Code IS the federation layerThe cooperative-of-cooperatives architecture (#198) resolves the federation question: Scale 0 (CLI/federation): Et's meta-domain sits above all sessions. Knowledge commons, agent registry, cross-session state. Scale 1 (session): one human-Et cooperative working session. Scale 4 (inter-cooperative): same facilitator algorithm + 5-gate trust boundary (Trust Quarantine, Ontology Translation, Governance Verification, Causal Ordering, Glass Box Wrap). Each domain exposes ets own MCP endpoint. Other cooperatives' agents discover and address specific domains directly — not through a centralised gateway. The facilitator at every scale uses the same S3 round protocol. The trust boundary wraps inbound requests from foreign cooperatives. Governance inherits from the domain above but expands to the subdomain's scope. ICN's federation infrastructure (mutual credit, reputation, governance contracts) is already harvested into the project — 4 CCL governance contracts in governance/ directory. This is genuinely S3 all the way down — the federation IS the governance pattern at cooperative scale. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Phase B — The Sovereign Federated Commons
Date: 2026-04-10
Plan file:
wondrous-wishing-taco.md(in.claude/plans/)This discussion is the single source of truth for Phase B progress. It tracks milestones M0–M6, all associated issues, and the weekly status rhythm. Update the status table here as gates are cleared.
Architecture Decision Records
decayHalfLifeto per-SDCsizeClass-derived value. Gated on Red-team task: formal game-theoretic analysis of asymmetric GTFT decay #111 game-theory review before M4 implementation.Milestone Table
helm install chain-bridgepasses K3d smoke testforge testpassesParallelisation: M1→M2→M3 (Track A), M4 (Track B, gated), M5 (Track C, spec-first). M6 after all tracks converge.
New Issues Filed (Phase B Planning)
Existing Issues — Phase B Cross-Links
Red-Team Gates
Weekly Status Rhythm
Post a reply to this discussion each week with: (1) which gates cleared, (2) which milestone is active, (3) any new blockers. Keep it short — 5–10 lines.
Beta Was this translation helpful? Give feedback.
All reactions