Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
- Published the Hive dashboard page reference, Dashboard settings explained,
Hosted Hive Hub onboarding, Self-hosted hub deployment and Data collection
and telemetry pages, which the dashboard help links and the Ask AI answers
rely on. Hive design records and ADRs now carry a hidden
`data-docs-kind="design-record"` marker so the Kapa source can exclude them,
and the remaining unsynced design records are listed as deliberate
omissions. Corrected the CNCF Sandbox acceptance date to September 2026
(hivecommons/hive#19182).
2 changes: 1 addition & 1 deletion docs/content/community/what-is-hive-commons.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

**Hive Commons** is a family of open source tools for working with AI coding agents. **Hive** manages project work. **Crux** runs the agents and can be used on its own.

Hive Commons is a [Cloud Native Computing Foundation](https://www.cncf.io/) Sandbox project. The CNCF Technical Oversight Committee voted to accept it in October 2026 ([cncf/sandbox#516](https://github.com/cncf/sandbox/issues/516)), and onboarding is tracked in [cncf/sandbox#545](https://github.com/cncf/sandbox/issues/545).
Hive Commons is a [Cloud Native Computing Foundation](https://www.cncf.io/) Sandbox project. The CNCF Technical Oversight Committee voted to accept it in September 2026: the vote in [cncf/sandbox#516](https://github.com/cncf/sandbox/issues/516) passed on September 28, 2026, and the [CNCF project page](https://www.cncf.io/projects/hive-commons/) lists it as accepted on September 29, 2026. Onboarding is tracked in [cncf/sandbox#545](https://github.com/cncf/sandbox/issues/545).

## Hive or Crux?

Expand Down
2 changes: 1 addition & 1 deletion docs/content/hive/dashboard-sections.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Each entry answers the same questions in the same order:

Hive has two release lines. **v5** is the stable line. **v6** is the newer line. Where something exists on only one line, the entry says so.

For short definitions of the names the dashboard uses, see the [dashboard glossary](/docs/hive/dashboard-glossary). For how the dashboard is built, see the [spoke dashboard guide](https://github.com/hivecommons/hive/blob/v5/src/docs/dashboard.md).
For short definitions of the names the dashboard uses, see the [dashboard glossary](/docs/hive/dashboard-glossary). For how the dashboard is built, see the [spoke dashboard guide](/docs/hive/dashboard).

### Live sidebar count feedback

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ One card per repository Hive looks after, listing its open issues and pull reque
- `project.forge` (or a repo's `project.repo_policies[].forge` / `forge_url` override) and the `gitlab:` or `gitea:` instance URL set the host label and links. See [Forges](/docs/hive/integrations/forges).
- The `dashboard.issue_bands` settings change the band rules.
- **Merge only on current base** ([#15335](https://github.com/hivecommons/hive/issues/15335)). A green `current-base` chip in the card header means the hive only merges a pull request there once its head contains the current base tip; a green head tested on an older base is updated with GitHub update-branch and merges when CI is green on the new head. The hive-wide default is the **Merge only on current base** switch under **Settings → Features → Auto-merge** (`auto_merge.require_current_base_default`, off by default; help text: "OFF by default. Before auto-merging in any lane, require the PR head to contain the current base tip; a green head tested on an older base is updated with GitHub update-branch and merges once CI is green on the new head. Costs one compare call per merge candidate. Per-repo overrides live on the repo card."). Each row under **Settings → Repos** carries the per-repo override — the **Merge only on current base** checkbox with an *inherits* marker, or an **inherit** button when the repo has its own value — written as `auto_merge.require_current_base` (on, also strict: a head the App cannot update is parked) or `auto_merge.skip_current_base` (off). `/api/status` carries the effective value per repository as `requireCurrentBase`.
- See [Repository card legend, issue bands, and PR bands](https://github.com/hivecommons/hive/blob/v5/src/docs/dashboard.md#repository-card-legend-issue-bands-and-pr-bands).
- See [Repository card legend, issue bands, and PR bands](/docs/hive/dashboard#repository-card-legend-issue-bands-and-pr-bands).

## ACMM Eval

Expand Down
943 changes: 943 additions & 0 deletions docs/content/hive/dashboard.md

Large diffs are not rendered by default.

8 changes: 4 additions & 4 deletions docs/content/hive/getting-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ You do not need to reach L6. At L6, permitted lanes can merge when automated che

| Starting point | Action | Continue when |
|---|---|---|
| No hive; you want hosting | Open [Request a hive](https://hive.hivecommons.dev/get-started) and follow [Hosted Hub onboarding](https://github.com/hivecommons/hive/blob/v5/src/docs/hosted-hub.md). Sign in with GitHub, supply the repository URL, and request a starting level. | An admin has approved and provisioned it; **My Hives** shows its dashboard URL. |
| No hive; you want hosting | Open [Request a hive](https://hive.hivecommons.dev/get-started) and follow [Hosted Hub onboarding](/docs/hive/hosted-hub). Sign in with GitHub, supply the repository URL, and request a starting level. | An admin has approved and provisioned it; **My Hives** shows its dashboard URL. |
| No hive; you will operate it | Choose [Docker Compose](https://github.com/hivecommons/hive/blob/v5/src/docs/quickstart-docker-compose.md), [Podman](https://github.com/hivecommons/hive/blob/v5/src/docs/quickstart-podman.md), or [Kubernetes](https://github.com/hivecommons/hive/blob/v5/src/docs/kubernetes-deployment.md). Complete that guide's runtime, storage, network, and login setup first. | Your container is running and you can open its dashboard. |
| You already have a dashboard URL | Sign in with the GitHub identity granted access by its owner. | You can see the welcome checklist and settings. |

Expand Down Expand Up @@ -73,7 +73,7 @@ not an unmanaged standalone deployment.

## Your first week (do exactly this)

1. **Connect and authenticate.** Finish Step 0, then follow [hosted first-run setup](https://github.com/hivecommons/hive/blob/v5/src/docs/hosted-hub.md#3-finish-first-run-setup-on-the-spoke-dashboard) for **Settings → Model Gateways** or the per-backend CLI login. A gateway's **Test** should report `OK — N models available`; a CLI backend must finish its login. Check errors rather than waiting for authentication to fix itself.
1. **Connect and authenticate.** Finish Step 0, then follow [hosted first-run setup](/docs/hive/hosted-hub#3-finish-first-run-setup-on-the-spoke-dashboard) for **Settings → Model Gateways** or the per-backend CLI login. A gateway's **Test** should report `OK — N models available`; a CLI backend must finish its login. Check errors rather than waiting for authentication to fix itself.
2. **Confirm limits before work starts.** Check the ACMM badge and **Settings → Budget**. Set Total Tokens, Period (days), and Critical Percent. To observe without new issues or PRs, use L2. Leave supervisor paused and brainstorm unchanged for this first exercise.
3. **Set cadences, then enable workers.** At L2, open the gear settings for scanner, quality, and guide. Set each available governor/load-mode cadence to **12h or 1d**, then un-pause them. Start with one agent if you want to distinguish its output. Check reviewer separately if enabled: it can post COMMENT-only reviews at L2, not approvals or merges.
4. **Verify setup.** Allow 2–3 minutes for configuration/status propagation. Confirm App access, backend authentication, the applied level, and the saved cadence. A first run can take 5–10 minutes or a full cadence interval; a heartbeat alone does not mean work has run. Check Activity and authentication errors if no run appears.
Expand Down Expand Up @@ -331,7 +331,7 @@ These agents first become available at L5 and remain **paused by default** at L5
1. Open **Settings → Project Observability**. Declare the stack your managed project actually runs and save. This may be OpenTelemetry, Prometheus, Grafana, a `ServiceMonitor`, or a commercial backend. Without that declaration, their PR-capable policies fail closed.
2. Set each agent's cadence before un-pausing it; **24h** is a conservative start. Saving the observability declaration never changes cadences (#7261), so both steps are required.

Leaving them paused is valid. See [Telemetry agent](https://github.com/hivecommons/hive/blob/v5/src/docs/telemetry.md), [Operations agent](https://github.com/hivecommons/hive/blob/v5/src/docs/operations.md), and the `project_observability` block in [agent configuration](/docs/hive/agent-configuration).
Leaving them paused is valid. See [Telemetry agent](/docs/hive/telemetry), [Operations agent](https://github.com/hivecommons/hive/blob/v5/src/docs/operations.md), and the `project_observability` block in [agent configuration](/docs/hive/agent-configuration).

### L5 review routine

Expand Down Expand Up @@ -417,7 +417,7 @@ to grant; remaining at a lower level is valid.
---

For configuration beyond this first path, use [agent configuration](/docs/hive/agent-configuration),
[settings](https://github.com/hivecommons/hive/blob/v5/src/docs/settings.md), and the [documentation map](/docs/hive/documentation-map).
[settings](/docs/hive/settings), and the [documentation map](/docs/hive/documentation-map).

## What this guide doesn't cover (and why)

Expand Down
Loading
Loading