Repository navigation
Description
Problem
Issues labelled proposal (and/or kind/design) whose RFC text has already merged keep deriving to stage/010-actionable. The Activity monitor then shows them as agent work sitting idle, when there is nothing left for an agent to do. Two live cases on hivecommons/hive today:
- 📝 RFC: LLM-ranked knowledge advisor (OMP-style) #17054 (📝 RFC) — a contributor claim was released (lease revoked), the hive adopted the PR as 📖 proposal: LLM-ranked knowledge advisor (knowledge system phase 2) #17107 (
docs/rfc-17054-…), it merged withRefs #17052only (no closing keyword). The stage engine moved the issue 040 → 010 at 21:38Z. The issue is now an open discussion thread with no agent deliverable, but reads as "Actionable". - 📝 Nous → Spek: feed the winning Nous experiment into spek-new as a source #17020 (📝 proposal, labelled
proposal) — PR 📖 proposal: Nous → Spek — the winning experiment as a spek-new source #17106 merged with a non-closingRefs #17020. The issue was labelledhive/partially-addressedand fell 040 → 010 at 23:54Z. Its body says "No Hive change is proposed yet." It still reads as "Actionable".
Mechanics
src/pkg/stageengine/derive_issue.go:244-253—issueProgressbooks the fall from 040 back to 010 as progress (not a regression) when the issue carrieshive/partially-addressed;actionableIssueStagethen returnsstage/010-actionablefor any open, unclaimed, unparked issue regardless of kind.src/pkg/github/issue_claim_gate.go:160-180— the admission gate refuses onlyneeds-human, the hold family,blocked, parked (045/017) and never-claim labels.proposal/kind/design/ 📝 titles are not gated, so the issue is genuinely claimable and "Actionable" is truthful to the scheduler — it is just the wrong stage for an issue whose remaining content is a discussion.src/pkg/claims/neverclaim.go:23—DefaultNeverClaimLabels = []string{"epic"}: the umbrella family already has a "list of work, not the work" stage treatment (derive_issue.go:197-205); proposals have no equivalent.
Net: the governor sits IDLE with nothing due, and the dashboard shows two "Actionable" items that no lane will ever usefully pick up.
Proposed rule
An open issue labelled proposal (and/or kind/design) with no live claim derives to a non-agent stage in the same family as the epic/never-claim umbrella treatment, rendered in Activity as "Open for discussion" (not "Actionable"). It stays claimable:
- a human
/claim(or the contribute relay) stages it 020/030 as today; - removing the
proposal/kind/designlabel returns it to normal 010 derivation; - a live agent/contributor claim recorded before the rule still stages 020/030 (mirror the epic behaviour, not stricter).
The rule should not touch the admission gate (issue_claim_gate.go): proposals remain claimable; only the derived stage and its Activity wording change.
Acceptance criteria
-
derive_issue.go: an open issue withproposalorkind/designand no live claim derives to the new stage; with a live claim it derives 020/030 as today. - Stage label + Activity chip read "Open for discussion"; the stage reason string names the triggering label.
- Falling 040 → the new stage after a merged
RefsPR is booked as progress, not regression (extendissueProgress). -
issue_claim_gate.gobehaviour unchanged (test: aproposalissue is not refused). - Both 📝 RFC: LLM-ranked knowledge advisor (OMP-style) #17054 and 📝 Nous → Spek: feed the winning Nous experiment into spek-new as a source #17020, replayed through the engine, land on the new stage rather than 010.
- Unit tests in
stageenginecover: proposal unclaimed, proposal claimed, kind/design unclaimed, label removed → 010.
Docs to update
src/docs/stage-engine-plan.md(and any stage-tracker / stage-label reference) — add the new stage and its derivation rule.src/docs/governor-thresholds.md— note that "Open for discussion" issues do not count toward actionable queue depth (or state explicitly that they do, if that is the decision).CONTRIBUTING.mdproposal section — mention that aproposalissue shows as "Open for discussion" until someone claims it.
Activity
hivecommons-hive commentedon Nov 8, 2026
🔓 Claim by @Karibhou released (lease revoked).
Claim history
Karibhou(contributor on hive hosted-available-oke-11-placeholder-r05x)Karibhou(contributor; lease revoked)🐛 fix: unclaimed proposal / kind/design issues derive stage/018-open-…
🐛 fix: unclaimed proposal / kind/design issues derive stage/018-open-…
hivecommons-hive commentedon Nov 8, 2026
PR #17220 covers this issue: #17220
The PR body says this is partial/non-closing work (
Refs/Part ofor leave-open wording), so Hive will not add a closing keyword. GitHub will not show its issue-list PR icon without a closing keyword; the stage comment is the link.🐛 fix: unclaimed proposal / kind/design issues derive stage/018-open-…
🐛 fix: unclaimed proposal / kind/design issues derive stage/018-open-…
github-actions commentedon Nov 8, 2026
@clubanderson this issue was closed by @hivecommons-hive[bot] as completed.
If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.
If you are still seeing the problem, comment
/reopenand it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.