| Filename | Latest commit message | Latest commit date |
|---|---|---|
mara (hyperhive#4271): "whatever is on main is trusted and should be pulled. dont make it periodic, just add it to the meta update when choosing the agent." A meta-input bump previously rebuilt every affected agent against whatever applied/<name> was already locked to. Normally current, but silently stale forever if a past deploy failed and nothing since retried it — the manual meta-input trigger never special-cased that either, since nothing wired it to check the config repo's live main at all. run_meta_lock now relocks each cascade agent's own input alongside the originally-requested ones, against the input's declared source (the forge URL) rather than the local applied/<name> mirror prepare_deploy uses for a reviewed deploy — there's no PR to review on this path, so nothing to gate. One combined lock_update call for the whole cascade: simpler than per-agent isolation, at the cost of one broken/unreachable agent repo failing the whole cascade relock rather than just that agent (the separate top-level input bump above it is unaffected). Known gap, not fixed here: applied/<name>'s own main/deployed/* tags never advance from this path, only a real MergeConfigPr deploy does that — so the audit trail stays as accurate as today, it just stops being what actually got built. |
||
| .. | ||
| 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/scheduler/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/integrations/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.