Issues that meet the Queen's own bar - #4445
Merged
Merged
Conversation
QueenSpecQuality checks four things and names them: a `## Boundary`, a scenario (Given/When/Then, either language), a requirement written as an obligation (`FR-001 ... MUST`), and criteria with a measurable outcome. Every issue the feeders have opened carried the first and the fourth and neither of the other two. Measured on the live tick: `incompleteSpec` skipped 69 candidates against 25 the day before - not because anything got worse, but because 102 more issues had been filed in the same shape. A skip is not a refusal, but a candidate skipped first is a candidate that waits, and these waited for two sections derivable from numbers the issue had already measured. All three shapes carry them now - single_issue, part_issues and the untested-function feeder - from one shared scenario_and_requirements(). The scenario names the file, what is wrong with it and the functions by name. The requirements are the three that were already true and unwritten: keep the signature, keep the file parsing, do not delete a function to satisfy a count. Verified against the Swift predicates rather than by eye: all four checks read true for all three shapes. Closes #4444 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
gHashTag
enabled auto-merge (squash)
September 20, 2026 13:45
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #4444
QueenSpecQualitychecks four things. Every issue the feeders have ever openedcarried two of them.
A skip is not a refusal — the swarm dispatches them when nothing better is
there. But a candidate skipped first waits, and these waited for two sections
derivable from numbers the issue had already measured.
All three shapes now carry them from one shared
scenario_and_requirements():Verified against the Swift predicates rather than by eye —
## Boundary,**given**/**then**,## Requirementswithmust, anacceptance criteriaheading — all four true forsingle_issue,part_issuesand theuntested feeder.
This does not make the work easier. It makes the issue legible to the policy
that was already reading it.
🤖 Generated with Claude Code