FlowDrop Workflow Specification 1.0-draft

The lane vocabulary is the served payload, not the shipped set

What a port may declare and what an implementation ships are different questions. Answering the first with the second is how a site could add a lane it could never use.

The rule

Normative: this is the rule
  1. The declarable lane vocabulary is the served port configuration: the shipped lanes, the port-shape registry (code-declared shapes first, then site-declared ones), and the site's stored overlay, composed in that precedence order.
  2. Whether a port may declare a lane is asked of that payload, never of the shipped set alone: otherwise a site can add a lane, colour it and write rules for it while no port is able to declare it, the declaration being silently replaced by the schema-derived lane with a wrongly coloured handle as the only symptom.
  3. A lane the payload does not declare is still refused, because such a port would be compatible with nothing, not even with another port of its own lane.
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-41 · changed in spec 1.0