Workflows and runs

A workflow describes repeatable work. A run is one execution of that workflow or assistant task. The Workflows Console groups workflows, tasks, runs and approvals in the Work area.

Versioned workflow identity

Cloud and Hermes execution use the same canonical workflow identity:

• a stable workflow key;
• a semantic version;
• declared execution targets such as cloud or hermes;
• schema references for inputs and outputs;
• a Workflows organization scope carried through the execution boundary.

The canonical runtime manifest is implementation-owned at contracts/workflows.v1.json. Catalog entries also carry lifecycle and release metadata. A catalog entry is not evidence that a workflow is production-ready; the Workflows Console’s current lifecycle, registry and production-readiness state remain authoritative.

Run lifecycle

From the Work area, users can inspect tasks and runs, open a run’s details and review its result. The current implementation also provides run streaming and server-side stop, retry and detail endpoints. Whether an action is available depends on the run state and the user’s access.

Every durable run should retain its Workflows organization scope. Cloud and Hermes callers must not invent different workflow identities or silently substitute a default organization when scope is missing.

Approval gates

Workflows that write, publish or distribute externally can require approval. An approval is a separate review decision, not a successful run status.

Next: Approvals.