Repository navigation
feat(runner): route external privacy restrictions - #926
Draft
afourniernv wants to merge 1 commit into
Draft
afourniernv wants to merge 1 commit into
afourniernv wants to merge 1 commit into
Conversation
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 was referenced Oct 11, 2026
afourniernv
removed this pull request from stack #934
October 11, 2026 21:57
afourniernv
force-pushed
the
codex/privacy-external-signal
branch
from
October 11, 2026 21:59
38f33be to
869a2c3
Compare
afourniernv
added this pull request to stack #966
October 11, 2026 21:59
Signed-off-by: Alex Fournier <afournier@nvidia.com>
afourniernv
force-pushed
the
codex/privacy-external-signal
branch
from
October 11, 2026 22:08
869a2c3 to
69fa69f
Compare
This branch has not been 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
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.
Privacy stack 3/9. Depends on #925. Next: #927.
What
Allow an embedded Rust host to mark a request as restricted. Routes explicitly opt in with
accept_external_signal; restricted execution uses only existing targets flaggedprivate = true.Why
Hosts can supply their own classification without Switchyard owning detection. The configured router still chooses among the allowed targets.
How tested
Runner tests passed for opt-in, target filtering, required roles, fallbacks, and auxiliary calls.
The complete stack also passed workspace tests, strict clippy (including prefill), formatting, and 187 Python tests. No live provider calls.
Notes for reviewers
Adds
mark_privacy_restricted(&mut Request)and the route'sprivacyTOML section. The marker is in-process only, not an HTTP header.Restricted construction preserves weights and required roles. Forward-auth privacy deployments are rejected; mixed routes reject Responses continuation requests. No built-in pattern detectors.