From the Research Universities edition of November 3, 2026
From Tool State to Scientific Action: Auditing Decision Provenance in Biomedical Research Agents (BioAgent-DF)
INTOSYN AI Labs, with authors affiliated with Columbia University and Microsoft · Research enterprise (biomedical research agents, GPU reliability and audit) · International (industry lab with U.S. university co-author); laboratory-style experiments
- Publisher
- arXiv
- Original publication
- 1 November 2026 (arXiv submission)
- Source retrieved
- 2026-11-04
What happened
Using values captured from faulty GPUs (silent data corruption that passes NaN/Inf checks), the authors show research agents can give the same verdict while reading and citing different evidence. In a hERG cardiac-safety assay allocation task, silent numerical faults changed testing decisions while the shortlist kept the same number of labeled blockers. Replacing the prediction file after the agent read faulty values recovered none of 39 changed decisions; restoring the earlier execution state with certified scores recovered all 39. Streaming arithmetic checks cut verification-plus-forward time by 42.4% versus the original FP64 implementation.
Why it matters
Relevant to research computing centers and autonomous-lab programs: audits of AI research agents should log evidence paths and execution state, and hardware faults on shared GPU clusters can silently alter scientific decisions. Limited relevance outside institutions running agents on GPU clusters.
Evidence and measured results
Controlled interventions on saved tool states with healthy-hardware continuation; SciFact retrieval with two 4B models across eight repeated batches; hERG allocation with 16 saved fault sources and 114 agent trajectories; recovery rules developed on a retrospective series then confirmed. Effects concentrated on selected captures: without selection on an upstream change, candidate discordance was no higher than healthy repeat variation. Preprint by an industry lab, not peer reviewed.
Limitations and uncertainty
Small models (4B) and specific faulty GPUs; repeatable evidence-path changes covered only two SciFact claims; R1+M margin rule is empirical; authors also release a GPU test tool, a possible interest; no prospective lab study.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-03; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Labs adopting AI research agents lack ways to detect when silent hardware faults or tool errors change decisions without changing aggregate metrics.
- Stakeholders
- Research computing/HPC operations
- Autonomous lab director
- PI running agent pipelines
- Research integrity office
- Discovery questions
- Do your agent logs record evidence read and cited, or only final answers?
- How are GPUs screened for silent data corruption?
- Can agent state be rolled back before a tool read?
- Which agent decisions trigger experiments or assays?
- Value hypothesis
- Decision-level checks and state rollback could prevent wrong experiments from being committed, at modest verification overhead in the reported implementation.
- Potential engagement
- An assessment of one agent-driven workflow for provenance logging, GPU health screening and a commit gate.
- Unsupported claims
- Shared clusters routinely corrupt research results
- Results generalize to large models
- A single tool removes the risk
Pre-sales engineering
Role takeaway
- Fit
- Strong for agent pipelines that commit experiments from GPU-computed scores; low for chat-style assistants.
- Architecture and integration
- Arithmetic checks on tool outputs, trusted recomputation, checkpointed agent state, certified commit service.
- Prerequisites
- GPU health/SDC screening
- Agent state checkpointing
- Structured logs of reads, citations and actions
- Trusted hardware for recomputation
- Constraints
- Evidence from 4B models and selected faults
- Margin rule is empirical, not a guarantee
- Extra token and compute cost for recovery
- Security
- Treat tool outputs as untrusted until checked; invalidate caches and dependent state after rollback; restrict who can commit instrument instructions.
- Proof of value
- Inject known faulty values and confirm commit gate blocks changed decisions
- Compare file replacement versus state restoration
- Measure verification overhead
Delivery
Role takeaway
- Work
- Instrument agent workflow with evidence-path logging and checkpoints; Add certified-commit step before experiment instructions
- Dependencies
- HPC operations
- Agent framework support for state save/restore
- Trusted recomputation capacity
- Ownership
- Research computing operations, with the lab PI accountable for committed experiments.
- Skills and adoption
- HPC staff and lab users need training on SDC, provenance logs and rollback procedures.
- Governance checkpoints
- GPU health screening before agent workloads
- Review of near-threshold decisions
- Change control for commit-gate rules
- Acceptance criteria
- Proposed: every committed agent action has a logged evidence path
- Proposed: fault-injection test blocks 100% of seeded changed decisions
- Proposed: verification overhead measured and reported
- Risks
- False sense of security from provenance logs
- Recovery token cost
- Vendor or tool lock-in
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Verification belongs at the point where an agent decision is committed: arithmetic checks on tool outputs, trusted recomputation, saved execution state for rollback, and a commit service that only accepts certified actions.
Governance
Who approves, reviews and stays accountable for outcomes?
Audit records should include what an agent read and cited, not only its final answer; a complete provenance record can faithfully preserve wrong values, so independent checks are needed.
Security and privacy
What data, permissions and controls need testing?
Silent data corruption is an integrity risk rather than a confidentiality one; restoring visible history and invalidating caches is part of the remedy.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
HPC staff need SDC awareness and rollback skills; lab staff need to read evidence-path logs.
Procurement
What should contracts, pricing and exit terms secure?
GPU purchases and cluster contracts could specify health testing and fault reporting; the paper names no procurement terms.
Operating model
Which teams own the service once it runs?
Places responsibility for agent decision integrity jointly on research computing and the lab, at the commit point.
Publication history
- 2026-11-03Research Universities · Issue 565 resources
Stable resource ID: intosyn-bioagent-df-decision-provenance-audit-20261101