Conversation
… the autopilot carries the rest before the tag (#3459) Part 2 of #3459, per the cop's ruling (the narrowing is approved on condition that nothing is silently left behind): - check_milestone_cut.sh --must-carry: RED only on an open issue labelled must-carry; every other open item is listed TO CARRY. Strict mode is unchanged, and it stays the final gate: a tagged milestone with ANY open item is RED (new self-test row S27: an unlabelled open issue left in a milestone is RED under strict). - scripts/release/carry_milestone_items.sh (new): moves every open non-must-carry item to the next release's milestone when that release's "EPIC: release train <next>" lists it, otherwise to `backlog`, each with a one-line slipped_from comment. It refuses (rc 1, writes nothing) while any must-carry issue is open. - autopilot.sh cut_tag: must-carry verdict -> carry -> strict verify (the existing call, byte-identical) -> tag. The move lives in the autopilot; the gate only verifies. - check_tag_step_gated.sh: asserts that order, that must-carry rc 1/2 and carry rc 2 never tag, and adds mutants M4 (must-carry verdict discarded) and M5 (carry call deleted); both turn it RED. Label `must-carry` created on paiml/aprender ("Blocks the release cut of its milestone (check_milestone_cut.sh)"). Refs #3459 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…pro-high + sonnet-5 + haiku-4-5, one brief) Evidence only; the judged diff is 9a6bc00. Sonnet nit 1 (--json gains mode/to_carry in strict mode; the verdict is unchanged) is recorded in the claude-lanes sidecar, per the cop. Nit 2 is filed as its own ticket. Refs #3459 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
noahgift
enabled auto-merge
September 24, 2026 07:43
Contributor
Author
|
Cop (aprender-cf) armed at 5c3e35b as a recorded override. receipt-lint does not yet accept the new shape.
|
|
§13.11 rung 1 — quorum shadow verdict Shadow mode: this records a verdict and merges nothing. A refusal |
This was referenced Sep 24, 2026
Contributor
Author
|
folded into #4317 (emergency fold, operator 2026-09-24) |
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
1 participant
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.
#3459 part 2: the must-carry universe. Part 1, the gated in-repo tag path, landed in #3617.
check_milestone_cut.sh --must-carry: RED only on an open ISSUE labelledmust-carry, never on a PR. Everything else is listed TO CARRY. Strict mode is unchanged. New self-test rows S24–S29; S27 checks that an unlabelled open issue under strict is RED.scripts/release/carry_milestone_items.sh: moves each open non-must-carry item to the next release's milestone when its epic lists the item, otherwise tobacklog, each with a slipped_from comment. It refuses, writing nothing, while any must-carry issue is open.autopilot.sh cut_tagruns the must-carry verdict, then carry, then the existing strict verify (byte-identical), then the tag.check_tag_step_gated.sh: asserts that order. New mutants M4 and M5 both turn it RED.Scope and measurements:
docs/audits/impl-PMAT-3459-receipt.md.Quorum: 3/3 PASS at 9a6bc00 with gemini-3.1-pro-high, claude-sonnet-5 and claude-haiku-4-5, all on one brief, sha256 689025e6…. The evidence-only child commit is
docs/audits/quorum-PMAT-3459-part2.*. Follow-up nit: #4176.Refs #3459
🤖 Generated with Claude Code