Execution Models
ByteOr OSS defines two execution models — SingleRing and LaneGraph — authored through the same source contract and compiled through the same validation pipeline.
Canonical shared reference
This page provides the OSS-focused view. The full execution model reference is shared across all product surfaces in the Core Concepts section.
SingleRing
Ordered linear execution. Stages run in topological order with explicit dependencies within a single shard.
- Straightforward ordered processing pipelines
- Stage ordering is the primary correctness requirement
- Lower complexity — no branching or fanout
LaneGraph
A directed graph of lanes and roles supporting branching, fanout, merge, and richer boundary routing.
- Complex topologies with branching or fanout
- Fan-in (merge) patterns
- Explicit lane-kind selection per connection
- Richer boundary routing policies
Shared Source Contract
Both models use PipelinePlanV2 as the source contract. The execution target is an explicit choice, not an implicit consequence of the spec shape.
OSS Crate Surface
The execution model implementation lives in the OSS crate workspace:
byteor-pipeline-spec— canonical plan and spec data modelbyteor-pipeline-lower— validation and loweringbyteor-pipeline-exec— runtime execution primitivesbyteor-pipeline-kernel— stage kernel contracts