| Filename | Latest commit message | Latest commit date |
|---|---|---|
d09ec31431
The container-resource exporter identified the samples it sent by container and by hive, but not by machine or by build — so a sample could not be attributed to the host it came from or the deploy that produced it. Both go on the OTEL resource rather than on each data point, for the same reason `hive` / `swarm` already do: they are constant across one hive-c0re. Only per-container facts stay per-data-point. - `host.arch` — mapped to the semconv spelling, not forwarded from rust's. The two disagree on exactly the architectures this runs on (`x86_64` / `aarch64` vs `amd64` / `arm64`), and the failure mode is silent: a dashboard filtering the standard value matches nothing. A test pins this, since nothing else would catch it. - `service.version` — the running flake rev, via `auto_update::current_flake_rev`, the same source the dashboard snapshot and `get_agent_meta` already use. NOT the crate version: that's a workspace constant that never moves between deploys, so it could not answer "which build produced this sample?". Omitted rather than guessed when the flake ref carries no rev. `spawn_exporter` takes the flake ref to reach the rev — the string it needs, not the whole `Coordinator`, so the module's coupling doesn't widen for one attribute. The issue's third item, `container`, needs no change: `attrs()` has emitted `container.name` per data point since this exporter landed. Checked with clippy (`--all-targets -D warnings`), `cargo test -p hive-c0re` (321 passed) and `nix fmt`. No option surface is touched, so no nix-eval gate. |
||
| .. | ||
| 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.