Hypervisor Roadmap
Hypervisor is the product estate over the daemon substrate: one Core, first-class App/Web/CLI clients, and cataloged application surfaces. The local/private-preview shell and broad P0–P2 surface ladder are verifier-gated; deeper marketplace, feedback, training, and governance work remains active or planned.
Hypervisor Roadmap Context
Hypervisor is the Console surface in the IOI roadmap. Hypervisor is the product estate over the daemon substrate: one Core, first-class App/Web/CLI clients, and cataloged application surfaces. The local/private-preview shell and broad P0–P2 surface ladder are verifier-gated; deeper marketplace, feedback, training, and governance work remains active or planned. This surface spans Built substrate through Horizon 3 — Goal Space service and should route technical readers to the canonical evidence behind each status claim.
Roadmap Records
The Hypervisor surface currently contains 11 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-012: Hypervisor Workbench private preview is Bounded preview in Built substrate with scope: Core client shell (Home, Projects, Automations, Applications, Sessions), approvals inbox, run lineage/replay, model catalog — P0–P2 surface ladder complete, verifier-gated.
- IIP-058: Identity, access, and OCU metering is Bounded preview in Built substrate with scope: Deployment-local principals, sessions, OIDC/SCIM, secrets, enforcement, and coarse receipt-derived OCU projection; no invoice-grade reconciliation or SaaS billing.
- IIP-059: Environments and BYO provider plane is Bounded preview in Built substrate with scope: Partial environment lifecycle, readiness, warm pools, placement, and provider adapters; one complete governed Akash workload, result, teardown, and settlement lifecycle demonstrated; DePIN and storage posture families vary.
- IIP-068: Governed external effect, end to end is Bounded preview in Built substrate with scope: A hostile, root-capable model worker crossed a VM-enforced authority boundary, executed a real Akash workload, returned authenticated results, settled to zero exposure, and produced C8 evidence a policy-gated registry accepted — on one pinned audited provider, under sovereign-local custody, verified by a first-party relying party.
- IIP-060: P3 surface ladder is Active implementation in Horizon 0 — contract convergence with scope: Marketplace deepening, native feedback/annotations, governance-card tail, and settings folds over the completed P0–P2 estate.
- IIP-054: Connector sprint readiness is Active implementation in Horizon 0 — contract convergence with scope: Connector estate, capability leases, and MCP gateway live; semantic-data chain and canonical risk-class enum migration in progress.
- IIP-020: Marketplace worker installs is Planned in Horizon 1 — single-node pursuit with scope: Operator installs, security policies, workspace extensions.
- IIP-071: Provider-neutral governed execution is Planned in Horizon 1 — single-node pursuit with scope: The same logical operation under the same authority and evidence contract across Akash, AWS, and local compute — a conformance proof, not candidate routing or adapter availability.
- IIP-035: Managed training workflows is Planned in Horizon 1 — single-node pursuit with scope: Foundry training and evaluation execution over the existing object plane: datasets, teacher sessions, tuning/distillation, benchmark gates.
- IIP-043: Benchmark-linked improvement is Planned in Horizon 1 — single-node pursuit with scope: Auto-tuning weights, shape corrections, error logs loop.
- IIP-044: Worker training platform is Planned in Horizon 3 — Goal Space service with scope: Decentralized compute orchestration, custom weights publishing.
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.