RT-PIPE

9 rules. Part II of the specification.

• PIPE-1Run status is read from persisted state, on two routes and one envelopecore
• PIPE-2The job status summary has one shape on every pathextended
• PIPE-3Status vocabulary is guarded in the summary and raw in the node countsextended
• PIPE-4Node statuses are keyed by workflow node id and collapse every iterationcore
• PIPE-5A run's jobs are the ones the run itself namesextended
• PIPE-6Authorization is decided before the handler, and travels with its cacheabilitycore
• PIPE-7One job entry shape, published identically by every surfaceextended
• PIPE-8Published execution context is filtered, not forwardedextended
• PIPE-9A timestamp is never fabricatedextended