Watch
0
0
Fork
You've already forked hyperhive
0
hyperhive/docs
Repository files (latest commit first)
Filename Latest commit message Latest commit date
atlas fae9398295 start the forge and github pollers when their token lands late
Both pollers wait about ten minutes for the agent's token, then exit 0.
Under Restart=on-failure that exit is final, and nothing started them
again, so a token minted or placed after the window left the agent
without notifications until its container restarted.

Add a path unit per poller with PathChanged on the token file(s) the
poller reads, the shape forge-avatar-sync already uses. A path unit
starts its service only when it is not running, so a poller that found
its token is untouched. The github path unit is gated on
github.enable like its service.

Container-side: it ships with the agent's next rebuild, and an agent on
an older rev keeps the old behaviour.

Closes #6179
2026-11-07 08:40:05 +01:00
..
1-getting-started docs: nest config examples and use neutral swarm/hive names 2026-11-06 21:20:49 +01:00
2-handbook start the forge and github pollers when their token lands late 2026-11-07 08:40:05 +01:00
4-implementation hive-agent: the agent has no login flow of its own, credentials come from the swarm 2026-11-07 08:32:11 +01:00
5-project docs: the trust-boundary pages keep the operator guidance, the mechanism moves to implementation 2026-11-06 19:45:11 +01:00
README.md docs: the trust-boundary pages keep the operator guidance, the mechanism moves to implementation 2026-11-06 19:45:11 +01:00

hyperhive docs

Depth reference for hyperhive — the substrate, not the pitch (that's the top-level README / website). Every page here stands alone; pick the one matching your task rather than reading top to bottom. The docs sit in five sections, by what the reader wants:

  1. Getting started: what hyperhive is, and how to bring one up.
  2. Handbook: running and using a hive and a swarm.
  3. Options reference: every NixOS option.
  4. Implementation: how it works inside.
  5. Project: how the project itself works.

1. Getting started

2. Handbook

Using and operating the hive and the swarm. Some pages here still carry implementation detail next to the operator content; sorting those out is later work.

Web UI and tools

Agent lifecycle

Trust boundary and security

Accounts and integrations

Swarm

3. Options reference

The autogenerated NixOS options reference (every services.hyperhive.* / hyperhive.* option, host and agent) lives on the website, built from the module declarations: the options site. Nothing of it sits in this tree.

4. Implementation

Turn loop, scheduler, CI, observability

Networking

Swarm services

Trust boundary mechanics

Web UI internals

Crate reference

  • What does a specific Rust crate do, on its own terms? → 4-implementation/crates/ — every workspace crate's own README.md, one level up from source; the crate itself is still the source of truth, this is just a walkable mirror.

5. Project

How the project itself works: processes, conventions, design guides.