#What Is ByteOr

ByteOr is a governed execution and replay platform for real-time systems. It combines deterministic pipeline execution with policy-gated deployments, incident capture, and audited replay.

#The Four-Layer Stack

ByteOr is built as four composable layers. Each layer has a clear boundary and can be understood independently.

Each layer builds on the one below it. IndexBus provides the transport. ByteOr OSS defines how pipelines are specified, validated, and executed. Enterprise adds governance and operational tooling. Cloud provides the hosted control plane.

#Execution Models

ByteOr supports two execution models through a single spec authoring surface:

• SingleRing — Ordered linear execution with explicit stage dependencies and shard-aware scheduling. Best for straightforward ordered pipelines.
• LaneGraph — Branching, fanout, merge, and richer boundary routing through a directed graph of lanes and roles. Best for complex topologies.

Both models share the same source authoring contract (PipelinePlanV2). The execution target is chosen explicitly, and the compiler lowers the plan into the canonical target format.

#Key Capabilities

#Spec-Driven Pipelines

Pipelines are defined as structured specs, not ad-hoc configuration. The spec is validated, compiled, and lowered into a canonical form before execution begins. This means runtime behavior is deterministic and reproducible.

#Governed Deployments

Production deployments require policy-gated approvals. Approvals are scoped to environments and spec versions, verified by cryptographic credentials, and recorded in audit trails.

#Incident Replay

When something goes wrong, ByteOr captures incident bundles containing the spec, validation result, policy audit, environment data, and state snapshots. Operators can replay captured inputs in dry-run mode for investigation or in governed execute mode for remediation.

#Runtime Operator Tooling

The runtime CLI provides verbs for every stage of the operator workflow: validate, describe, dot, diff, run, doctor, snapshot, incident-bundle, and replay.

#What ByteOr Is Not

• ByteOr is not a general-purpose workflow engine or ETL platform.
• ByteOr does not replace your message broker — it adds a deterministic execution layer on top of bounded transport.
• ByteOr does not claim to be a security boundary by itself — it relies on OS-level process isolation and adds governance controls on top.

#Next Steps

• Architecture and Stack — how the layers compose
• Execution Models — SingleRing and LaneGraph in detail
• Cloud Quick Start — deploy your first pipeline through the control plane