FlowDrop Workflow Specification 1.0-draft

Published execution context is filtered, not forwarded

Whatever an engine parks on a run would otherwise become public the moment it is written, and after one release it cannot be withdrawn without breaking consumers.

The rule

Normative: this is the rule
  1. The execution_data.context a run publishes is a filtered projection of the execution context, not the stored context forwarded verbatim, and the filter is a single point through which everything published passes.
  2. Engine-internal analysis artefacts (a graph-analysis snapshot such as a loop membership map is the case in point) are removed whole rather than by selected sub-keys, so their internal shape is not published and may change without notice.
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 · PIPE-8 · changed in spec 1.0