Provenance

TL;DR for operators Dividing a high-stakes decision among specialist agents does not specify who may see which evidence, who owns each subdecision, or who can revise it. HiMA-MDD1 turns those choices into explicit system rules for PHQ-8 assessment from completed multimodal clinical interviews. The strongest architectural signal is not “more agents perform better.” Before global verification, four specialists produce the lowest total-score error, while two specialists produce the highest screening kappa and Macro-F1. Removing cross-factor audit and targeted revision causes the largest screening-performance decline among the paper’s three component ablations. Giving four specialists bounded item-specific evidence also beats giving them a capped shared evidence pool on every reported pre-verification metric, although that experiment changes both evidence composition and context length. ...

TL;DR for operators If an AI coding assistant can install software, do not assume it will inspect the evidence already available about where that software came from. In Pengyin Shan’s pre-registered demand-side audit,1 only 9 of 1,920 registered trials retrieved a relevant trust signal before the install-or-decline decision. Across 2,114 completed registered and supplementary trials, not one assistant executed a signature or attestation verification command. ...

TL;DR for operators A research assistant answers a question you give it. A more autonomous scientific system can propose a hypothesis, criticize it, run analyses, compare outcomes, and decide whether another iteration is warranted. Once these functions are coordinated, the operational unit is no longer a model call. It is a discovery loop. ...

TL;DR for operators An analytical agent can select an appropriate tool, complete a computation, and return a plausible result while still being wrong at the point that matters operationally: deciding whether the result should be trusted, reported, stored, or used to launch further automated work. Brain Researcher addresses that later decision by making the research episode—not the model response—the governed unit of work. It constrains available resources, records provenance, tests alternative defensible specifications, assigns explicit states to scientific claims, and controls which results are eligible to enter memory. The paper reports a large improvement in first-action tool routing, from 23.3% without the system to 93.6% with it. Yet verified evidence grounding reaches only 22.0%, and an automated scientific-review layer still missed a scoring error that required human detection. ...

TL;DR for operators The paper addresses a problem that appears after literature retrieval succeeds. A research organization may already have the relevant papers and may even have extracted the reported measurements, yet those observations can still be unsafe to combine because material names, property definitions, units, temperatures, methods, and other conditions do not align. ...

TL;DR for operators A retrieval system can answer only the questions a user thinks to ask. That becomes a design constraint when the user’s main problem is not missing information but missing awareness that information is missing. VeriForge addresses this by giving AI initiative over discovery while leaving the writer in control of synthesis. In a study of 12 writers, blind-spot alerting averaged 6.33 with VeriForge versus 3.00 with a strengthened baseline, and 11 of 12 participants rated VeriForge higher. Creativity support, exploration behavior, and expert-rated perceived domain competence also improved after statistical correction.1 ...

TL;DR for operators When an agent discovers that a stored customer preference, prior observation, or workflow fact was wrong, deleting that record may be too late. The faulty information may already have shaped a plan, triggered a tool call, entered the final answer, or created new persistent memories. Yu et al. propose a repair mechanism that follows those dependencies rather than resetting everything.1 On their 150-case controlled benchmark, it recovered 85.3% of cases, compared with 77.3% for LLM-judge repair, while reducing the replay ratio from 21.7% to 12.3% and average LLM calls from 9.80 to 5.70. ...

TL;DR for operators A scientific poster can look polished and still fabricate the plots or diagrams readers interpret as evidence. PosterHarness separates those responsibilities: the image model designs the layout and decides where evidence should appear, but it must leave those regions blank for source-paper figures to be inserted later by deterministic code. ...

TL;DR for operators Generated images may carry a more durable signature than most teams assume. Not a cute watermark. Not a metadata tag. Not a visible logo hiding in the corner like a nervous intern. A model-level statistical signature. The paper Guess the Unified Model: How Much Can We Recover from Generated Images? studies whether images produced by unified multimodal models can be attributed back to the model that generated them.1 The authors train a ConvNeXT classifier to identify the generating model from images produced by five open-source unified models, then extend part of the analysis to include two closed-source systems. The core result is blunt: attribution works surprisingly well. With 100 training images per model, accuracy is already 36% in a five-way task where chance is 20%. With 3K images per model, it reaches 93.9%. With 25K images per model, it reaches 99.9%. ...

TL;DR for operators RAGA is not another “add a graph and accuracy goes up” paper. That would be too convenient, and therefore suspicious. The useful idea is more operational: treat retrieval-augmented generation as a knowledge management process, not a pile of embeddings with a polite chatbot on top. The paper proposes RAGA, short for Reading-And-Graph-building-Agent, an autonomous system that reads documents, searches existing graph knowledge, verifies whether new entities or relations should be added, and then constructs or updates a knowledge graph with source-linked provenance.1 Its core loop is Read–Search–Verify–Construct, implemented as a ReAct-style tool-calling agent rather than a one-shot extraction pipeline. ...