docs: reframe stale 'the manager' as the root/bootstrap container (infra + web-ui)
Port-range, network-isolation, state-dir, web-UI-port, priv allowlist, and rebuild-source mentions now refer to the root/bootstrap container rather than 'the manager' — no structural manager exists (root-ness is topological). Real artifact names (the manager.nix template toplevel, /run/hyperhive/manager/mcp.sock) are left as-is.
This commit is contained in:
parent
adb76f3cdf
commit
ec5c7d49c4
6 changed files with 13 additions and 13 deletions
|
|
@ -96,7 +96,7 @@ across `destroy`/recreate (`--purge` wipes them).
|
|||
## Persistent notes dir per agent
|
||||
|
||||
`/var/lib/hyperhive/agents/<name>/state/` bind-mounts to
|
||||
`/agents/<name>/state` (RW; uniform for sub-agents + manager).
|
||||
`/agents/<name>/state` (RW; uniform for all agents — sub-agents + root).
|
||||
The harness exposes the same path
|
||||
via `$HYPERHIVE_STATE_DIR`. System prompts tell agents to keep
|
||||
durable knowledge here (`notes.md`, anything else). The harness also
|
||||
|
|
@ -112,7 +112,7 @@ unlucky. Operator resolves a collision by renaming the offending
|
|||
agent (different hash → different port) and rebuilding. No state
|
||||
file, no probing, no port-allocation drift — the value is
|
||||
reproducible from just the name. Every agent — including the
|
||||
manager — hashes into 8100..8999 via the same FNV-1a; dashboard
|
||||
root/bootstrap container — hashes into 8100..8999 via the same FNV-1a; dashboard
|
||||
at `cfg.dashboardPort` (default 7000).
|
||||
|
||||
## Restart races on TCP bind
|
||||
|
|
|
|||
Loading…
Reference in a new issue