vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity
hyperhive/hive-meta-flake
History
Repository files (latest commit first)
Filename Latest commit message Latest commit date
atlas 4697740a7e build an archetype agent from internal/meta only at the archetype it has now 
on deploy, hive-c0re takes the internal/meta head for an archetype agent only
when the head lists that same archetype, and for a custom agent only when the
head lists it as custom, so a switch between the two, or to another archetype,
builds from the hive's own flake until the swarm commits the new flake.
the record location is described in the same docs paragraph.
2026-10-24 21:13:25 +02:00
..
src build an archetype agent from internal/meta only at the archetype it has now 2026-10-24 21:13:25 +02:00
Cargo.toml move the meta flake render into the hive-meta-flake crate 2026-10-24 21:13:24 +02:00
README.md move the meta flake render into the hive-meta-flake crate 2026-10-24 21:13:24 +02:00

README.md

hive-meta-flake

The meta flake's flake.nix text: one nixosConfigurations.<agent> per agent, each built from hyperhive's agent-base plus the agent's config input or archetype.

Pure string rendering, with no IO and no environment reads. The caller passes the hyperhive pin, the agents with their pins, and the values every agent container gets. hive-c0re and swarm-controller both call render_flake, so there is one renderer.