Repository navigation
Judge violations with a probability cutoff and expose example presets - #2
Merged
Merged
Conversation
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
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
Judge each change with one boolean question and a violation probability. A finding is emitted when that probability meets the rule's cutoff. Lower scores produce no finding; known missing evidence, partial evidence limitations, and inference errors still produce incomplete checks. Binary answers do not trigger extra model calls based on uncertainty.
Expose
prepareExamplesso model testers can replay exact initial, expanded, and partial evidence packets from labeled fixtures. Preparation uses disposable Git repositories, makes no inference calls, and keeps expected labels outside model input. Document calibration and model-tester integration for agents. Existing custom outcome/confidence evaluators remain supported; increment the protocol version to invalidate cached judgments.Validation
npm run check: 52 tests passed, covering threshold boundaries, raw probability caching, incomplete evidence/errors, preparation parity, and cancellation cleanup.npm pack --dry-run --jsonpassed.Version prepared as 0.3.0; not published.