Repository navigation
Data classes at every model boundary: no P2/DP30 to Jev or the task model (#13) - #16
Merged
Merged
Conversation
…odel (#13) policy.yaml gets `classification` (public < internal < P2 < DP30, class per tool, restricted terms with a class). Content above max_to_model / a model's max_class is withheld with the neutral barrier message; content above injection.jev.max_class (default internal) cannot be injection-checked, so its request is blocked. Classes come from the source, never the content; masking does not lower them; missing classes or limits fail closed; the whole history is re-classified on every request. Messages are skipped by Jev only once it has passed them, so replayed blocked prompts stay blocked. tests/test_classification.py checks what reached the model, Jev (incl. real HTTP payloads and retries) and the audit log. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Closes #13.
What
classificationinpolicy/policy.yaml:public < internal < P2 < DP30, a class per tool, and a class on restricted barrier terms (Falcon = DP30).max_to_model(P2), or a model's ownmax_class, is withheld with the neutral barrier message. Search results that mix classes keep the lower items.injection.jev.max_class: internal, never abovemax_to_model. P2 that the model may see but Jev may not cannot be injection-checked, so the request is blocked, whateveron_errorsays./metricscounts them with their latency.Demo impact (strict defaults, agreed)
injection.jev.max_classtoP2live restores the per-field quarantine flow.Tests
tests/test_classification.py(23 tests): synthetic business facts with nothing a regex can find; asserts on what reached the model, Jev (including realJevJudgeHTTP payloads through a mocked 429 retry) and the audit log. With the gate removed, 21 of 23 fail. Existing onboarding and demo-judge tests updated to the new behaviour. Full suite: all committed tests pass.Known limit
For history the gateway never saw, a tool result's class falls back to the tool name the agent claims (decisions.md D6).
🤖 Generated with Claude Code