CAPABILITY / 01
Branch-shaped control
Give a child its own namespace, its own controller, and its own local admin — without authority beside or above its parent.
BOUNDED AUTHORITYZENOH NETWORK CONTROL / 001
See the whole Branch.Change the right thing.
A hierarchical Zenoh network is many Routers, under many owners, sharing one namespace. Scout gives every Branch a controller that states what it actually knows, changes Router configuration through a reviewed path, and delegates authority without giving it away.
CONTROL MODEL / SIX CAPABILITIES
Operate intent, not infrastructure trivia.
Scout keeps Branch, Node, Router, Data Area, access, and change in one frame, and leaves the certificates, ACLs, and rendered artifacts one disclosure away.
CAPABILITY / 02
Safe Router changes
Render, validate, review, stage, apply, and observe a candidate, with the restart consequence and last-good recovery in view before you confirm.
INTENT TO EVIDENCE CAPABILITY / 03
Access people can read
Name a Data Area, choose a subject and an action, then read the default-deny native Zenoh ACL that Scout compiles from it.
SCOPED POLICY CAPABILITY / 04
Useful through a disconnect
A partitioned controller keeps operating on what it owns. Remote state is labelled last-known until a fresh acknowledgement arrives.
PARTITION-AWARE CAPABILITY / 05
Identity with a boundary
Every Branch issues its own local identities. Private keys stay out of the browser and out of the management API, and no controller signs for another Branch.
LOCAL TRUST CAPABILITY / 06
Operational truth
Reachability, Router state, deployment outcome, identity, and observation age stay separate, so yesterday's nominal report stays yesterday's.
FRESHNESS FIRSTTHE CONSOLE / FOUR SCREENS
The interface tells you what it knows—and when.
Scope, freshness, identity, and the distance between recorded intent and observed enforcement stay on screen. Every judgment names the evidence under it.
Home leads with what needs attention
The overall judgment names the evidence it rests on, how old that evidence is, and the next useful action.
A Node, group by group
Router identity, process state, management link, agent, and certificate evidence stay distinct instead of collapsing into one health light.
Delegation is reviewed before it exists
The final review names the child, its owned prefix, its capabilities, and how far it may delegate — before anything is created.
Applied stays inspectable
The active revision, the deployment result, the effective configuration, and per-key provenance remain in one frame.
CONTROL PATH / INTENT TO ROUTER STATE
A safe path from human intent to Router state.
The browser never holds a private key or a writable Zenoh identity. The controller authorizes and compiles intent; signed, scoped commands travel a management path that stays independent of the Router being changed.
Local intentSigned controlObserved result
- 01
State intent
A local operator chooses a Branch, Node, setting, or access outcome in the browser.
- 02
Authorize and compile
The Branch controller checks operator scope, records the Change, and renders the effective candidate for the target Node.
- 03
Deliver signed control
Typed commands cross the independent management session with content, scope, issuer, and life bound together.
- 04
Observe the result
The Node agent validates locally, applies only what it owns, and reports fresh evidence back to the controller.
CURRENT RELEASE / v0.1
What's in v0.1
Everything below runs today, on one development machine, against real controllers, Node agents, and managed Zenoh Routers.
- 01
Three independent Branch controllers
HQ, Vilnius, and Field each run their own controller, database, local issuer, local-admin sign-in, and admin origin.
- 02
Real Node enrollment
One-time enrollment material, separate agent and Router identities generated on the host, replay refusal, and activation.
- 03
Reviewed Router configuration
Typed settings through render, validate, stage, apply, restart, and observation, with last-good recovery when the health path fails.
- 04
Data Areas and Access Grants
Named key-expression regions compiled to default-deny native Zenoh ACLs and applied by the controller that owns the Router.
- 05
Cross-Branch access
Explicit direction, delegated ceilings, per-side enforcement, and authenticated Field → Vilnius → HQ delivery proved by counts, sequences, and digests.
- 06
Recursive rollout
Frozen target sets, one wave per operator release, signed acknowledgements at every hop, and a held wave when a Router goes offline.
- 07
Topology you can interrogate
Expected, observed, and correlated links kept apart, each carrying the controller it came from and how old it is.
- 08
Durable single-host deployment
A root Branch that survives a restart, plus rendered systemd and launchd templates. Preview: Scout writes the files and installs nothing.
v0.1 is a development and evaluation profile: one host, no production packaging, no application payload inspection. The product walkthrough and command reference state the current surface in full.
RUN IT / ONE MACHINE
Run the whole three-Branch network locally.
HQ, Vilnius, and Field: three Branch controllers, three Local Owners, three managed Routers, recursive topology, cross-Branch policy, authenticated traffic, and a rollout that stops on a Router it cannot reach.
scout doctor --artifact-root /opt/scout
scout run bootstrap-network release_root=/opt/scout root_state=/var/lib/scout/root root_bind=127.0.0.1 root_router_listen=tls/0.0.0.0:7436 root_router_advertise=tls/root.example:7436