Repo Map

    The platform is intentionally split across repositories so each layer can keep a clear ownership boundary.

    RepositoryOwnsCanonical docs
    indexbusBounded shared-memory transport, lane semantics, router/merge infrastructure, transport ABISynced IndexBus docs and rustdoc
    byteorPipeline spec model, validation, compilation, runtime execution primitives, ByteOr ABISynced ByteOr OSS docs and rustdoc
    byteor-enterpriseGovernance, approvals, replay, product runtimes, adapters, DataGuardSynced Enterprise docs and rustdoc
    byteor-cloudHosted control plane, deployments, agents, config bundles, artifacts, approvals UXSynced Cloud docs
    byteor-docsPublic hub, onboarding, cross-repo narrative, reference entry pointsThis Rspress site

    How to use this split

    • Use this site for the product story, onboarding path, and cross-repo navigation.
    • Use synced repo docs when you need the canonical technical or operator contract.
    • Use repo rustdoc when you need crate- and type-level API detail.

    Most common navigation paths

    • Substrate and transport integration: IndexBus
    • OSS runtime and spec model: OSS
    • Enterprise runtime operations: Enterprise
    • Hosted control plane: Cloud
    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