Skip to main content
VentStream Cloud separates what an operator requested from what an engine has observed.

​
Desired run state

Each change creates a complete desired-state snapshot with a monotonically increasing pipeline revision. The agent persists a newer snapshot before acting, ignores stale revisions, and treats redelivery of the same revision idempotently.

​
Observed run state

Agents report starting, bootstrapping, running, paused, drained, degraded, or failed together with the desired revision they are reconciling. Cloud does not infer successful pause or drain from heartbeat freshness.

​
Operation state

Operations can also expire. Queued operations can be canceled; once execution has crossed a side-effect boundary, Cloud does not claim cancellation without an agent result. Agent receipts are persisted before acknowledgement so reconnect delivery does not repeat a completed destructive action. Use ventstreamctl ... --wait when a script requires terminal success rather than mere API acceptance.