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

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

Browse source
This commit is contained in:
iris 2026-11-06 18:34:41 +01:00 • committed by mara
commit 0e10473e6f
2 changed files with 49 additions and 49 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/2-handbook/agent-lifecycle/config-changes.md
View file

@ -201,7 +201,7 @@ wraps it with identity + `HIVE_PORT` / `HIVE_LABEL`.
### Forge config repos
The bundled `hive-forge` container runs on the swarm's forge host
(`deploy.forgejo.enable`, see [`../swarm/services.md`](../swarm/services.md)).
(`deploy.forgejo.enable`, see [`2-handbook/swarm/services.md`](../swarm/services.md)).
Every agent created through the swarm has a repo in the private
`agent-configs` Forgejo org, created and seeded by swarm-controller.
hive-c0re pushes nothing to it, keeps no clone and reads nothing from it: forge

2
docs/2-handbook/agent-lifecycle/persistence.md
View file

@ -69,7 +69,7 @@ table, and the per-agent power-intent registry:
On a host whose hive-c0re once kept scheduled prompts, the file also
holds `scheduled_prompts` and `scheduled_prompt_targets`. Nothing opens
them; scheduled prompts live at swarm level
([`swarm/schedules.md`](../swarm/schedules.md)). They're safe to drop by
([`2-handbook/swarm/schedules.md`](../swarm/schedules.md)). They're safe to drop by
hand.
Retention: