6739bb903d
Every docs directory moves under 1-getting-started, 2-handbook, 4-implementation or 5-project; the options reference (section 3) comes from the website and has no directory here. trust-boundary stays whole under the handbook for now. web-ui, swarm and tools split between handbook and implementation, and the command-line references move to 2-handbook/reference. Links, path references in code and nix, and the docs index follow the moves; no page content changes.
21 lines
951 B
Markdown
21 lines
951 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/trust-boundary/boundary.md` for the socket topology.
|