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

the rendered meta flake pins each agent config by forge URL at its forge main

Browse source
This commit is contained in:
atlas 2026-10-18 22:24:49 +02:00 • committed by mara
commit 09cabf8398
8 changed files with 432 additions and 163 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/integrations/forge.md
View file

@ -118,11 +118,11 @@ Two things live in the `agent-configs` Forgejo organization:
hive-c0re pushes nothing to this org; it only reads from it.
Repos stay private, so an agent can't read another
agent's config. (Agents remain read-only collaborators on `core/meta`.)
The agent's **persistent meta flake input** is the hive's local `applied`
mirror of this repo (`agent-<n>.url = git+file://<applied>`; see
[config-changes.md § Meta flake](../agent-lifecycle/config-changes.md#meta-flake)),
so building never depends on the forge being reachable. hive-c0re's own git
reads of this repo, which fill the mirror, authenticate with the hive's read
The agent's **persistent meta flake input** is this repo's `main` head,
pinned by sha (`agent-<n>.url = git+<forge>/agent-configs/<n>.git?rev=<sha>`;
see
[config-changes.md § Meta flake](../agent-lifecycle/config-changes.md#meta-flake)).
hive-c0re's own git reads of this repo, which resolve the sha, authenticate with the hive's read
token through `forge::reader_token()` (see
[How a hive reads the forge](#how-a-hive-reads-the-forge)).
- The dashboard links each container's deployed config commit to this