Implement Slice Nine structured PERSON discovery and protection - #12
Merged
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
This branch was successfully deployed
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.
Objective
Add model-free PERSON discovery and protection for parsed JSON records. A record such as
{ "first_name": "May", "last_name": "Nguyễn" }now produces path-qualified PERSON findings and can be redacted through the existing transformation policy, without requiring caller mappings for supported field names.Changes
namefields require an explicit PERSON mapping.docs/structured-performance.md.Existing text APIs retain their seven-detector coverage. No new third-party dependencies, models, or dictionaries are introduced. Local artifact measurements show approximately 16.5% growth for the Python extension and 8.9% for the Node native module; the measurement notes explain workload and cold-start limitations. This implements schema-guided name protection; it does not claim arbitrary name recognition in prose. Package publication and migration of the current MCP consumer remain pending.
Verification
cargo fmt --all --checkcargo clippy --workspace --all-targets --all-features -- -D warningscargo test --workspace --all-features— 76 tests passedLocal binding verification used macOS ARM64, Python 3.14.6, Node 24.19.0, and Chromium. Rust used toolchain 1.88.0. Cross-platform CI results should be evaluated separately from these local checks.