feat(sensitive): bind model prompt and token policy - #77
Draft
seonghobae wants to merge 4 commits into
Draft
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Aug 11, 2026
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.
Partial implementation of #10, stacked on PR #75.
Buyer/security gap
Issue #10 requires any sensitive-data model disclosure path to bind a reviewed prompt contract, output schema, and bounded token budget in addition to the already active provider/model/region/retention/training/subprocessor/export route authority. A route match alone must not authorize an unbounded or differently shaped model invocation.
Dependency
This Draft is stacked on unchanged exact PR #75 head
286f92aae9e298ab7dff1fd81c7850aabd5692ceand must remain Draft while #75 and its sensitive-handle prerequisites remain active.TDD and implementation state
The original test-only head
8099a24093407ac0e69f9530d180da5f90e592faestablished the missing production boundary. Exact current headadb67f8de3e4828db14dfa0e2950b672b60709c5now implements and exposesModelInvocationRequest,ModelInvocationScope,ModelInvocationDecision, andevaluate_model_invocation.The production evaluator:
ModelRouteDecisiondenial before invocation-specific checks;Exact-head CI run
31477512549completed successfully. The combined commit status currently reports CodeRabbit success, no formal reviews are returned, and no inline review threads are currently returned for this exact head. Predecessor-head evidence is not transferred.Truth boundary / remaining #10 work
Matching invocation metadata remains separate from raw-value disclosure, provider authentication, model execution, output validation, retention enforcement, expiry, conversation-history isolation, fallback selection, and export execution. In particular, this head deliberately does not provide invocation-policy expiry; Draft PR #79 carries a separate test-first expiry contract stacked on this exact head.
This PR must remain Draft until its dependency stack is integrated and fresh exact-head/live-base acceptance is re-established. It does not close #10.