Synced from Hive. This page is pulled from hivecommons/hive@v5 during the docs build. Edit the canonical source in the Hive repository.
Dashboard glossary and sidebar IA
This glossary records the operator-facing names used by the dashboard. The ADR-0018 IA/naming pass is implemented.
For a plain-language explanation of every dashboard section — what it shows, how its numbers are worked out, and what to do about them — see Dashboard sections explained. Each section title’s ? mark opens its entry there.
Terms
| Term | Meaning | Use in operator UI |
|---|---|---|
| Agent | Runnable automation process or configured role that can plan, scan, review, or otherwise work on hive tasks. | Use for dashboard automation and agent detail pages. |
| Contributor | Human or GitHub account participating through the contributor portal. | Use for people/accounts, leaderboards, trust controls, and profile/admin copy. |
| Contributor agent (ClankeR) | A contributor’s relay-backed worker. Use the full form on first or prominent mention, then Contributor agent for repeated inline mentions. | Use when the operator UI refers to the worker connected through the contributor relay. |
| Governor | Policy engine that decides cadence, autonomy, budgets, and merge/apply gates. | Use for the overview/governance surface and settings that control automation policy. |
| Fleet | The set of agents or contributor agents under observation in an operational context. | Use for aggregate operational controls and live monitoring. |
| Issue band | A display-only group in a repository card’s issue column, named for the operator’s action: Unclaimed, Claimed, Needs triage (agent-filed and not yet acknowledged by a human), Needs human, or Confirm & close. | Use for Projects card grouping; do not imply scheduler eligibility changed. Hover a band header, Overview slice, or legend row for its rule. |
| Pill legend | The collapsible Projects-section key explaining pill colours, borders, glyphs, and badges as a colour key plus captioned issue, pull-request, review, link, and action pills. The aligned repository-card rows keep the left chip for the issue band or PR review class and align actions in fixed slots. | Use for the compact legend above project cards. |
| PR band | A display-only group in a repository card’s pull-request column: Needs human, Merge-eligible, Blocked, In review, Open, or Draft. | Use for Projects card grouping; do not imply merge queue, hold, or review eligibility changed. |
| Stale issue | An actionable repository-card issue whose updated_at activity is older than the configured dashboard.issue_bands.stale_days threshold. | Use for the N no activity > Nd counter and 🕒 badge. |
| Stale PR | A repository-card PR whose updated_at activity is older than the configured dashboard.issue_bands.stale_days threshold. | Use for the PR 🕒 badge. |
Keep ClankeR when naming the contributor relay product/brand, for example the contributor portal line “Powered by ClankeR.” Avoid casual lowercase clanker as an operator-facing noun.
Sidebar map
The operator sidebar keeps the existing destinations, IDs, data-action handlers, and route hashes, but groups them by operator task:
| Group | Items |
|---|---|
| Dashboard | Overview, Governor, Throughput |
| Agents | Dynamic agent tree, + Add agent, + Group |
| Resources | Projects, Contributors |
| Intelligence | Advisory, ACMM Eval, Inception, Knowledge, Strategy Lab |
| Admin | Tokens, Cost, Review Queue, Agents, Audit Log, Diagnostics |
| Help | FAQ, Getting Started, API Spec (Redoc), Getting Started Guide, Join our Discord, Report an Issue |
On the v6 line the sidebar also lists Runs and Platform. Sections hidden by the ACMM level or a feature setting are hidden from the sidebar too.
Count badges use the shared .badge-count recipe. Zero counts render as dimmed 0 badges with data-zero.
Internal clanker-* CSS classes, DOM ids, data keys, and JavaScript names are stable compatibility identifiers. They are not user-facing names and should remain as-is.