| Filename | Latest commit message | Latest commit date |
|---|---|---|
7f920718f2
mara on !2910: "also remove imperative path for the things that are not nodes yet, file follow up issue to fix that". `TransientGuard`, the stored map and both manual set/clear are gone. `transient_snapshot()` is derived and nothing else — destroy and migration show no pill, because there is no node to derive one from. The pill returns for free when they become nodes. What those three guards were actually doing, though, was suppressing the crash watcher, not drawing a pill. `migrate.rs` said so in its own comment: without it, `crash_watch` fires `ContainerCrash` for every migrated agent and the manager tries to recover containers that were stopped on purpose. Destroy is the same — the container disappears deliberately and nothing in the graph says so. Deleting them outright would therefore have traded a dashboard pill for false crash alerts on every destroy and every migration. So the suppression survives as its own thing, `suppress_crash_watch`, with a name that says what it is. It is still RAII, and still held for the operation rather than stamped once, because the crash watcher's grace window is finite and a destroy is not — a single tombstone would expire mid-operation. The drop stamps the tombstone, covering the poll that lands just after. That leaves RAII in the codebase for exactly one purpose instead of two. Untangling the pill from the suppression is what made the transient layer deletable at all. Follow-up issue for making destroy + migration real queue nodes to follow; at that point this guard goes too. Checked with clippy (`--all-targets -D warnings`), `cargo test -p hive-c0re -p hive-jobq` (322 + 41 passed) and `nix fmt`. |
||
| .. | ||
| 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.