Expand description
The node contract: re-executable units over consumer state S.
Nodes are the consumer’s computation units; the engine owns topology, scheduling, and
state movement. A node never names its successors — it reads its gathered inputs,
mutates RunContext::state, stages outputs, and the engine decides what happens next
by evaluating the outgoing edges. A node may run zero, one, or many times per run.
Enums§
- Activation
- How a node joins a frontier, i.e. how its pending activation tokens are counted.
- Node
Outcome - Defines the evaluated outcome of a single node’s execution turn.
Traits§
- BspNode
- The programmatic contract for writing execution nodes.
- Dataflow
Node - The dataflow-profile authoring trait: plain-Rust node authoring without macros.