feat: evaluate policy revisions on retained datasets - #17
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
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.
Run versioned encrypted JSONL datasets against the same engine as the gateway. Add comparisons, confusion matrices, latency/cost accounting, cancellation/resume, scoped reports and explicit paid-provider consent. Include dashboard/CLI controls and a reproducible local regression fixture.
Validation: Workspace checks and 20 local synthetic cases passed. No real-provider accuracy or cost benchmark is claimed.
This is a stacked PR. Review this diff against
codex/review-inbox; merge its dependency first. The website and final standalone CLI changes follow separately.