Every invocation compiles to a plan and is classified step by step—real today, not a roadmap claim.
Route work.
Halt when the source moves.
Chaining multiple skills into a single routed workflow is in development. What's real and callable today is single-skill invocation: invoke_skill compiles a skill to a risk-classified action plan and pauses at "awaiting approval" for any step that needs a human—the safety contract this orchestration layer will build on.
REAL TODAYOne skill, safely.
One skill, safely.
Multi-step is coming.
A step classified as requiring approval pauses the run until a person clears it. This gate does not get skipped for the sake of automation.
Routing work across multiple skills or systems as one orchestrated flow, and halting that flow specifically when a source it depends on changes mid-route.
In progress.
Not shipped today.
There is no multi-step orchestration layer in production yet. Single-skill invocation, with its full safety contract, is real today.
See the MCP tool surface →