Workflows API

The workflows API is the clearest operational surface of HyperAgent. It should be read as the control-plane interface for run creation, state tracking, and staged output visibility rather than as a thin wrapper around one contract-generation endpoint.

Run Model

A workflow should be interpreted as a durable run with stage-level state, not as a one-shot request. The current product and repository model track runs, run steps, stage transitions, and workflow outputs as first-class control-plane state. This matters because release-readiness, verification, simulation, and deploy preparation all depend on durable workflow evidence rather than transient logs alone.

How to Read This

Older docs may make workflows sound like broad lifecycle automation across every chain and capability. The current truth set is narrower. Read the workflows API as the current control-plane surface for the MVP lane, then read broader claims only where implementation status is explicitly stated.