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

docs: persistence and config changes become one operator page

Browse source 
The operator parts of the persistence and config-changes pages merge into
agents/persistence.md. The sqlite tables, state dirs, mounts and migrations move
to 4-implementation/agent-state/persistence.md, and the deploy path, meta flake,
deploy markers, startup migrations, root container, system messages and
autoupdate move to 4-implementation/agent-state/config-changes.md. Links, code
comments and nix comments that named the old sections point at the new pages.
This commit is contained in:
iris 2026-11-10 22:22:06 +01:00 • committed by mara
commit 0ae34b1cd0
1 changed files with 919 additions and 881 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/4-implementation/swarm/forge-accounts.md
View file

@ -69,13 +69,13 @@ Two things live in the `agent-configs` Forgejo organization:
allowlists are the `operators` team, and the agent can neither push
`main` directly nor self-merge. An operator's merge in the Forgejo UI
deploys the merged commit (see
[config-changes.md § Config changes](../../2-handbook/agents/config-changes.md#config-changes)).
[config-changes.md § Config changes](../../4-implementation/agent-state/config-changes.md#config-changes)).
hive-c0re pushes nothing to this org and reads nothing from it.
Repos stay private, so an agent can't read another
agent's config. The agent's **persistent meta flake input** is this repo's `main` head,
pinned by sha in `internal/meta` (`agent-<n>.url =
git+<forge>/agent-configs/<n>.git?rev=<sha>`; see
[config-changes.md § Meta flake](../../2-handbook/agents/config-changes.md#meta-flake)).
[config-changes.md § Meta flake](../../4-implementation/agent-state/config-changes.md#meta-flake)).
The `hive-forge` CLI (separate workspace crate, see
[`README.md`](../../README.md) file map) wraps the Forgejo REST API