FlowDrop Workflow Specification 1.0-draft

Status vocabulary is guarded in the summary and raw in the node counts

Two counters in the same payload count the same jobs on different terms, and a consumer that reads one as if it were the other draws the wrong conclusion.

The rule

Normative: this is the rule
  1. In job_status_summary and the job API's status_summary, total counts every job, but a bucket is incremented only for a persisted value that is a defined job status.
  2. The buckets may therefore sum to less than total, and a value outside the vocabulary must never appear as a key there.
  3. Each read reports the distinct unrecognised values once.
  4. The per-node node_statuses[*].status_counts is deliberately not guarded: it counts persisted values as they are, so a value outside the vocabulary does appear both as a key there and as node_statuses[*].status.
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-3 · changed in spec 1.0