mara/hyperhive
mara/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity

docs: sort the top-level directories into five sections by what the reader wants

Browse source 
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.
This commit is contained in:
iris 2026-11-06 18:30:12 +01:00 • committed by mara
commit 6739bb903d
1 changed files with 736 additions and 701 deletions
Download patch file Download diff file Expand all files Collapse all files

4
hive-agent/README.md
View file

@ -16,7 +16,7 @@ understand or change: what happens between a message landing in the
inbox and the agent's reply, how the harness bootstraps login/auth,
how it serves the per-agent web UI, or how turn/event stats get
recorded. Architecture detail lives in
[`docs/turn-loop/`](../docs/turn-loop/README.md); this README is just the
[`docs/turn-loop/`](../docs/4-implementation/turn-loop/README.md); this README is just the
map of the module tree.
## Shape
@ -49,5 +49,5 @@ map of the module tree.
Siblings: **`hive-agent-mcp`** (the MCP server this loop points the
agent at every turn) and **`hive-runtime`** (the library a turn runs
through).
[`docs/turn-loop/::Harness binary shape`](../docs/turn-loop/README.md#harness-binary-shape)
[`docs/turn-loop/::Harness binary shape`](../docs/4-implementation/turn-loop/README.md#harness-binary-shape)
covers all three together.