Requirements

Scout operates from installed release artifacts. Runtime commands do not need Cargo, Bun, a source checkout, or a project-local toolchain.

Release layout

The release root must contain the scout, controller, and Agent binaries, the private configuration checker, and the built admin console. The installation guide for your package defines the concrete root; examples use /opt/scout.

Pinned dependencies

Run the product check instead of comparing versions by hand:

scout doctor --artifact-root /opt/scout

The command checks the exact versions recorded by the release and reports separate evidence for every dependency and component. An unavailable check stays unavailable; it is never reported as nominal.

Host authority

Creating service units, writing protected Client configuration, or enabling a service requires explicit system-administrator authority. Ordinary API and recipe steps use the caller’s Scout token. Recipes never carry credentials or privileged shortcuts.

For a local evaluation, reserve distinct state directories and ports for each Branch and ensure no existing Zenoh process owns the selected endpoints.