#Choose Your Path

ByteOr spans four product and repository surfaces. Start with the path that matches your role, then drop into synced repo docs or rustdoc only when you need implementation detail.

#Evaluating the platform

• Start with What Is ByteOr for the four-layer stack.
• Continue to Architecture for how the layers compose.
• Use the section roots for deeper technical entry points: OSS, Enterprise, Cloud, and IndexBus.

#Building on the OSS execution substrate

• Go to OSS for the open-source runtime and spec model.
• Use Execution Models, Spec Authoring, and Validation and Compilation for the authoring and lowering flow.
• Drop into ABI and Headers and Rustdoc entry points when you need integration detail.

#Operating enterprise runtimes

• Start at Enterprise.
• Use CLI Reference, Tuning Profiles, and Incident Bundles and Replay for the operator loop.
• Read Enterprise Governance before enabling governed actions in staging or production.

#Running the hosted control plane

• Start at Cloud.
• Use Cloud Quick Start for the first draft-to-deployment path.
• Continue to Agents, Approvals, and Incident and Replay for steady-state operation.

#Integrating the transport substrate directly

• Start at IndexBus.
• Continue to Execution Patterns, SHM Transport, and Layouts.
• Use Rustdoc entry points when you need the normative transport contracts.