Fetching from the wire…
Public story · 2026-08-17 · high
The paper names the failure count-scale drift and says the fix is arithmetic: pool calibrated log-likelihood ratios, not raw weights.
Why now: Covered in the August 17 briefing, the timing is a nudge to recheck any scoring system that has grown its source list since its threshold was set.
A paper names a bug baked into every score-summing detector: the threshold slides as you add sources, per arXiv 2608.14509.
Any system that scores risk by summing weighted signals and checking the total against a cutoff carries the same flaw. The drift grows as source reliability varies, and no fixed threshold works across every mix of sources.
The paper separates two jobs most systems fuse: reading a single source, and combining several readings into one call. It proposes a four-field evidence format as the boundary between those steps.
When sources carry different reliability, a majority-vote rule and a posterior-probability rule rank the same evidence in different orders. No single threshold reconciles the two, the paper finds.
The fix doesn't need a rebuild. Pool calibrated log-likelihood ratios instead of summing raw weights, and the threshold stops sliding as sources get added. The same weakness sits inside score-summing triage engines and additive multi-signal detectors.
If your scoring system sums weights and thresholds the total, look at when that threshold was tuned. It was probably tuned for fewer sources than you're running now.
Each link below shares sources, entities, or timing with this story.
A synthetic benchmark constructs conflicts where exactly one evidence source matches ground truth, independently varying modality, recency, stated reliability, and provenance. Across open-weight instruction-tuned models the arbitration is systematic: distinct text-versus-numbe...
Li, Huo, and Johnson show that one-way message flow between agents produces neither mimicry nor solo behavior but an entirely novel dynamical state, at identical temperature settings. It's conceptual rather than quantitative, but the implication for orchestrator-worker fan-out...
This one rearranged my week. An essay published August 4 walks through Databricks' independent benchmark of coding harnesses against its own multi-million-line codebase. Pi, a harness with four built-in tools and a system prompt under 1,000 tokens, paired with Opus 4.8 at xhig...
Agent Lightning v1.0 (arXiv 2608.17528) inverts the standard agentic RL architecture, and the inversion is the whole point. Normally the training engine owns the environment loop. It drives the agent, collects trajectories, computes rewards. Which means your training setup and...
Load Hijack modifies nothing but router weights in a checkpoint. When a private trigger appears, token-to-expert assignment concentrates on experts co-located on a single GPU, making it a straggler while peers idle (arXiv 2608.10614). Across three MoE families and four corpora...
When an agent consolidates an external observation into long-term memory, attach platform-controlled metadata recording the source's trust level, then gate tool execution by matching action risk against supporting-memory authority. Laundered memories hit a 1.000 attack success...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.