#Runtime CLI

byteor-runtime is the shared operator CLI. Product binaries mirror the same verb surface and add their own stage or adapter resolution.

#Verbs

#Common run Flags

--spec=<path>
--profile=default|low-latency|isolated-core
--shm-parent=<path>
--mlockall=on|off
--wait=spin|backoff
--pin=none|balanced|physical
--sched=other|fifo|rr
--rt-prio=<N>
--env=dev|staging|prod
--approval=<path>
--approval-key-set=<path>
--config=<path>

One-shot bring-up also uses run --sp plus input flags such as --input-hex=... or --input-ascii=....

#Product Binaries

Each product binary extends the shared verb surface:

#Capability Contract

capabilities emits a machine-readable document describing the runtime surface:

• Stage catalog entries
• Target support
• Lane-feature availability
• Replay defaults
• Environment restrictions

Cloud and operators consume this contract directly to understand what the runtime supports.

#Compatibility Report

compatibility --spec=<path> [--env=<env>] evaluates a spec against the runtime:

• Target support
• Stage coverage
• Unknown stage keys
• Approval requirements
• Replay posture
• Model-specific run modes

#Snapshot and Incident Bundles

• snapshot captures SingleRing or LaneGraph state directly
• incident-bundle packages the spec, validation result, policy audit, environment data, and optional snapshots into a durable triage unit
• replay consumes a bundle and emits a replay audit documenting selected inputs and resulting decisions

#Machine-readable index

• CLI verbs JSON index