Watch
0
0
Fork
You've already forked hyperhive
0
hyperhive/hive-core-agent-sock/README.md
iris 0e84fe8bc4 docs: the handbook follows the three layers: swarm, hives, agents
The handbook's sections were agent-lifecycle, integrations, swarm, tools,
trust-boundary and web-ui, which do not follow how the system is built, so a
reader could not tell which layer a page is about. Its pages now sit in
swarm/, hives/ and agents/, with the accounts an agent can hold outside the
system in external-accounts/.

- swarm/: forge, matrix and the knowledge repo join the swarm pages, and so
  does the swarmctl reference.
- hives/: the dashboard, hivectl and its reference, and the operator/agent
  boundary, with a README that takes over the old web-ui and tools pages.
- agents/: the roster, persistence, config changes, the agent's own web page
  (was web-ui/agent) and the security model, with a README.
- external-accounts/: GitHub and GitLab.

Pages are moved whole; none is split yet. Every reference follows: relative
links in the docs, `docs/2-handbook/...` paths in code comments, the nix
checks that regenerate the CLI references and the ignore list, and docs/README.md,
whose handbook section is now by layer.
2026-11-07 12:19:36 +01:00

21 lines
942 B
Markdown

# hive-core-agent-sock
Wire types for the **per-agent socket** (`/run/hive/mcp.sock`) — the
unified `Request` / `Response` protocol spoken between an agent's in-container
harness and the `hive-c0re` daemon.
## Why it's its own crate
Re-homed out of `hive-sh4re` so this one socket owns its protocol crate,
mirroring the `hive-host-sock` / `hive-priv-sock` splits. The shared payload
types it references (`Message`, `LooseEnd`, …) stay in `hive-sh4re`,
which this crate depends on — this crate is just the request/response envelope
for this socket.
## Not to be confused with `hive-agent-sock`
This is the **host-served** protocol: the harness talks _out_ to `hive-c0re`
over `/run/hive/mcp.sock` (broker sends, lifecycle).
`hive-agent-sock` is the separate _in-container_ socket the harness serves to
its own local producers — that one never leaves the container. See
`docs/2-handbook/hives/boundary.md` for the socket topology.