Structure Before Intelligence: Gating What Agentic Scientific Workflows Release
On the map: LLM agents and tool use → Software engineering coding agents
Abstract (arXiv)
An agentic scientific workflow can run to completion and still release wrong results: a silent numerical error, a stale input, or a defect in a shared upstream step can contaminate several outputs while a sibling branch stays correct. We treat trust in such results as a release decision. A harness around the workflow's directed acyclic graph (DAG) decides which outputs may be used: it enforces mandatory checks, contains failures to the affected branch, recomputes from tracked versions, adds validators, and releases a result only if a risk model estimates its probability of being invalid as low. Language-model agents work inside the harness, choosing corrective actions and reviewing releases, but cannot override it. On 60 held-out paired instances of two workflows with injected faults, we switched components on and off. Each supplied a different property. Containment and recovery raised the number of correct results. Validation supplied safety: fixed rules without validation released 37 invalid results, while validating every candidate released none. Risk estimation supplied efficiency, matching that safety with 31% fewer validators at somewhat lower yield, although better targeting than random validation was not shown. Lineage evidence helped on one workflow. The language model added no measurable benefit: whether invalid results escaped depended on the harness, not the model. This proof of concept points to a practical path: placing agents inside explicit release-control structure can keep released scientific results trustworthy, and it gives more capable agents a measurable baseline to improve on.
Key facts. No citing papers in the map yet (data through 14 Oct 2026). Placed in Software engineering coding agents, one of 16 directions in LLM agents and tool use. Builds on 12 of its 37 references that are in the map. First posted on arXiv 14 Oct 2026.
Builds on
12 of 37 references.
Closest ancestors · 1
Same direction, newest first
Other references · 11
- 2023Judging LLM-as-a-Judge with MT-Bench and Chatbot Arenacited by 8,626
- 2023Large Language Models are not Fair Evaluatorscited by 1,085
- 2024The AI Scientist: Towards Fully Automated Open-Ended Scientific Discoverycited by 1,071
- 2017Selective Classification for Deep Neural Networkscited by 852
- 2025PaperBench: Evaluating AI's Ability to Replicate AI Researchcited by 321
- 2021Learn then Test: Calibrating Predictive Algorithms to Achieve Risk Controlcited by 271
- 2025AgentSpec: Customizable Runtime Enforcement for Safe and Reliable LLM Agentscited by 223
- 2024CORE-Bench: Fostering the Credibility of Published Research Through a Computational Reproducibility Agent Benchmarkcited by 123
- 2025Securing AI Agents with Information-Flow Controlcited by 121
- 2025BixBench: a Comprehensive Benchmark for LLM-based Agents in Computational Biologycited by 89
- 2015Shield Synthesis: Runtime Enforcement for Reactive Systemscited by 42
Built on by
Not cited yet.
Similar, not cited
Close in wording, no citation either way
- 2026Correct Is Not Governed: Provenance Integrity in Agentic Workflows
- 2026AgentEval: DAG-Structured Step-Level Evaluation for Agentic Workflows with Error Propagation Tracking
- 2026Plausible but Wrong: A case study on Agentic Failures in Astrophysical Workflows
- 2026Trace-Level Analysis of Information Contamination in Multi-Agent Systems
- 2026Evaluating Agentic Bioinformatics through Function, Evidence, and Validation
- 2026GraphFlow: An Architecture for Formally Verifiable Visual Workflows Enabling Reliable Agentic AI Automation
- 2026REVISE: Validity-Guided Recovery for Online Revisions in Agent Workflows
- 2026Mnemosyne: Agentic Transaction Processing for Validating and Repairing AI-generated Workflows