Skip to content

Tool Runtime Index

Document ID: TRT-INDEX-001
File Path: docs/07-tool-runtime/index.md
Version: 1.0.0
Status: Active
Owner: AI Platform Team
Last Updated: 2026-06-27


This document is the central navigation and architecture index for the Tool Runtime in the Wovyr AI Platform.

The Tool Runtime is the deployable service that executes tools — safely, with isolation, resource limits, and governance — on behalf of agents and workflows. It operationalizes the model defined by the Tool Framework: the framework specifies what a tool is and how to build one; the Runtime is where tools actually run at scale.


As with the LLM Gateway and the Memory Engine, the platform separates the model from the operated service.

ConcernTool Framework (04-agent-framework)Tool Runtime (07-tool-runtime)
DefinesTool model, SDK, manifest, traitsThe execution service & fleet
AudienceTool authorsOperators + calling services
RegistryRegistry model and discovery APIOperates the registry at runtime
PermissionsPermission model & policy schemaEnforces them per execution
SandboxingSandbox types & policy schemaProvisions and runs real sandboxes
ScalingOut of scopeWorker pools, autoscaling, distribution

The Runtime implements the framework’s Dispatcher, Permission Engine, Sandbox Manager, and Runtime Adapter (Tool Framework §6) as a deployable container. See C4 Container §4.6.


Tool Runtime
├── Execution API (invoke / stream / cancel)
├── Dispatcher (resolve tool → route to worker)
├── Permission Engine (authorize before execution)
├── Sandbox Manager (provision isolated environments)
├── Runtime Adapters (native / wasm / container / microVM / remote)
├── Worker Pool (fleet of execution workers)
├── Resource Governor (limits, quotas, fairness)
├── Secret Injector (mount secrets into sandboxes)
└── Telemetry (logs, metrics, traces, audit)

Caller (Agent Runtime / Workflow)
│ REST / gRPC
Execution API ──► AuthN/Z + tenant resolution
Dispatcher ──► resolve tool + version (Registry)
Permission Eng. ──► authorize (Policy Engine)
Sandbox Manager ──► provision isolated environment
Runtime Adapter ──► execute tool with limits + secrets
Collect / stream result ──► audit + metrics
Destroy sandbox ──► return result

A detailed lifecycle appears in Overview §6.


DocumentResponsibility
overview.mdService responsibilities, architecture, lifecycle, NFRs
execution-api.mdInvoke / stream / cancel contract (REST + gRPC)
sandbox-runtime.mdIsolation backends, sandbox lifecycle, resource enforcement
worker-pool.mdExecution fleet, scheduling, scaling, distributed execution
security-isolation.mdNetwork/filesystem isolation, secrets, tenant isolation, threat model
observability-ops.mdHealth, metrics, tracing, audit, SLOs, runbooks
e2b-gap-analysis.md(Planned) E2B gap closure: persistent sessions, filesystem/process APIs, streaming, SDK

  1. Untrusted by default — every tool runs sandboxed; nothing executes on the host.
  2. Least privilege — no network or filesystem access unless explicitly granted.
  3. Ephemeral execution — sandboxes are created per execution and destroyed after.
  4. Governed — authorize, meter, rate-limit, and audit every invocation.
  5. Isolated tenancy — one tenant’s execution cannot observe or affect another’s.
  6. Bounded — CPU, memory, disk, time, and egress are always capped.
  7. Observable — every execution emits logs, metrics, traces, and an audit record.



VersionDateDescription
1.0.02026-06-27Initial Tool Runtime Index