Repository navigation
feat(rag): opt-in experimental Hybrid ask with evidence gate - #84
Merged
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
/rag/askpath. Dense remains default; Ticket Agent and the original Dense 0.9 distance policy are unchanged.RAG_HYBRID_SEARCH_ENABLED, new default-falseRAG_HYBRID_ASK_ENABLED) plus requestretrieval_mode=hybridandrefusal_policy=v5_3_experimental. Rejectmax_distanceon Hybrid rather than silently applying or ignoring a distance threshold. Hybrid defaults to Top14; Dense remains default3/max10.Verification
ruff check ., in-memory Python compilation andgit diff --checkpassed. Primary checkout's existing changes left untouched.Explicit boundaries
This is runtime wiring for an off-by-default experiment, NOT v5.3 promotion or independent semantic-quality acceptance. Historical NO_PROMOTION / FAIL conclusions are unchanged. Valid evidence locators/source IDs do not prove entailment, faithful generation or prompt-injection resistance. It does not replace default refusal or create tickets.
Actual provider execution of the newly added classifier/generator path and controlled answer/refusal acceptance remain pending separate data-egress/cost authorization. The previous 8 embedding + 3 rerank smoke authorization is not reused.