Skip to content

Refuse to publish a task the Queen could never dispatch #4723

Description

@gHashTag

Boundary

  • tools/queen/task_shape.py
  • tools/queen/feed_untested.py
  • tools/queen/feed_defects.py
  • tools/queen/feed_empty_bodies.py
  • tools/queen/refile.py
  • .github/workflows/queen-task-shape.yml

The hole

An issue with no ## Boundary is not work the Queen declines — it is work she cannot see. She reserves files before dispatching, so with nothing to reserve the issue is skipped every round, for good.

Measured 2026-09-23: 565 of 649 candidates skipped for missingBoundary, twenty lanes idle, refusal="nothing to choose" over a board of six hundred open issues.

Every one of those was opened by something that never checked. The feeds (feed_untested, feed_defects, feed_empty_bodies) and refile all call gh issue create with no gate at all, so the swarm has been filling its own backlog with rows it cannot dispatch.

needs_boundary.py labels them a day later; propose_boundary.py drafts what is missing. Both are repairs after the fact. What is missing is the gate.

What to build

  1. tools/queen/task_shape.py — one rule, a pinned twin of boundaryPathsOf in queen-tick.ts. Not an approximation: a gate stricter than the Queen rejects work she would have taken; looser, and it passes work she will silently skip.
  2. Every creator refuses before it files.
  3. A workflow on issues: opened/edited that says on the issue itself what is missing.

It must not close anything. An issue may be a real problem badly filed, and deleting a person's report to keep a queue tidy is the wrong trade.

roadmap and epic stay exempt — a goal is not a task.

Acceptance

  • task_shape.py --self-test passes, pinning the section-ends-at-next-## rule, first-token-per-line, backtick and punctuation stripping, and ## Границы
  • the twin is verified against issues the Queen has already parsed, not only against itself
  • each of the four creators refuses a body with no boundary and still files a shaped one
  • a documentation-only boundary warns and is not refused
  • the workflow comments what is missing and never closes an issue

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions