Skip to content

feat(runner): isolate restricted decision targets - #927

Closed
afourniernv wants to merge 1 commit into
codex/privacy-external-signalfrom
codex/privacy-decision-isolation
Closed

afourniernv wants to merge 1 commit into
codex/privacy-external-signalfrom
codex/privacy-decision-isolation

Conversation

@afourniernv

@afourniernv afourniernv commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

Draft stack 4/10.

What

Allow a privacy route using a typed decision judge to configure a separate decision target for its restricted lane.

Why

Remapping only answer targets is not enough. A restricted request must not consult the standard lane's decision service before routing.

How tested

Configuration tests cover valid lane-specific decision targets, missing restricted targets, and unknown target references. The complete stack passed workspace formatting, Clippy with warnings denied, and workspace tests. No live provider calls.

Notes for reviewers

Adds the TOML field privacy.restricted_decision_target.

No public Rust, Python, HTTP, or ABI changes.

Signed-off-by: Alex Fournier <afournier@nvidia.com>
@afourniernv
afourniernv added this pull request to stack #934 October 6, 2026 18:18
@afourniernv

Copy link
Copy Markdown
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.

@afourniernv afourniernv closed this Oct 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant