| Filename | Latest commit message | Latest commit date |
|---|---|---|
c2f8ee225d
Mara wanted the underlying plumbing gone too, not just the dashboard display. Traced every consumer before cutting: - certFingerprint (services.hyperhive.swarm.hives.<name>.certFingerprint): removed the nix option entirely. Its only consumer was the dashboard code removed in the previous commits. - HYPERHIVE_PEERS: removed entirely — the env var itself, the whole block that built it in hive-c0re/environment.nix, and its entry in meta.rs's FORWARDED_VARS (which forwarded it into every agent container). Turned out to have zero real consumers, not just one: the docs claimed hive-agent::identity::peers() read it for qualified agent labels, but no such function exists — identity.rs only qualifies THIS agent's own label with HYPERHIVE_HIVE_DOMAIN, nothing peer-list-related. Grepped the whole hive-agent crate to confirm before removing. services.hyperhive.swarm.peerHives (the nix option HYPERHIVE_PEERS was built from) is untouched — swarm-wireguard.nix reads it directly for the wg-hive mesh, a real and unrelated consumer. Verified: cargo build/clippy/test -p hive-c0re -p swarm-controller all clean (needed nix develop -c per the usual -lsqlite3 gap), all touched nix files pass nix-instantiate --parse, and a throwaway nixosSystem eval confirms the wireguard mesh still configures a peer's wireguardAddress into wg-hive correctly with certFingerprint gone. |
||
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
hive-c0re
The unprivileged host daemon (runs as hive-core). Owns the sqlite
broker, the approval/question/schedule queues, the generic job-DAG
queue, container lifecycle, gateway/forge/matrix provisioning,
per-container stats, and the axum operator dashboard. Largest crate in
the workspace — bin-only, no separate lib.
When to use it
Host-level, cross-container orchestration: spawning/rebuilding/
destroying agent containers, the approval flow, dashboard-visible
state, provisioning per-agent forge/matrix/gateway accounts. Agent-side
behavior (turn loop, MCP tools) lives in hive-agent/hive-agent-mcp
instead — this daemon only talks to agents over the socket wire types
in hive-sh4re.
Shape
Cohesive clusters live in directory submodules, each re-exported at
the crate root (crate::broker::… keeps resolving regardless of which
subdirectory a module actually lives in). One line each — read the
module's own //! doc-comment for real detail, don't expect this file
to track it:
dashboard/— the operator dashboard (containers, approvals, schedules, questions, logs, topology).job_queue/— the job-DAG queue + desired-state reconciliation (docs/coordinator.md).lifecycle/—nixos-containerlifecycle + per-agent config flake generation.stores/— sqlite-backed stores (broker, queues, audit, power).workers/— background sweeps (crash watch, scheduled prompts, auto-update, knowledge sync).agent_config/— per-agent registries (tool groups, capabilities, resource limits, topology).stats/— dashboard metrics aggregation + OTEL export.socket_server/— the unix-socket request server shared by per-agent + manager sockets.forge/— optional Forgejo wiring (docs/forge.md).coordinator.rs— top-level wiring forserve.meta.rs,migrate.rs— the meta flake + schema/state migrations.matrix.rs,gateway_nginx.rs,webhook_secret.rs,priv_client.rs— matrix provisioning, gateway vhosts, webhook secrets, and thehive-privclient respectively.
See the top-level CLAUDE.md/docs/ index for the full reading-path
map.