| Filename | Latest commit message | Latest commit date |
|---|---|---|
Six diagnostics and eight comments explained where an environment variable comes from by naming the module file that sets it. The reader of a panic is an operator, who does not edit that file; the reader of the comment is already in the code. Neither can act on a filename, and a filename in prose is checked by nothing. Each one now names what the reader can act on: the option where there is one (services.hyperhive.network.bridgeName, .bridgeIp, .bridgePrefixLength, c0re.assets, c0re.orgAvatarPng), otherwise the unit the process is expected to run under. Two of the six diagnostics had a real option available; the other four have none, so they name the unit rather than an invented path. Four of them pointed at hive-c0re.nix, which is a directory. Two of those spelled it nix/modules/hive-c0re.nix — a directory that does not exist either, and one of the two was wrapped across a line break, so no grep for the whole path could have found it. That is the argument for the change: prose naming a file rots silently because nothing compiles it. Scope here is the four files around those diagnostics. The same pattern still matches elsewhere in the tree; that sweep follows. |
||
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
hive-c0re
The unprivileged host daemon (runs as hive-core). Owns the sqlite
broker, the approval/reminder/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, 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.