Promote FEAT-067 to accepted — v3.3.0 not-ready 5 → 4 - #189
Merged
Conversation
Merged in #188 with 13/13 CI green; its two oracles re-run on main. AC1 is met: filtering by class / code / function / operator / gap-kind returns only matching records, each carrying its stable obligation id. Mutation-checked three ways, each asserted to apply to one site AND to compile. One of those mutants had to be redone after producing invalid Rust and no test output -- an unmeasured mutant, not a surviving one. Safe to promote now that REQ-020 carries its own measured NOT-SATISFIED record (#186): FEAT-067 traces to REQ-020, and before that record existed this promotion would have left REQ-020 looking closer to satisfied than it is. rivet=0 claim-check=0 fmt=0 drift-gate=0. Claude-Session: https://claude.ai/code/session_01KkNzkNYzPh7366DkNijeNc Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
📐 rivet artifact deltaPR: #189 Base SHA: Validationhead — `rivet validate` resultbase — `rivet validate` result (for comparison)Artifact stats
full stats — headDiff (base → head)AADL model — headPosted by the |
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.
Merged in #188 with 13/13 CI green; its two oracles re-run on
main.AC1 is met: filtering by class / code / function / operator / gap-kind returns only
matching records, each carrying its stable obligation id.
Mutation-checked three ways, each asserted to apply to exactly one site and to
compile. One mutant had to be redone after producing invalid Rust and no test output —
an unmeasured mutant, not a surviving one.
Why this promotion is safe now and wasn't before
FEAT-067
traces-toREQ-020. Before #186 recorded REQ-020's measured NOT-SATISFIEDstate, promoting a feature that traces to it would have left REQ-020 looking closer to
satisfied than it is — the exact asymmetry that produced four drifted claims this
session: evidence lives in the feature's ACs, the claim lives on the requirement, and
nothing links them.
Recording the limit first, then promoting, is the ordering that keeps both honest.
rivet=0 claim-check=0 fmt=0 drift-gate=0🤖 Generated with Claude Code
https://claude.ai/code/session_01KkNzkNYzPh7366DkNijeNc