FlowDrop Workflow Specification 1.0-draft

One execution has at most one stored snapshot

The rule

Normative: this is the rule
  1. Storing a snapshot is an upsert keyed by execution identifier: an existing record for the same execution is overwritten in place, so one execution never accumulates two snapshot records.
  2. Cleanup deletes records created before a given time and, where a set of statuses is given, only those whose status is in it, answering with the number deleted, zero when nothing matches.
  3. Access to a snapshot is enforced at the API boundary and enforced once there, not repeated by the layer that stores them.
  4. A scheduled cleanup runs with no principal and deletes on the predicate above alone.
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-9 · changed in spec 1.0