Saved Flows and Revisions

A Saved Flow is the durable, executable definition created from Canvas. The Canvas UI currently calls entries in Library → Templates “templates”; they are Saved Flows in the lifecycle described here.

Identity in user terms

Identity	Why it matters
Saved Flow ID	Distinguishes one durable Flow from another, even if names match.
Revision	Advances when the saved definition changes.
Executable fingerprint	Identifies the execution-relevant specification.
Run ID	Identifies one execution snapshot and its evidence.

A display title is for navigation, not concurrency control. Pioneer uses the ID, revision, and fingerprint to prevent a proposal or run request from silently targeting changed state.

Draft, save, and run

Canvas draft --Save/Update--> Saved Flow revision --Run approval--> execution

Each arrow is explicit. Applying a proposal to the draft does not save it. Updating a Saved Flow does not execute it. Executing a revision does not prove success.

Historical evidence

A saved-Flow run records the source Saved Flow ID, saved revision, executable fingerprint, run identity, session identity, and submission time. Later edits do not rewrite that provenance. Executions can therefore show what actually ran even when the current Saved Flow has moved on.

Legacy or direct Canvas runs may have less complete saved-source provenance. Pioneer reports missing provenance as unavailable rather than guessing.