fix(privacy): add value-blind public source gate - #76
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
Add a value-blind privacy gate for this public repository and remove private identity details from current operational authority where they are not required.
Validation
scripts/validate-repo.shpasses in the CI-shaped non-TTY execution environment.git diff --checkpasses.External / optional checks
The public gate does not claim knowledge it does not possess.
Optional private-denylist validation, root-policy linkage, and the producer differential remain explicitly
not_rununless their operator-controlled external inputs are supplied.Scope
This PR does not:
Those concerns remain separate.