FlowDrop Workflow Specification 1.0-draft

A port's lane is consumed at a public boundary

The lane a port declares is not only a colour on a canvas. It is the shared answer to "what may a caller supply?" at the endpoints that start a workflow and take a turn in a session.

The rule

Normative: this is the rule
  1. A port's declared lane decides what a caller may supply at a workflow's public entry points: launching a workflow and taking a turn in a session answer from the same check.
  2. A port on the sink or on a control lane places no constraint: any JSON value is accepted, including an array or null.
  3. Narrowing that, for instance by keying the check off JSON Schema's seven type words alone, is strictly stronger and is a breaking change to a public endpoint: it is announced, never carried in on a refactor.
  4. The name a projection gives the field that carries the lane is likewise a client-facing contract.
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-40 · changed in spec 1.0