FlowDrop Workflow Specification 1.0-draft

A gated node whose executor cannot be resolved never executes

Fail-closed here means error, not ask. Reading a missing executor as "no side effects" silently ungates the node; asking about a call that can never run trains operators to rubber-stamp.

The rule

Normative: this is the rule
  1. Where a node's confirmation requirement must be derived from its executor and that executor cannot be resolved (no such executor is defined, or its implementation is unavailable), the node must not execute and must not raise a confirmation prompt.
  2. The derivation fails, and the node fails as any node with an unresolvable executor does.
  3. An implementation may elsewhere let callers probe an executor's declarations without raising, treating an unresolvable one as declaring nothing; that leniency must not be used at the gate, where it would read a missing executor as harmless.
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-11 · changed in spec 1.0