Each hive owns its issues; the workspace owns the view. bh sync aggregates every registered hive — cloned ones by local path, uncloned ones via a blobless minimal-clone cache — so bh hq bd ready answers "what's actionable anywhere?" even on a machine with no code checked out.
bh hq and bh sync use it. The prefix is permanent and derived from org + repo; the provider — the thing most likely to change — lives in a label, so a host migration is a label edit, not data surgery.bh hive sync reconciles a hive against the fleet in both directions. Where the two disagree it surfaces the disagreement as data rather than picking a winner quietly — a conflict is something you read and decide, not something a sync resolves silently while you're not looking. bh sync is the fleet-wide pass: it adds every registered hive, clone-caching the ones that aren't checked out locally.
Work also arrives from outside the plan. bh report files a bug or request into any hive you own — including from a different hive entirely, which is how one repo tells another that something it depends on is broken. bh escalate is the lighter move: name a tool problem, hand it up, and keep working rather than stopping to route it yourself.
Both land in one queue. bh work intake is the per-hive view andbh hq intake the fleet-wide inbox, and the queue is source-agnostic — a cross-hive report, an imported GitHub issue, and a legacy import all triage the same way, with duplicate detection running on entry and again at triage so a colliding request doesn't bury the queue. Four verbs dispose of anything in it:
bh work accept — real work: set type and priority, clear it into the backlog, where it flows through the ordinary ready/dispatch loop.bh work reject — not a bug, or won't do: close it with a reason the reporter can actually read.bh work reroute — filed against the wrong hive: re-file it into the right one, or bounce it up when it's genuinely ambiguous.bh work promote — too big to simply accept: hand it to the planner, which adopts it into a gated molecule instead of letting it sit as an oversized ticket.| Doc | Covers |
|---|---|
docs/AGF.md | The tenets, naming, container branches, dispatch depth, role modes — the process overview. |
docs/DESIGN.md | Hives, prefixes, labels, identity-over-time, git-native hosting — the why. |
docs/WORK.md | Every bh work verb, refine plans, validation modes, conflict ladder, batches, PR-governed landing. |
docs/PLANNING-PLANE.md | The two gates, fidelity tiers, spike loop, replan vs groom. |
docs/CONTROL-PLANE.md | The four control seats, Head Office partitions, the commissioning loop. |
docs/ASSURANCE.md | The warden, the security:* gate, the verifier lens. |
docs/HUB.md · docs/HIVES.md | The cross-hive aggregate, onboarding, hive kinds and identity. |