FlowDrop Workflow Specification 1.0-draft

A pipeline engine is a ready-work loop

Re-entering a node on a later pass is what makes loops possible at all, and the empty pass is what defines the end of the run.

The rule

Normative: this is the rule
  1. A pipeline engine repeatedly asks for the work that is ready.
  2. Each pass promotes every idle unit of work whose dependencies are met to pending and persists that promotion, then returns all pending work (including work already pending from an earlier pass), ordered ascending by priority, so a lower priority number runs first.
  3. A unit whose dependencies are unmet is left idle and untouched.
  4. The engine stops when a pass returns nothing; that empty return is what quiescence means.
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 · ORC-9 · changed in spec 1.0