FlowDrop Workflow Specification 1.0-draft

Dynamic escalation can add an approval but never remove one

Data flowing into a node (including arguments a model filled) may raise the bar for that execution. It may never lower it.

The rule

Normative: this is the rule
  1. Where governance grants the dynamic escalation control, the node type declares a reserved confirmation input port, hidden by default, and a truthy value delivered to it gates that execution.
  2. A falsy value does not participate: upstream data can add an approval requirement and must never remove one.
  3. A value whose truthiness cannot be determined escalates; over-asking is the fail-safe direction for a value crossing a port.
  4. Enforcement is at the gate, not at authoring time: an undeclared port is wireable regardless, so identical wiring on a node type without the grant delivers a value the runtime ignores.
  5. The escalation is not a resolved parameter and must not reach the node's parameters; it is bound into the consent arguments explicitly, so that a change of policy between two executions forces a fresh question (RT-GATE-3).
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 · RT-GATE-9 · changed in spec 1.0