#ByteOr Enterprise Docs

Curated rustdoc entry points for this namespace.

GitHub source for the owning repository.

byteor-enterprise is the product and operations layer that sits on top of the byteor OSS execution substrate.

This workspace contains shared infrastructure crates plus a small set of operator-facing binaries.

ByteOr Enterprise exposes the byteor execution substrate through a small number of operator verbs and tuning profiles. The important choice is the execution model: SingleRing for compact, tightly bounded flows, or LaneGraph for larger topologies with explicit lanes and roles.

byteor-actiongraph is the enterprise runtime surface for side-effecting stages. Use it when the spec needs to call an external HTTP target or launch an approved local program as part of pipeline execution.

byteor-dataguard is the enterprise runtime surface for schema checks, deterministic redaction, and DataGuard audit output. Use it when the operational contract depends on a file-backed schema registry and a reviewable redaction policy.

byteor-edgeplane is the enterprise runtime surface for transport wiring. Use it when the operational question is "how do I move bytes between external systems and a ByteOr execution path with observable adapter health?"

This guide describes the deployment assets that exist in the repository today and how to read their intended scope.

This is the public runbook that connects host readiness, live state capture, incident export, replay, and artifact interpretation into one repeatable operator sequence.

byteor-policy is the enterprise guardrail layer. It keeps the decision process explicit: given an environment, a replay posture, a dry-run flag, and an action capability, the runtime can explain whether execution is allowed.

Replay is the enterprise path for turning captured runtime state into a controlled audit and, when policy permits, a controlled re-execution.

This page separates the public operator contracts in this repository from the parts of the product surface that are implemented but still moving quickly.

byteor-runtime is the shared operator CLI. The product binaries mirror the same shape and then layer in their own stage or adapter resolution.

This document records the intended approval credential contract used to satisfy enterprise side-effect gates in staging and production environments.

These artifact formats are versioned operator contracts produced by the current byteor and byteor-enterprise runtime surface.