-
-
Notifications
You must be signed in to change notification settings - Fork 35
fix(arbitration): resolve issue #174 first-response bias #225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
shrixtacy
merged 1 commit into
shrixtacy:master
from
savanigit:fix/issue-174-arbitration-resolution
Mar 31, 2026
+160
−39
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: shrixtacy/Ai-Council
Length of output: 1694
🏁 Script executed:
Repository: shrixtacy/Ai-Council
Length of output: 1668
🏁 Script executed:
Repository: shrixtacy/Ai-Council
Length of output: 1548
🏁 Script executed:
Repository: shrixtacy/Ai-Council
Length of output: 1879
🏁 Script executed:
Repository: shrixtacy/Ai-Council
Length of output: 1734
🏁 Script executed:
Repository: shrixtacy/Ai-Council
Length of output: 1145
Fix the ranking in
_resolve_confidence_conflictto prioritize confidence over quality.The helper
_select_best_response_for_conflictranks responses with(quality_score, confidence_score), making quality the primary decision axis. This causes_resolve_confidence_conflictto select a lower-confidence response if it has better risk/length/assumption metrics, contradicting its documented behavior of "choosing the most confident response". The returned reasoning ("selecting response with highest confidence score") is also inaccurate.Examples: A response with 50% confidence but better risk/length scores beats one with 95% confidence but worse non-confidence metrics.
Update the helper to accept a
rankingparameter (or create a separate confidence-first variant) so_resolve_confidence_conflictcan useconfidence_scoreas the primary key instead ofquality_score.Example fix
def _select_best_response_for_conflict( self, conflict: Conflict, responses: Optional[List[AgentResponse]] = None, + ranking_key: str = "quality", ) -> Optional[AgentResponse]: # ... candidate selection logic ... - return max( - candidates, - key=lambda r: ( - self._calculate_quality_score(r), - r.self_assessment.confidence_score if r.self_assessment else 0.0, - ), - ) + if ranking_key == "confidence": + return max( + candidates, + key=lambda r: r.self_assessment.confidence_score if r.self_assessment else 0.0, + ) + + return max( + candidates, + key=lambda r: ( + self._calculate_quality_score(r), + r.self_assessment.confidence_score if r.self_assessment else 0.0, + ), + )Then call from
_resolve_confidence_conflict(...)withranking_key="confidence".📝 Committable suggestion
🤖 Prompt for AI Agents