Conversation
|
Signed-off-by: adhaile <adhaile@nvidia.com>
gburachas
force-pushed
the
vgr/review/01-capabilities
branch
from
September 30, 2026 19:18
47b2cd7 to
c0cc1fb
Compare
gburachas
force-pushed
the
vgr/review/02-policy
branch
from
September 30, 2026 19:19
00fce77 to
a3905e8
Compare
This was referenced Oct 1, 2026
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
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.
What
Adds the decision policy for verification-gated routing, building on the capabilities introduced in #716. It combines verifier scores, yes/no verdicts, and tool-result history to decide whether to accept the local attempt or escalate to the capable tier.
It also adds verifier request builders, verdict parsing, and a probability readout from OpenAI Chat logprobs.
Why
Each verification branch needs explicit acceptance rules. A factual answer can be checked directly, while an agentic result also needs evidence that tool failures were resolved. Keeping these rules separate from execution makes the policy reviewable without following model calls or streaming behavior.
Notes for reviewers
Review this against #716. Start with
decideincrates/libsy/src/algorithms/vgr/decide.rs, then readreadout.rsandrungs.rs.logprobsalongside the already-supportedtop_logprobs.This PR defines policy and verifier inputs. #718 connects them to runtime execution.