IIP-075: One monitor for every boundary effect
IIP-075 is recorded on the Hypervisor Daemon roadmap with status Active implementation in Horizon 0 — building the governed core: One monitor for every boundary effect. Every effect a guest agent can cause (network, credentials, model and tool calls including MCP and connectors, business actions, spend, delegation) crosses one small reference monitor. The monitor records the intent before dispatch, decides it under policy, and reconciles the outcome. Guests run in isolated cells that fail closed..
What it is
Every effect a guest agent can cause (network, credentials, model and tool calls including MCP and connectors, business actions, spend, delegation) crosses one small reference monitor. The monitor records the intent before dispatch, decides it under policy, and reconciles the outcome. Guests run in isolated cells that fail closed.
Where it stands
Under construction; isolation and containment are on the current critical path. Today’s connector and MCP routes predate the monitor and move behind it as it lands.
What has to be true next
An independent attacker, with a budget fixed in advance, runs the bypass battery against each class of cell and finds zero effects outside the monitor.
Status
Active implementation in Horizon 0 — building the governed core. Implementation is underway and has current code anchors, but the stated scope is not complete. Horizons order work by evidence, not by date.
Evidence
The paper, release, repository path or evidence bundle behind this status.