hivelisted

# Hive Operations Use Hive as the control plane. Do not replace its status, watch, scheduler, or recovery machinery with shell polling, process discovery, or an agent-authored sidecar. ## Request routing For daily-history questions such as what happened today, yesterday, on a persisted date, or in one project's daily activity, read [daily-digest.md](references/daily-digest.md) and use its pure JSON route immediately. Do not run the current operational-status loop first. For present operational state, task progress, blockers, or actions, use this loop: 1. Request a fresh machine snapshot with `hive status --operational --json`. 2. The normal `hive` command is the active installation. Inspect `runtime.channel`; when it is `dogfood`, report `runtime.display_version`, the full `runtime.build_sha`, and `runtime.deployment_id`. Do not bypass dogfood by locating another Hive binary, registry, daemon, or web service unless the operator explicitly asks: dogfood replaces the installed runtime rather than running beside it. 3. Check `ok`, `completeness`, task-graph freshness, and scheduler freshness before making a confident claim. 4. Report counts, the exact `project:slug`, state, blocker owner, reason, stage/marker, and provider or scheduler evidence when present. 5. For one exact task's result, usage, applicable evidence, or diagnostic locator, use `hive task TARGET --project NAME --json`. Follow its receipt-correlated log reference with `hive task TARGET --project NAME --log` o