Expand description
External workflow definitions and validation entrypoints.
§Fragment: workflow-structural-boundary
This crate owns the static workflow graph shape. It validates structural facts that must be true before any runtime can reason about execution: nodes are uniquely named, ports are uniquely named within a node, and edges connect declared output ports to declared input ports. Runtime concerns such as scheduling policy, cycles, payload compatibility, cancellation, and backpressure are intentionally left to later layers.
§Fragment: workflow-validation-scope
The validation rules stop at structural honesty on purpose. A graph can be structurally valid and still semantically wrong for a later runtime or data model. Keeping that line clear prevents the workflow crate from accumulating scheduling, typing, or capability policy that belongs elsewhere.
§Fragment: workflow-deterministic-errors
Validation uses ordered maps and sets so duplicate detection and missing-edge errors are reported deterministically. The graphs are small enough that this tradeoff favors stable diagnostics and test output over marginal hash-table speed.
Structs§
- Edge
Definition - Directed connection from one output port to one input port.
- Edge
Endpoint - Static endpoint for one side of a workflow edge.
- Node
Definition - Static node declaration and its input/output port topology.
- Workflow
Definition - Parsed workflow definition independent of runtime execution.
- Workflow
Graph - Validated graph-level workflow structure.
Enums§
- Edge
Capacity - Capacity policy for a workflow edge.
- Edge
Endpoint Role - Which side of an edge failed validation.
- Port
Direction - Direction of a port in a node’s static topology.
- Workflow
Validation Error - Error returned when a workflow graph is structurally invalid.