#Operator Loop

ByteOr is easiest to reason about as one repeated loop:

1. Author a shared plan through the canonical spec contract.
2. Validate and compile into the selected execution target.
3. Deploy under environment-aware approval and policy controls.
4. Capture and replay artifacts when the runtime needs investigation.

#Author

Authoring starts from a shared plan model rather than graph-only UI state.

• Spec Authoring covers the plan contract and how authored intent maps to the canonical target.
• Execution Models explains when to choose SingleRing versus LaneGraph.

#Validate and compile

Validation is not optional formatting. It is the step that turns authored intent into a deterministic, canonical runtime contract.

• Validation and Compilation explains the lowering path.
• KV Spec Format and Stage Identity cover key reference contracts behind the compiled form.

#Deploy

Deployment posture changes by product surface, but the control points are consistent.

• Governance and Approvals covers the approval gate.
• Cloud explains version, bundle, deployment, and agent orchestration.
• CLI Reference and Production Profiles explain the enterprise runtime side of deployment execution.

#Capture and replay

Capture is the evidence path for incident handling, not an afterthought.

• Incident Bundles and Replay covers the enterprise runtime operator flow.
• Incident and Replay explains the control-plane side of the same loop.
• Artifact Schemas describes the stable machine-readable outputs produced by those flows.