Repository navigation
feat: reach scenarios — test how a change is met, not only what it is given (v0.19.0) - #14
Merged
Merged
Conversation
… given (v0.19.0) The per-requirement floor varies the input through the caller a change was built against. Each change now also runs three reach scenarios: another caller of the same behavior (entry), a record the change did not create (state), and a condition no requirement names (context), picked from a new plan.md Reach list of every caller found across repositories and tiers. Refusing input existing callers send is named a contract change and trips the plan gate; the adversary blocks a new refusal with no caller check; and profile: strict coverage requires a check or gap per reach axis.
… can co-occur A state scenario that acts on seeded data skips the return trip where the product rebuilds the request, and single-axis runs miss a defect that needs two axes at once. The verifier now reaches the picked state the way a user does (earlier step, leave, return, continue) and also runs picks that can happen in one real use together; plan.md's Reach records both.
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.
Why
The verifier's per-requirement floor (happy, boundary, negative) varies the input and runs through the caller the change was built against. A change can pass all of it and still fail for a second caller of the same behavior that sends an older or smaller request. Origin: a fix whose new validation refused a request another screen had always sent.
What
entry(another caller — the one whose request differs most), onestate(a record the change did not create), onecontext(a condition no requirement names). Named<id>.entry|state|context; an empty axis gets a gap line.- Reach:line in intent.md.tripwire.shpattern, plan Gate tier readspublic API/contract.profile: strictcoverage requires a proving check or gap per reach axis (reach.<axis>uncovered otherwise).Verification
gates/selftest.sh→SELFTEST PASS.main(contract wire not tripped; strict coverage passed with no reach scenario) and pass here.Upgrade note
profile: strictfeatures need three more check/gap lines (entry, state, context). Advisory recipes, records, and gate formats are unchanged.