Repository navigation
fix(ratchet): R4-carve discipline recognizes Class P legitimate-carve channel - #2442
Merged
Merged
Conversation
… channel CI failure on main caught real ratchet drift. Brief at docs/briefs/r3-evaluator-tc3-d4-eval-step-producer-worker.md:121 flagged: "(α)/(β) novel-substrate-introduction explicitly carved to R4+ via Class P partition (Debt-Paydown PR #2437)" — line uses "carved to R4+" anti-pattern but framing IS structurally legitimate (routes through Class P, the new past-R3 channel introduced via Debt-Paydown lane scope expansion at PR #2436 + Class P populated at PR #2437). Pre-Class-P, the ratchet's permitted markers covered: - pre-2026-05-09 carve framings (DISSOLVED, AMENDED 2026-05-09, etc.) - supersession annotations (formerly, prior, historical, supersede) Post-2026-05-09 legitimate carve channel via Class P was missing from permitted markers. Going forward, R4+ work should route through Class P (Debt-Paydown lane scope), not via direct C1/C2/C3 carves (which were dissolved 2026-05-09). Fix: extend PERMITTED_MARKERS with Class P / past-R3 / R3 close cycle exit / R4+ via Class P / Debt-Paydown patterns. Also add self-test case pinning Class P recognition (4 → 5 self-test cases). **Verification**: - Self-test 5/5 passing (incl. NEW Class P case) - Tree check: 33 citations, all properly annotated (was 32; +1 Class P citation in TC3 D4 brief now recognized as legitimate) **Note on PR #2441 silent failure**: PR #2441 merged at 21:46:56Z WITH ci=FAILURE. Branch protection did not enforce CI as a hard merge block. This is operator-tier (branch protection rules need updating); PM surfaces but cannot fix. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 9, 2026
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.
Summary
CI failure on main caught real ratchet drift. Brief at
docs/briefs/r3-evaluator-tc3-d4-eval-step-producer-worker.md:121flagged:Line uses "carved to R4+" anti-pattern but framing IS structurally legitimate — routes through Class P (the new past-R3 channel introduced via Debt-Paydown lane scope expansion at PR #2436 + Class P populated at PR #2437).
What changed
Pre-Class-P, ratchet's permitted markers covered:
DISSOLVED,AMENDED 2026-05-09, etc.)formerly,prior,historical,supersede)Post-2026-05-09 legitimate carve channel via Class P was missing. Going forward, R4+ work should route through Class P (Debt-Paydown lane scope), not via direct C1/C2/C3 carves.
Extension: PERMITTED_MARKERS now includes:
Class P/class P/past-R3/past R3R3 close cycle exitR4\\+ via Class PDebt-Paydown/debt-paydownPlus self-test case pinning Class P recognition (4 → 5 cases).
Verification
Note on PR #2441 silent CI failure
Operator action needed: PR #2441 merged at 21:46:56Z WITH
cijob FAILURE. Branch protection did not enforce CI as a hard merge block. The ratchet IS working correctly; the gap is in the merge-policy enforcement layer (GitHub branch protection rules).PM surfaces this; cannot fix — branch protection requires repository-admin authority.
🤖 Generated with Claude Code
SG-0 hand-path delta: +0