[strategist] Contributor ladder has no reviewer-scaling rung — triage/review capacity is the org bottleneck (74 issues in 1-triage, 32 aged >60d)

[hivecommons-hive]

Strategic Finding

Type: adoption-blocker / ecosystem-opportunity
Horizon: near-term
Cluster: governance docs in projectbluefin/common — CONTRIBUTING.md and contributor-ladder documentation. No open PR touches this cluster (verified against the 2026-08-27 hold-gated PR snapshot: common#1000 is the only open docs PR and covers the Flatpak update schedule only).

Evidence

• Maintainer acknowledgment: on [strategist] Advisory findings backlog (1020, 31 critical) exceeds triage capacity; digest channel truncated at GitHub limit #959 (2026-08-09), @castrojo noted "Should have updated the contributor ladder for incoming review pressure" after ad-hoc recruiting @joshyorko to help review.
• Issue funnel quantification (org-wide snapshot 2026-08-27, 215 open issues):
  • 74 issues (34%) sit in 1-triage; 32 of them are older than 60 days, oldest 213 days (common#192).
  • 3-clanker-queue holds 51 issues while 3-human-queue holds only 3 — the pipeline is agent-heavy precisely because human triage/review bandwidth does not scale.
• The recruitment that relieved [strategist] Advisory findings backlog (1020, 31 critical) exceeds triage capacity; digest channel truncated at GitHub limit #959 was informal (a maintainer asking in a comment thread), not a ladder-driven path a contributor could discover and self-serve.

Rationale

Agent lanes (scanner/quality/sec-check) are producing a steady stream of findings and hold-gated PRs — the 2026-08-27 snapshot shows 33 open hold-gated PRs awaiting human review. Throughput is now gated on reviewer availability, not on finding or fixing. Without a documented reviewer track (triage permissions → review mentorship → merge rights), every capacity increase depends on a maintainer happening to notice a willing contributor. Projects that formalize this rung convert issue-filers into reviewers; projects that don't accumulate a permanent triage backlog and burn maintainer attention on coordination instead of review.

Proposed Next Step

Add a "Reviewer" rung to the contributor ladder in projectbluefin/common CONTRIBUTING docs: explicit expectations (e.g., N substantive reviews on hold-gated PRs), what access it grants (triage label rights, requested-reviewer status), and the nomination path. Seed it by inviting the contributors already doing informal review (ref #959 thread).

Refs #959 (non-closing — that thread is the motivating incident, this issue tracks the structural fix)

---

Filed by strategist agent (ACMM L5 — hold-gated mode)

🐝 Hive Agent: strategist | Instance: hosted-projectbluefin-knuckle-gjvq | SHA: unknown

— hive: agent=strategist backend=copilot model=kimi-k3

[joshyorko]

@castrojo hive is wild

[hivecommons-hive]

Funnel update (2026-08-28 ~13:30 UTC)

The hold gate is accumulating faster than review is draining it:

Metric	2026-08-28 05:44 UTC	2026-08-28 13:30 UTC	Delta
Hold-gated PRs (org-wide)	40	47	+7 in ~8h
Actionable PRs (org-wide)	57	61	+4
Issues in triage queue	74	70 (common) / 233 (org-wide actionable)	—

Additional context:

• Oldest actionable issue: common#192 (213 days).
• Bluefin stable still frozen at stable-20260720 (39 days); promote PR bluefin#1115 open with zero reviews (cross-ref [strategist] Release-gate posture diverges across all 4 product lines — no org-wide stall/override policy #1028).
• server repo PXE cluster adds 4 more hold-gated PRs implementing an unapproved issue ([strategist] Lifecycle inversion in server repo: 4 overlapping PXE PRs (#22/#25/#26/#27) implementing unapproved feature server#14 #1033).

At this inflow rate (~20 hold PRs/day if sustained) against ~3 active human reviewers, the hold backlog doubles roughly every 2-3 days. Each additional day of latency also increases rebase/rotation cost for the 40+ agent-authored PRs already waiting.

Reinforces the proposal above: a reviewer-scaling rung (triage → approved → queued path for trusted contributors) is now the binding constraint on org throughput.

---

Filed by strategist agent (ACMM L5 — hold-gated mode)

🐝 Hive Agent: strategist | Instance: hosted-projectbluefin-knuckle-gjvq | SHA: unknown

— hive: agent=strategist backend=copilot model=kimi-k3

[hivecommons-hive]

Funnel update — 2026-08-29

• 1-triage: 74 (8/27) → 67 today — modest drain, but 210 actionable issues remain org-wide
• Hold-gated PRs: 40 (8/27) → 47 (8/28) → 52 today — the PR-side bottleneck keeps compounding faster than issues drain
• 3-human-queue: 1
• bluefin#1115 (stable promote, frozen 40d) still has zero reviews — the single highest-leverage review in the org right now

Reviewer-scaling rung remains the binding constraint: agent output is accruing at ~5 hold-gated PRs/day while human review bandwidth is flat.

---

Filed by strategist agent (ACMM L5 — hold-gated mode)

🐝 Hive Agent: strategist | Instance: hosted-projectbluefin-knuckle-gjvq | SHA: unknown

— hive: agent=strategist backend=copilot model=kimi-k3

[hivecommons-hive]

A merged PR referenced this issue without closing it. Carrying the remainder back here so the issue timeline shows what is still open.

• docs(contributing): add triage-sla.md — 14-day first-response SLA proposal for human-authored issues #1195 — docs(contributing): add triage-sla.md — 14-day first-response SLA proposal for human-authored issues (docs(contributing): add triage-sla.md — 14-day first-response SLA proposal for human-authored issues #1195)

• docs(contributing): add reviewer-ladder.md — concrete proposal for the reviewer-scaling rung #1080 — docs(contributing): add reviewer-ladder.md — concrete proposal for the reviewer-scaling rung (docs(contributing): add reviewer-ladder.md — concrete proposal for the reviewer-scaling rung #1080)

This comment is edited in place by the task-list sweep on every cycle; it is not duplicated.

[castrojo]

This was generated by AI during triage.

Closing as completed: The requested reviewer-scaling rung for the contributor ladder proposed in this issue has landed on main via #1080 (docs/contributing/reviewer-ladder.md and linked in CONTRIBUTING.md), with companion triage SLA proposals landed via #1195 (docs/contributing/triage-sla.md).

[castrojo]

This was generated by AI during triage.

Reopening: PR #1080 added docs/contributing/reviewer-ladder.md as a proposal, but formally adopting the Reviewer rung into CONTRIBUTING.md governance and granting corresponding triage permissions remains pending maintainer action.