Internet of Intelligence

Hypervisor Daemon Roadmap

The Hypervisor Daemon is the canonical runtime and effect boundary for autonomous work. A working local implementation spans policy, tools, models, connectors, workflows, receipts, replay, and SDK/CLI clients while the Rust kernel cutover remains active; hosted/DePIN profiles are not shipped.

Hypervisor Daemon Roadmap Context

Hypervisor Daemon is the Substrate surface in the IOI roadmap. The Hypervisor Daemon is the canonical runtime and effect boundary for autonomous work. A working local implementation spans policy, tools, models, connectors, workflows, receipts, replay, and SDK/CLI clients while the Rust kernel cutover remains active; hosted/DePIN profiles are not shipped. This surface spans Built substrate through Horizon 5 — public commitments and should route technical readers to the canonical evidence behind each status claim.

Roadmap Records

The Hypervisor Daemon surface currently contains 14 roadmap records. Each record has its own canonical URL, horizon, status, and evidence profile so readers can distinguish implementation claims, publications, previews, active cuts, and future direction.

  • IIP-005: Runtime daemon v0 is Bounded preview in Built substrate with scope: Working local daemon boundary with Rust-owned runtime slices, tool/MCP controls, policy decisions, receipts, and replay; kernel migration remains active.
  • IIP-006: Agent SDK / ADK facade is Bounded preview in Built substrate with scope: IOI SDK client library and ADK builder framework as clients over daemon contracts.
  • IIP-007: CLI / TUI operator surface is Bounded preview in Built substrate with scope: CLI/headless operator client for domains, manifests, receipts, authority scopes, and node operations.
  • IIP-008: Workflow substrate is Bounded preview in Built substrate with scope: Shared graph model, node contracts, schemas, recipes, and receipts.
  • IIP-013: Hypervisor Workbench surface is Bounded preview in Built substrate with scope: Verifier-gated Workbench application surface over Hypervisor Core; the product shell is not the runtime or product identity.
  • IIP-052: Local model mounting and routes is Bounded preview in Built substrate with scope: Model-route registry, BYOK, LM Studio/Ollama/vLLM/llama.cpp mount drivers, load/unload/remount, and invocation receipts.
  • IIP-056: Kernel substrate unification is Active implementation in Horizon 0 — contract convergence with scope: Cutover from the JS product daemon to the Rust daemon core with Rust/WASM step-module backends; route families migrate behind the hypervisor-conformance gate.
  • IIP-019: Persistent runtime substrate is Active implementation in Horizon 0 — contract convergence with scope: Durable daemon process lifecycle over Agentgres-backed state with replication durability classes.
  • IIP-053: Authority Gateway private preview is Planned in Horizon 1 — single-node pursuit with scope: Daemon sidecar profile: agent harness adapters (Codex, Claude Code, OpenHands, Aider), shell/Git/file/API mediation, wallet-scoped authority, approval gates, receipts, and replay.
  • IIP-055: Hosted and CI/CD gateway adapters is Planned in Horizon 2 — two sovereign nodes with scope: GitHub App, webhook, API proxy, deployment gate, and receipt-ingestion adapters for opaque or hosted agent systems.
  • IIP-057: Hosted and DePIN runtime nodes is Speculative horizon in Horizon 4 — enterprise and embodied with scope: Hosted, DePIN, and TEE venue contracts beyond the working local runtime; advances only when proven scenarios require them.
  • IIP-067: HypervisorOS bare-metal profile is Speculative horizon in Horizon 4 — enterprise and embodied with scope: Speculative Type 1 node profile with the daemon as node root; there is no HypervisorOS build today.
  • IIP-051: AFT Verification Client is Evidence-gated in Horizon 5 — public commitments with scope: Verification client for AFT consensus headers and state-channel proofs, gated on formal and network evidence.
  • IIP-027: Protocol-aware execution is Evidence-gated in Horizon 5 — public commitments with scope: Local execution aware of AFT consensus assumptions and state channels.

Evidence Links

Evidence links connect this roadmap surface to papers, repositories, releases, developer documentation, or product surfaces. They are part of the canonical internal-link graph for IOI.