#ByteOr Enterprise Architecture Overview

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

At a high level, the stack is:

1. byteor OSS: spec types, validation, compilation, executor primitives, SHM backings, and the hot-path runtime model.
2. byteor-enterprise: runtime packaging, policy gates, replay tooling, DataGuard, transport adapters, and product-specific binaries.
3. Optional cloud/control-plane layers: bundle authoring, fleet management, approvals issuance, and UI workflows. Those planning artifacts are archived here, but the authoritative cloud workspace lives outside this repo.

#What this workspace owns

The enterprise workspace is organized around four operator-facing binaries and a set of support crates:

• byteor-runtime: shared operator CLI for validation, execution, preflight checks, snapshots, incident bundles, and replay.
• byteor-edgeplane: transport-facing runtime for ingress and egress adapter loops.
• byteor-actiongraph: action-oriented runtime for side-effecting stages such as http_post:* and exec:*.
• byteor-dataguard: runtime for schema checks, redaction, and fused DataGuard stages.

Supporting crates provide the main enterprise value add:

• byteor-policy: environment-aware side-effect gating and replay policy decisions.
• byteor-replay: offline replay and immutable replay audit generation.
• byteor-dataguard-core and byteor-redaction: schema-aware privacy and audit logic.
• byteor-adapters: ingress and egress integrations for transports such as HTTP, gRPC, Kafka, NATS, Redis Streams, RabbitMQ Streams, S3, PostgreSQL, and WebSocket.
• byteor-ops and byteor-obs: host readiness, RT scheduling, memory-locking, pinning, and observability glue.

#Execution flow

The common enterprise flow is:

1. Author or receive a spec.kv pipeline description.
2. Validate and describe it with byteor-runtime or the product binary.
3. Run it in SingleRing or LaneGraph form with an explicit tuning posture.
4. Enforce environment and side-effect policy before live actions execute.
5. Export artifacts such as incident bundles, snapshots, replay audits, and DataGuard reports for operator review.

#Design boundary

This repo documents current enterprise behavior, not every historical design idea. If a document describes SaaS UI, control-plane APIs, or long-range planning instead of the current runtime and operator model, it belongs in ../archive/README.md rather than in the canonical sections above.