Add nadir-caliper-2: consult-only arbiter (supersedes pending nadir-caliper #173) - #174
Closed
doramirdor wants to merge 1 commit into
Closed
Add nadir-caliper-2: consult-only arbiter (supersedes pending nadir-caliper #173)#174doramirdor wants to merge 1 commit into
doramirdor wants to merge 1 commit into
Conversation
… nadir-caliper, PR RouteWorks#173) One branch changed from nadir-caliper: where grok-4.3 confirms neither probe, ship qwen instead of grok. RouterBench-only evidence: that branch selects questions all models fail (grok 12% vs qwen 15% correct), so the premium answer bought no accuracy at 25x the price. grok-4.3 becomes consult-only. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
Author
|
/evaluate |
Router Evaluation ResultsRouter: RouterArena Metrics
Evaluation completed by RouterArena automated workflow |
Contributor
Author
|
The evaluation answered the question this PR existed to ask: nadir-caliper-2 scores 74.10 vs nadir-caliper's 74.55, so the branch change is a measured regression on this dataset (the arbiter's answers on the no-confirmation slice are worth ~13pp there, unlike on RouterBench where we measured them at ~0). Per the decision rule stated in the PR body, we accept the evaluated outcome: withdrawing this submission and closing the PR. #173 (nadir-caliper) remains Nadir Lab's intended entry. Both artifacts and both evaluations stay public for anyone auditing the comparison. Thanks for the compute, and apologies again for the churn. |
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.
Submission from Nadir Lab (https://getnadir.com, https://github.com/NadirRouter, info@getnadir.com).
This supersedes our pending
nadir-calipersubmission (#173) and, like it, thenadir-tumblerleaderboard entry. One Nadir Lab row, please, with affiliation shown as Nadir Lab linking to https://getnadir.com. We are intentionally replacing a submission whose evaluation we have already seen (74.55) with a variant we have not: our RouterBench-only branch analysis, documented in the config description and committed before this PR, says this version dominates it. We accept the evaluated outcome either way.The one change from nadir-caliper
Identical menu, probes, arbitration, and provenance. The only difference: where grok-4.3 confirms neither probe (the hardest 16% of traffic), the router ships qwen instead of grok. On our RouterBench labels that branch selects questions every model fails (grok correct 12%, qwen 15%), so the premium answer bought no accuracy at 25x the price. grok-4.3 is consult-only in this version and is never shipped; the >=30% downroute constraint is trivially satisfied at 100%.
Cost fields sum to $0.418165 ($0.0498/1K) at current
model_cost.jsonprices from recorded token usage. The robustness file is a genuine re-run of the identical rule on all 420 perturbed prompts. Everything else (training-data policy, contamination audit, per-row provenance on 2026-08-05 generations, the grok-4.3 registry line) is unchanged from #173.Files
router_inference/config/nadir-caliper-2.jsonrouter_inference/predictions/nadir-caliper-2.json(8,400 rows)router_inference/predictions/nadir-caliper-2-robustness.json(420 rows)universal_model_names.py(same one-line grok-4.3 registration as Add nadir-caliper: consensus-verified cascade from Nadir Lab (true grok-4.3 prices; supersedes nadir-tumbler) #173)Both
check_config_prediction_files.pygates pass locally. Contact: info@getnadir.com.🤖 Generated with Claude Code