Repository navigation
Conversation
…s measures it (#5451) specs/queen/dispatch.t27 stopped at review_state accept and said nothing about what reaches master, so the owner's rule of 2026-10-01 lived only in tools/queen/publish.py, unmeasured by the spec's own harness. - PUBLISH_RULE, and f65 [publish]: of 5 verdicts x 6 head relations x 2 parent-commit kinds, the publisher arms exactly the accepts at the judged head (or under its own docs/now-only commit over it). - trinity_queen_dispatch.py: a sixth evidence kind, `publish`, which loads the publisher's own accepted_at and drives all 60 shapes on every `check`. Three planted publishers must each fail --self-check: one that arms any accept, one that arms any verdict at the judged head, one that never asks what the commit over the judged head touched. - Replay re-run (2488/2488); the seal is re-saved for this spec only. Why now: of 554 merged bee PRs, 515 carry no accept from her. #5183 merged with her verdict `escalate` and replaced tools/check_seal_coverage.py with one comment line. Closes #5451 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
This was referenced Oct 1, 2026
Merged
This was referenced Oct 6, 2026
Merged
Merged
Merged
Merged
This branch has not been deployed
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 #5451
specs/queen/dispatch.t27stopped atreview_state acceptand said nothing about what reaches master. The owner's rule of 2026-10-01 (her accept IS the merge, and nothing else is) lived only intools/queen/publish.py(#5422), so the spec's own harness never measured it.What changes
PUBLISH_RULE, and finding f65[publish]: of 5 verdicts × 6 head relations × 2 parent-commit kinds, the publisher arms exactly the accepts at the judged head, or under its own docs/now-only commit over that head.tools/trinity_queen_dispatch.pygets a sixth evidence kind,publish. It loads the publisher's ownaccepted_atfrom this checkout and drives all 60 shapes on everycheck. There is no record to go stale.--self-check: three planted publishers must each fail.Evidence (local, t27c built from master's
bootstrap/)Why now: an audit of every merged
queen-*PR against her verdict on its issue.escalateand replacedtools/check_seal_coverage.py(688 lines) with one comment line.🤖 Generated with Claude Code