Skip to content

Runtimes

UWS core defines workflow orchestration. Concrete runtimes bind at execution time and own leaf work: HTTP/event calls, expression evaluation, item resolution, credentials, clients, provider configuration, process management, storage, and product-specific behavior.

Runtime Supplement 1.0

The public uws.runtime.1.0 supplement is a small metadata profile for non-HTTP leaf operations. It is used on extension-owned operations:

operationId: render_message
x-uws-operation-profile: uws.runtime.1.0
x-uws-runtime:
  type: fnct
  function: render_message
  arguments:
    - template: "Ticket {{ticket_id}} is ready"

x-uws-runtime.type is required. Valid runtime type selectors are:

ssh, cmd, fnct, fileio, sql, s3, smtp, dns, ldaps, scp, sftp, and llm.

HTTP is intentionally not a runtime type. HTTP/API/event source operations use core UWS operation binding fields: sourceDescription plus generic sourceOperationId / sourceOperationRef, or the legacy OpenAPI selectors for OpenAPI sources.

Payload Fields

Field Purpose
type Required non-HTTP runtime selector.
command Command text for command-like runtimes.
workingDir Working directory for command-like runtimes.
function Function name for function runtimes.
workflow Nested workflow reference.
arguments Runtime-owned argument values.

The supplement does not standardize credentials, hosts, provider selection, client behavior, security configuration, result schemas, or execution side effects. Those belong to the bound runtime or product-owned extension profiles.

The separate mock fixture format stores source-neutral response values keyed by the resolved UWS request. The public mock runtime executes through the core orchestrator. Its pure runtime supplies fixture/example/synthesis responses and retains bounded would-be request records in memory without network calls. A separate hybrid wrapper requires explicit enablement and delegates only declared UWS 1.12+ reads to a caller-supplied adapter; writes and unknown effects stay on the pure mock path.

For UWS 1.9 advisory content-trust analysis, a runtime implementation may provide a resolver that classifies its own inputs and outputs. In particular, LLM data and instruction channels must be distinguished, and command, SQL, or other side-effect authority channels should be declared explicitly. This resolver is analysis-only: it is not called by UWS validation or execution.

References