Versions, history, restores, and forks
Linear history
Section titled “Linear history”A workflow has one current revision and one immutable linear history. Creation produces Version 1. Each changed Save appends and activates the next version. The save requires the exact workflow CAS returned by the latest read.
Persisted revisions are always valid, compiled, and artifact-backed. Invalid source remains in the browser editor. A canonically unchanged save returns the current revision and creates no history entry.
Revision contents
Section titled “Revision contents”A revision records its version number, operation, source, schemas, capability manifest, compiler metadata, call sites, and artifact identity. It also records the human author and optional agent provenance.
Undo and Restore
Section titled “Undo and Restore”Undo appends a revision containing the previous source. Restore can append a revision from any selected version. Both operations record the source revision and preserve all existing history.
A running run stays pinned to its selected revision. A later save, undo, or restore does not make that run stale.
Any seated member can fork a selected revision. The fork is a new owned workflow with its own valid Version 1. Detached provenance points to the source workflow and revision.
Only the seated owner can save, restore, archive, or unarchive a workflow. Organisation admins who do not own the workflow must inspect and fork it.
When an owner loses organisation membership or a seat, their workflows are auto-archived. History and existing runs remain readable, and other members may fork them.