OpenKO
Phase 0 Complete · Protocol Scaffold

Coordinating humans
and intelligence openly.

OpenKO is a decentralized coordination protocol for missions, services, and governance — where every node is simultaneously a user, worker, provider, and governor.

OpenKO
Coordination layer
missions treasury reputation governance
Exosphere
Runtime layer — executes trusted capsules and enforces capabilities
capsules DID capabilities ZPU
Linux / Host OS
Foundation
cgroups namespaces seccomp

Real-world coordination

What does OpenKO
actually look like?

Not platforms. Not apps. Coordination that belongs to the people doing the work.

🏘️
A village funds a road
Residents post a mission. Contributors — surveyors, laborers, equipment providers — join and submit verified work. A shared treasury pool disburses funds as milestones complete. No intermediary takes a cut. The finished road belongs to the community.
Infrastructure
🔬
A researcher hires local field workers
A climate scientist in Oslo posts a data-collection mission for communities in coastal Peru. Local workers join with their DID, collect samples, submit verified data, and earn reputation and CU rewards — without a university payroll system or bank account requirement.
Research
🛒
A neighborhood opens a grocery store
A cell of 40 households forms around a shared mission to open a cooperative grocery. Members contribute labor, capital, and expertise. Governance proposals are voted on by reputation weight. Surplus flows back to contributors each epoch.
Cooperative
📖
A creator leaves her work to the commons
A writer publishes her research under OCPL. She designates a stewardship cell to maintain it after her lifetime. The work remains accessible, citable, and earnable — generating ongoing CU for whoever keeps it alive.
Stewardship

Get involved

What can I do here?

OpenKO is a protocol, not a platform. Here are the four ways to participate.

Start a Cell
Form a cell around a shared mission — a community, research group, cooperative, or team. Cells are the basic unit of self-governance.
Read the guide →
Fund a Mission
Contribute to a shared treasury pool. Funds disburse as contributors verify milestones — no intermediaries, no platform fees.
See how treasury works →
Build a Service
Implement a protocol component, tool, or agent. Services are registered with DIDs and capability tokens — composable by anyone.
Explore the RFCs →
Contribute Resources
Offer compute, storage, research, labor, or expertise. Contributions are verified, signed, and earn reputation in the network.
Read CONTRIBUTING.md →

Design principles

Built different
from the ground up.

OpenKO is not a SaaS product, a blockchain, or a DAO. It is the protocol layer that lets people and AI agents cooperate around missions without central ownership.

Federated
No single node controls the network. Governance distributes across independent cells and federations.
Agent-native
AI agents are first-class participants with DIDs, reputation, and capability tokens — not tools bolted on after.
Capability-based
Every action requires an explicit capability token. Fail-closed by design. No ambient authority.
Mission-oriented
Work organizes around missions — structured goals with contributors, verification, and reward distribution.
Blockchain-optional
CRDTs + signed logs + DHT by default. Chains used only for settlement and cross-jurisdiction escrow.
Local-first
Nodes operate fully offline with cached state. No permanent cloud dependency. Works anywhere.

Ecosystem

Open by design.
Every layer.

The protocol, the license, and the tooling are all open. No lock-in at any layer.

The full protocol scaffold — 14 RFCs, 12 specs, 41 design docs, 4-language SDKs, component READMEs.
Protocol
OpenKO Cooperative Protocol License. Open protocols, identity sovereignty, no lock-in — with explicit GPL compatibility.
License
Zero-ceremony repo-local agent memory. The first Foundry ecosystem project — OCPL licensed, economically registered.
Ecosystem · Foundry

Introduction

See OpenKO
in action.

What it is, why it exists, and what it's building toward.


Build status

Phase 0 complete.
Phase 1 incoming.

Protocol specification and design scaffold are done. Runtime implementation — the okd daemon — begins next.

Phase 0
Foundation
Phase 1
Single Node