ByteOr Enterprise Product Surfaces

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

    Binaries

    BinaryPurposeEnterprise-specific surface
    byteor-runtimeShared operator CLIValidation, description, DOT output, execution, doctor, snapshot, incident bundles, replay
    byteor-edgeplaneAdapter-oriented runtimeIngress and egress transport loops, runtime heartbeat and snapshot reporting
    byteor-actiongraphAction runtimeResolver-key actions such as http_post:* and exec:*, side-effect gating
    byteor-dataguardData protection runtimeSchema checks, redaction rules, fused DataGuard stages
    byteor-cloud-controlplaneWorkspace member for cloud/control-plane workNot the canonical operator surface for this repo; see archive notes and the separate cloud workspace for active control-plane documentation

    Library groups

    GroupCratesRole
    Runtime identity and pathsbyteor-coreStable product IDs, environment parsing, lane and SHM path conventions
    Governancebyteor-policyReplay posture, side-effect gates, approval requirements
    Execution helpersbyteor-engine, byteor-runtime, byteor-app-kitRuntime wiring, CLI glue, app scaffolding
    Replay and artifactsbyteor-replay, byteor-obsIncident capture, replay audits, telemetry plumbing
    Data safetybyteor-schema, byteor-redaction, byteor-dataguard-coreSchema compatibility, transforms, audit reports
    External integrationbyteor-adapters, byteor-actionsAdapter loops, transport bindings, side-effecting action stages
    Host operationsbyteor-opsPreflight checks, RT scheduling, CPU pinning, memory locking

    Operational shape

    The runtime CLI and the product binaries intentionally look similar. The shared verbs reduce the number of operator playbooks the team has to carry, while stage resolution and adapter wiring stay product-specific.

    That consistency is one of the main enterprise design choices: the same spec inspection, host-readiness, artifact export, and replay habits should transfer across runtime, EdgePlane, ActionGraph, and DataGuard.

    Provenance
    Need the canonical source?
    Use the public hub to orient yourself, then jump to repo-owned docs or rustdoc when you need contract-level detail.
    Source-of-truth modelRepo docs index