Terminology

action. One named operation of a connector, called as connector.action.

action call. A step body that names an action and supplies its arguments.

agent node. A step body that delegates a bounded sub-task to a model.

binding. A name that holds one value or one scope for the life of a run. A binding is created once and is never reassigned.

capability. A named execution feature that an implementation declares.

catalog. A service or collection that publishes and versions manifests and packages.

connection. The credentials and connection parameters that reach one account of one connector.

connector. One named integration, declared by a manifest.

construct. A step body other than an action call: value, render, route, choose, for_each, parallel, wait, wait_for, repeat, call, stop, run, or agent.

deployment environment. The configuration that supplies connections, workflow identity, capabilities, and policy to an implementation.

evaluation fault. A condition that stops an expression from producing a value at run time.

extension point. A manifest schema entry that a connection defines rather than the vendor.

extension region. A value whose schema is an extension point.

filter package. A published, namespaced set of extension filters with fixtures.

guard. An expression in a position that requires a boolean: when, a choose arm, until, the condition of a conditional expression, the argument of keep, and the outcome of a reconcile.

implementation. Software that claims conformance at a declared level.

manifest. The document that declares one connector, or one filter package.

outcome. The recorded result of a step: succeeded, skipped, failed, or not_run.

part. One named rendered string that a multi-part render step binds.

partial. A template fragment that produces no binding and exists to be included.

projection. A map of names to value-shaped structures, evaluated in a stated scope, that creates bindings in another scope. into, outputs, and with are projections.

promise. A manifest boolean with a defined operational consequence: idempotent, deterministic, validated_output, self_hosted.

run. One execution of one workflow.

run record. The ordered history of a run, sufficient to reproduce it.

scope. A set of bindings. Scopes nest.

schema overlay. A per-connection document that declares the fields of a connector’s extension points.

step. One element of a step list: a map with exactly one key, which is the step’s id.

step body. The value under a step’s id: an action call or a construct.

template. Prose or markup that the workflow owns, rendered by a render step.

trigger. A declared event source that starts a run.

Workfile. One document in the format that this standard defines.