Repository navigation
feat(runner): inspect privacy requests deterministically - #928
Closed
afourniernv wants to merge 1 commit into
Closed
afourniernv wants to merge 1 commit into
afourniernv wants to merge 1 commit into
Conversation
Signed-off-by: Alex Fournier <afournier@nvidia.com>
afourniernv
added this pull request to stack #934
October 6, 2026 18:18
|
Contributor
Author
|
Closing this draft stack for now. I’m sharing the cumulative branch and design/evaluation artifacts for architecture feedback before reopening a smaller stack. |
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.
Draft stack 5/10.
What
Add optional deterministic privacy checks for common personal data and credential patterns.
Inspection covers normalized and preserved request state within fixed byte, depth, and traversal limits. Opaque or oversized input is restricted rather than passed through.
Why
Many sensitive requests can be identified locally without adding a model call or its latency.
How tested
Tests cover the detector catalog, structured request fields, preserved provider bodies, split text, opaque content, and scan limits. The complete stack passed workspace formatting, Clippy with warnings denied, and workspace tests. No live provider calls.
Notes for reviewers
Configuration:
Adds
regexto the runner. No public Rust, Python, HTTP, or ABI changes.