OpenKO Roadmap

Phase 0 — Foundation

Protocol specifications, architecture, and design documents. No running code — all decisions made deliberately before a single line of implementation.

✓ Complete

✓RFC 0000–0013: full protocol RFC suite

✓12 formal domain specs (DID, capability, mission, federation…)

✓41 design documents — architecture, economics, philosophy, governance

✓Philosophy layer: 9 docs covering civilization coordination

✓SDK stubs: Rust, Python, TypeScript, Go

✓Mission TOML templates and working examples

✓Deployment guides: local node, cloud, federation

✓OCPL v1.1 license + 32 component READMEs

Equivalent to: "OpenKO fully specified on paper."

Phase 1 — Single Node

The okd daemon runs locally. Identity, missions, and treasury work on one machine.

→ In Progress

✓okd daemon binary (Rust)

✓ok CLI: status, identity, mission commands

✓DID wallet: Ed25519 key generation, local storage

✓Mission CRUD: create, list, get (SQLite)

✓Audit log: append-only signed events

✓CapsuleRuntime trait + LocalRuntime (Exosphere seam)

○Capability token issuance + evaluation (fail-closed)

○Mission state machine: open → active → verification → complete

○Contribution submission + peer review flow

○Local treasury: pool balances, CU accounting, epochs

○Reputation: CU accumulation, aggregate score

○Knowledge graph: SQLite FTS5 + content-addressed blobs

○Local agent hosting: personal agent capsule, delegation token

○DID resolution: local cache + DHT stub

Equivalent to: "OpenKO on one machine."

Phase 2 — Federated Mesh

Multiple nodes synchronize. The resource marketplace goes live. Missions propagate across the network.

· Planned

○libp2p mesh: QUIC, gossipsub, Kademlia DHT, circuit relay

○XIP transport: signed invocations, nonce protection, replay prevention

○Mission propagation: gossip-replicated mission state

○Reputation sync: cross-node attestation graph

○Compute marketplace: offer advertising, task routing, CU settlement

○Federation join protocol

○myc:// addressing: DHT-backed service discovery

○Governance: proposals, reputation-weighted voting

Equivalent to: "OpenKO LAN/Internet."

Phase 3 — Cooperative Network

Autonomous agent coordination, compute economy, and knowledge compounding at scale.

· Planned

○Swarm protocol: coordinator spawns, sub-delegation, consolidated outputs

○ZPU Fabric: vCPU model, lane orchestration, eBPF telemetry

○Distributed inference: Zorro + llama.cpp inference capsules

○Knowledge compounding: cross-mission citation graph, semantic search

○Basic Sustenance Fund: per-epoch baseline allocation

○Dashboard app: mission board, contributor profile, treasury view

○Commercial federation tooling

○Contribution decay: governance weight decay for inactive contributors

Equivalent to: "Distributed cooperative intelligence layer."

From scaffoldto civilization.

Phase 0 — Foundation

Phase 1 — Single Node

Phase 2 — Federated Mesh

Phase 3 — Cooperative Network

From scaffold
to civilization.