Skip to content

feat(queen): the Queen's priority, decided in t27, and tri priority (Closes #6366) - #6367

Merged
gHashTag merged 2 commits into
masterfrom
claude/queen-priority
Oct 5, 2026
Merged

gHashTag merged 2 commits into
masterfrom
claude/queen-priority

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 5, 2026 •

Copy link
Copy Markdown
Owner

Closes #6366. Refs #6063.

What

  • specs/queen/priority.t27: the one home of the priority rule.
    • Label vocabulary as str consts, one per level: CRITICAL P0,priority/critical,critical; HIGH P1,priority/high,high-priority; NORMAL P2,priority/medium; LOW P3,P4,priority/low.
    • At most 3 criticals per listing; the rest run as HIGH.
    • An open blocker (issue_dependencies_summary.blocked_by) skips the issue.
    • Labelled work ages one level after 14 days, never to CRITICAL. Unlabelled work never ages, so a repository with no labels keeps today's order exactly.
    • Ties go to GitHub's listing order.
    • A why code per issue.
    • 8 tests plus 1 invariant.
  • tri priority: read-only; prints today's listing order beside the priority order. It decides only through gen/c/queen/priority.c + ctypes, and reads the vocabulary from the same compiled file.
  • CI: loop-tools-gate step The Queen's priority is decided in t27. It runs the spec tests from the generated C, fixtures for every rule (including stokowski's "no priority sorted ahead of urgent"), and a reversed outranks as the mutation control.

Evidence

Design sources

A survey of Copilot coding agent, Devin, OpenHands, Cursor, Jira rank, the Kubernetes priority queue, Sidekiq and stokowski. None of them picks the next task for you. The failure modes guarded here: starvation, priority inflation, head-of-line blocking, and "no priority" sorting ahead of urgent.

Not here

  • The running supervisor (gHashTag/BrowserOS trios/agent-server) still ignores labels. It changes in its own PR, which the owner decides because merging there deploys production.
  • specs/queen/dispatch.t27 PRIORITY_RULE still describes the running Queen. It changes when that PR lands.

🤖 Generated with Claude Code

 #6366)

specs/queen/priority.t27 owns the rule: label vocabulary per level, a cap of
3 criticals, blocked issues skipped, one level of aging for labelled work,
listing order as the tie-break. tri queue prints today's order beside it,
deciding only through gen/c/queen/priority.c (gen-c SAME on the t27c lab).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-05 05:46:42 UTC

Summary

Status Count
Total Open PRs 46
PRs with Failing Checks 34
PRs with All Checks Green 12
READY 11
FAILING 34
PENDING 0
NO CHECKS YET 0

These columns do not partition: 11 + 34 + 0 + 0 = 45, and there are 46 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=8597b6ded596 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

#6366)

scripts/tri_loop/queue.py shadowed the stdlib queue for every tool run from
scripts/tri_loop (tri stranded failed: queue has no SimpleQueue). Renamed to
priority.py. The shell census moved: run: steps 287->288 and runner-named
266->267, the one new step 'The Queen's priority is decided in t27'.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@gHashTag gHashTag changed the title feat(queen): the Queen's priority, decided in t27, and tri queue (Closes #6366) feat(queen): the Queen's priority, decided in t27, and tri priority (Closes #6366) Oct 5, 2026
@github-actions

github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-05 05:54:38 UTC

Summary

Status Count
Total Open PRs 47
PRs with Failing Checks 34
PRs with All Checks Green 13
READY 11
FAILING 34
PENDING 0
NO CHECKS YET 0

These columns do not partition: 11 + 34 + 0 + 0 = 45, and there are 47 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=8597b6ded596 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

queen: a task priority the Queen can apply (specs/queen/priority.t27 + tri queue)

1 participant