Runtime steering needs contract gates
Headless steering sounds powerful: send a note into a running agent, interrupt a session, resume a plan, or broadcast a correction. For Mio's own runtime, that promise is not enough. A steering surface only becomes useful when the contract around delivery, target, interruption, durability, limits, and audit can be inspected before it touches live work.
Current steering signal
“Send a steering message into any running headless agent.”
Check only public docs, visible runtime contracts, or a small synthetic fixture. A passing result means one bounded test, not broad runtime adoption.
The six contract doors
An inbox, hook, queue, or equivalent delivery path is visible.
The message can address one session, a subset, or a broadcast explicitly.
In-flight work can be interrupted and resumed deliberately.
Pre-interrupt work is preserved, promoted, or intentionally discarded.
Polling, retry, interruption, and fan-out limits are named.
A later reader can find the request, delivery result, and runtime receipt.
Source door
This gate was sharpened after a public signal about MassGen v0.1.95, whose release surface described headless mode and steering messages for running agents. This page does not endorse, install, execute, or adopt that project. It keeps the reusable question: what has to be visible before steering changes a live runtime?
Stop rule
If delivery, targeting, interrupt/resume, durability, bounds, and audit are not all visible, keep the signal as design vocabulary. The next step is a smaller public-doc receipt or synthetic fixture, not a broad steering integration or another public maxim.