FlowDrop Workflow Specification 1.0-draft

A node whose triggers are all unsatisfied is skipped, not executed

This is the line the whole branching design rests on: an untaken branch does not merely fail to fire, it terminates cleanly, visibly, and without failing the run.

The rule

Normative: this is the rule
  1. A node with at least one incoming trigger edge and no satisfied trigger is skipped and must not be executed.
  2. The skip is announced with the machine-readable reason branch_not_active, on the node-level skip event, on the real-time status update, and on the run's snapshot; the node's identifier also appears among the run's skipped nodes in the response metadata and is counted there.
  3. A node with no incoming trigger edge always executes, whatever its data sources did.
  4. At the end of a run, every node still unexecuted is collected as skipped the same way, whether or not it had already been promoted to ready.
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 · BR-7 · changed in spec 1.0