Watch

History

Repository files (latest commit first)
Filename	Latest commit message	Latest commit date
atlas 657d1b5061 feat(#2788 ): carry Skipped to the wire as its own state A node ruled out by its own dependency edges settles `Skipped` host-side, but the wire folded it into `Cancelled` and `dag_view` filtered it out entirely, so a client never saw which branch a run didn't take. Post-#2785 that is not a rare shape: every approval DAG has two not-taken tails and every rebuild has one, on the happy path as much as on failure. `State` gains `Skipped`, and it counts as terminal — the wait loops in hivectl's progress display and the daemon's dag-settled check decide "finished" with `all(is_terminal)`, so omitting it would hang them on essentially every DAG. `dag_view` now emits skipped nodes but no longer lets them keep a DAG alive. Serialization and completion were the same expression: a DAG left the snapshot because its nodes had all been filtered away. Keeping skipped nodes on the wire under that rule would pin every finished deploy in the queue view forever, so the completion test is now its own flag. `rollupState` in the dashboard gains the matching arm. It has no `done` case — `done` is inferred by falling off the wire — so its trailing `return 'queued'` catches anything it doesn't recognise, and a green deploy would have read as permanently queued the moment the backend started emitting the new state. The Rust and JS roll-ups have silently disagreed before; they are edited together here and say so.		2026-07-27 20:27:58 +02:00
..
src	feat(#2788 ): carry Skipped to the wire as its own state	2026-07-27 20:27:58 +02:00
Cargo.toml	docs: declare readme = "README.md" for the last four crates	2026-07-27 09:35:06 +02:00
README.md	docs: trim readmes down, stop restating impl detail the module docs already own	2026-07-26 21:01:00 +02:00

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-container lifecycle + 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 for serve.
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 the hive-priv client respectively.

See the top-level CLAUDE.md/docs/ index for the full reading-path map.