FlowDrop Workflow Specification 1.0-draft

A loop-back input is a control sink, and any is retired

any and trigger differed in one way only (one had compatibility rules built into it from every other lane), and that is a property of being the sink, not of being any.

The rule

Normative: this is the rule
  1. A loop_back input declares the trigger lane.
  2. any is no longer a lane a port may newly declare, and the rules that make the sink reachable from every other lane target trigger instead.
  3. any is not removed from the served payload: it is served disabled, with compatibility rules in both directions and a description saying it is deprecated, because an editor builds its compatibility map from the served list alone and omitting a lane silently makes every edge on a port still declaring it incompatible.
  4. A consequence of targeting trigger is that a data output may be drawn into an ordinary trigger input; the runtime discards the value rather than delivering it.
  5. Compatibility is an authoring affordance only: no server path validates a connection against port lanes, so a wire an editor newly permits was already accepted by every server path if authored by hand.
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 · SCH-38 · changed in spec 1.0