Repository navigation
feat(eval): surface final_response_match_v2 judge reasoning and pass rubric rationale through details - #279
Merged
Conversation
…rubric rationale through details
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.
final_response_match_v2failures now explain themselves. ADK asks the judge for its reasoning and then drops it. A small subclass of ADK'sFinalResponseMatchV2Evaluatorkeeps that reasoning and returns it as a rubric score (rubric_id: final_response_match). The score is still ADK's own label parsing. Remove the subclass once ADK returns the reasoning itself.MetricResult.detailsnow carries rubric scores and rationale for any metric that returns them, not onlyrubric_based_*. This also adds rationale tosafety_v1andmulti_turn_*, which ADK already returns. Metrics that return no rubric scores keepdetails: null. No score, status, threshold or aggregation changes.The CLI table and the UI do not show the rationale yet. Use
-o json, the API or gRPC.