Runtime Orchestrator

Given an approved execution request, how is the correct runtime selected and coordinated independently of any provider? Routing kernel above the execution surfaces — deterministic selection, chaining, fallbacks, immutable plans. Coordinates nothing. Read-only.

Plans

Capabilities

Routable runtimes

Approval barriers

Web research + visual analysisready

4 node · 3 runtime · 2 fallback

browsercomputervision

API → filesystem → webhook pipelinewaiting_approval

3 node · 2 runtime · 0 fallback

apifilesystem3 approval

Desktop app + window arrangementwaiting_approval

3 node · 3 runtime · 2 fallback

desktopterminalwindow3 approval

Constrained research (fallback promoted)waiting_approval

2 node · 2 runtime · 0 fallback

apimcp1 fallback promoted1 approval

The Universal Runtime Orchestrator owns runtime selection and coordination semantics: capability discovery (grounded in the Runtime ABI), deterministic ranked selection with recorded reasons, constraint filtering, ordered fallbacks, dependency-ordered chaining, policy and approval awareness, planner and memory integration, and broker readiness. Plans are deep-frozen (immutable) and every node is planned-only — the orchestrator never executes provider code, performs API requests, launches browsers or desktops, or mutates a filesystem. Future runtimes plug in by registering a RuntimeCapability and shipping an AbiDescriptor; the selection/ordering/validation logic never changes (a new runtime id is an additive one-line type extension). Real coordination is owned by the future Broker behind a binding Policy allow.