Watch

History

Repository files (latest commit first)
Filename	Latest commit message	Latest commit date
atlas 6a8a729f58 fix(#3020 ): K3PT ST4T3 says what it shows, and stops reading the job graph `build_tombstone_views` folded `transient_snapshot`'s keys into its `live` set, so an agent with in-flight transient work was treated as not-a-tombstone. Since #3010 that set is derived from the running job graph, which made a page about on-disk state a function of the scheduler. Dropping the filter exposes what was always true underneath: nothing records a destroy. Every definition-side artifact — state subvolume, proposed + applied repos, `deployed/0`, meta registration, topology entry — is written by `Provision` before the container exists and survives `lifecycle::destroy`. So a mid-spawn agent is byte-identical on disk to a tombstone. Per mara on #3020: remove the filter, warn on the page, keep the issue open for the swarm-controller / snapshot-storage rework where the problem shape changes anyway. - dashboard/tombstones.rs: drop the param + the chain; document the real semantics - core.js: amber caveat banner above the rows; row badge `destroyed` -> `offline`, which is what an absent container actually proves - dashboard.css: `.tombstone-warn`, modelled on `.port-conflict` but amber and without the pulse — a permanent banner that pulses trains you to ignore it - docs/web-ui/dashboard.md: the pane was described as "destroyed-but-state-kept agents", now the exact wrong claim		2026-08-03 18:07:04 +02:00
..
src	fix(#3020 ): K3PT ST4T3 says what it shows, and stops reading the job graph	2026-08-03 18:07:04 +02:00
Cargo.toml	jobq-wire: move the generic graph projection into its own crate	2026-08-03 00:39:14 +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.