DMAIC-Bench:多阶段分析任务中智能体从自我反思到自我约束的转变

arXiv cs.AI 论文

摘要

DMAIC-Bench 提出「自我克制」(self-restraint)能力评测,包含 15 个工业案例共 97 个任务及配对反事实变体,发现 13 个模型在 NO-GO 决策上的执行路由准确率平均仅 19%,远低于 GO 决策的 92%。

arXiv:2610.32305v1 Announce Type: new Abstract: Multi-stage analytical tasks require LLM agents to use intermediate evidence to decide whether to continue, redirect or stop. Self-reflection, in which an agent critiques its output, is widely studied, yet a critique does not show whether evidence changed the next action. We call that capability self-restraint. Existing agent benchmarks largely measure task completion or output quality and leave it untested. DMAIC-Bench evaluates it with 97 seeded tasks across 15 industrial cases in four sectors, built around Lean Six Sigma's explicit statistical prerequisites. Paired counterfactual variants require opposite actions at the same workflow position, distinguishing warranted restraint from indiscriminate stopping. We assess execution traces with a private scorer and final claims through independent expert review. Across 13 models from six providers, execution-level routing accuracy averages 92% on matched GO decisions and 19% on NO-GO decisions, counting any forbidden downstream computation as a route error. Execution traces show agents reporting correct diagnostics before performing analyses that those results disallow. Separately, blinded expert review of the 11 audited agents estimates that reports act on invalid evidence at 47% of reached NO-GO decisions, with an interval from 31% to 61%. Explicit stopping permission helps some models without consistently restoring correct decisions at both GO and NO-GO forks. Sixteen life-sciences tasks in bulk ribonucleic acid sequencing (RNA-seq) and case-control genome-wide association studies (GWAS) show that the same framework can evaluate evidence-dependent decisions beyond industrial workflows. Project code and data are available at: https://github.com/psptpx/DMAIC-Bench-public.
查看原文

相似文章

97.2% 的安全拦截机制在多跳智能体交接后不再发挥拦截作用(arXiv 新论文)。你会传递哪些信息,以确保“必须”始终是“必须”?

Reddit r/AI_Agents

一篇新的 arXiv 论文(《当“必须”变成“也许”》,Sun 等人著)发现,在经过多跳智能体交接后,97.2% 的上游安全阻断约束会因压缩、计划同化或责任归属推延而失去约束力——即使权限保持不变——这表明,交接产物本身需要采用明确保留约束的设计。

我在 100 项真实网站任务上测试了 openclaw、hermes、Chrome 中的 claude 和我自己的浏览器

Reddit r/AI_Agents

作者构建了 5dive,一个面向 AI 智能体的开源服务端浏览器运行时,并在 Online-Mind2Web 的 100 项真实网站任务及 4 项受控任务上,将其与 OpenClaw、Hermes 和 Chrome 中的 Claude 进行了基准测试。结果发现,表现最好的几种配置通过率相近,但速度和成本差异显著,其中 5dive(pi)成本最低,总计仅 0.65 美元。

@rohanpaul_ai:谷歌一篇新论文发现,在用户错误地说“那……”之后,Gemini AI 智能体撤销正确工作的可能性要小得多……

X AI KOLs Timeline

谷歌的一篇论文表明,当 Gemini AI 智能体先记录一份包含已核实主张及其置信度的“Thinking-in-Bets”(以赌注思维思考)核对清单时,在用户提出无根据的抱怨后,它们错误地撤销正确工作的可能性会大幅降低;在补丁审查中,错误返工率从 12.2% 降至 0.02%。