FlowDrop Workflow Specification 1.0-draft

An engine that cannot use a snapshot refuses it, never restarts

Silently discarding a snapshot and starting over looks like resilience and is the opposite: it re-runs every side effect the snapshot recorded as already done.

The rule

Normative: this is the rule
  1. An engine that cannot consume a snapshot it has been given must refuse, naming the snapshot, and must not silently discard it and start the run from the beginning.
  2. An engine with no snapshot-seeding mechanism therefore refuses any snapshot attached to a run, before any run or job exists.
  3. No snapshot attached remains a plain fresh start.

Why

Recorded under OPEN-10.

Rule identifiers are permanent and are never renumbered. Each implementation publishes its own standing against these rules; this specification does not.spec 1.0-draft · INT-15 · changed in spec 1.0