IIP-056: Kernel substrate unification
IIP-056 is recorded on the Hypervisor Daemon roadmap with status Active implementation in Horizon 0 — contract convergence: Kernel substrate unification. 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-056 Roadmap Record
IIP-056: Kernel substrate unification is an IOI roadmap record for the Hypervisor Daemon surface. Its status is Active implementation in Horizon 0 — contract convergence and it belongs to the Substrate track. Implementation is underway and has current code anchors, but the stated scope is not complete. The canonical scope is: 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.
Surface Context
This record should be read as part of the Hypervisor Daemon roadmap, not as a replacement for source papers or product pages. The parent surface gives the broader context for why this milestone exists, what it depends on, and which IOI surfaces it supports. The parent Hypervisor Daemon surface has no surface-level dependency in the current roadmap model. The parent surface unblocks later roadmap surfaces: hypervisor, ioi, decentralized.
Evidence And Verification
The record is designed to make roadmap evidence crawlable and separable from research claims. No item-level dependencies are listed for this record. Evidence links below point to the paper, release, repository, developer documentation, or product page that supports this milestone.
Canonical Relationship
This page is the canonical roadmap record for IIP-056, while the parent roadmap surface and linked research pages remain the canonical sources for broader product and protocol context. Internal links point here when the milestone status, horizon, dependencies, or evidence trail for Kernel substrate unification matters.
Roadmap Role
IIP-056 exists to clarify roadmap status, bounded scope, horizon placement, and evidence relationships. Technical concepts flow through this page to canonical research pages, while product or runtime context flows to the relevant surface page. This preserves a complete status and evidence trail without making roadmap records compete with deeper IOI papers.