Reliable by Design · 05.14
Capability Router: One Door for Workflow, Node, Phase, Agent & MCP
Resolves a single capability URN onto one execution path, so chat, workflow, and MCP all delegate through the same trusted handlers.
A URN in, a delegation plan out — or honest guidance
The router never reimplements execution — it maps a capability URN onto arguments for an existing, already-trusted platform tool, so capability.invoke delegates through the exact handlers chat, workflow execution, and MCP already share:
| URN kind | Resolves to |
|---|---|
workflow | agentis.workflow.run |
node | agentis.run.replay — replay-from-node against the workflow's latest run |
phase | agentis.run.replay — from the phase's entry node |
agent | agentis.agent.dispatch |
mcp_tool | agentis.mcp.call |
app | The app's sole workflow, or disambiguation guidance if it has several |
Never a silent wrong action
Some URN kinds simply aren't invocable — a skill URN isn't a standalone run, it's a building block meant to be wired into a workflow via skill_task/extension_task; a collection URN is data, not an action, and should be queried or written instead. And when a target genuinely can't be executed as-is — a deep node with no prior run to seed its upstream state from, an app with several workflows and no clear default — the router returns structured guidance naming the concrete next URNs or tools to try, rather than guessing and doing the wrong thing quietly.
Continue
The regression gate that runs cold-start build tasks against a seeded workspace and grades the actual outcome — pass@k versus pass^k.
Manual, cron (natural-language to UTC), webhook, and persistent-listener triggers — how a run actually starts.