公开论文雷达

公开 arXiv 研究简报 · 2026-08-26T01:13:46.398901+00:00

先看结论和关键数字,再决定要不要读原文。候选只在首次出现时展示;旧候选若后来通过深读门槛,仍会进入重点。

别用一个模型通吃,按任务分解再交给机器裁决

六张卡都在用LLM或智能体做自动化,共同教训是单一模型加统一策略会失败,必须先按任务或类别拆开。建议先读需求工程那篇打底,它把“没有模型跨任务通吃”讲得最直白;再看两篇按类别或画像分而治之的做法;最后落到两篇用验证器给出机器可复核证明的思路,从凭经验过渡到可复核。

推荐阅读顺序

  1. 2608.21531:先读,它给出全组的底层判断:跨五类需求任务无单一模型持续领先,得逐任务选型。
  2. 2608.23152:把“先分类再分策略”落到反制言论:仇恨分五类路由到小于2B的专用智能体。
  3. 2608.22310:同样反对统一处理:长期记忆不压缩不改写,用三层图分级、画像导航取原文。
  4. 2608.21718:垂直领域样本:XR缺陷按单行/函数/类三粒度设提示,靠修复率加人工审查背书。
  5. 2608.21516:转向验证器背书:把Python译成Dafny/CBMC,让验证器裁决而非LLM打分。
  6. 2608.22928:读到最强保证:从执行记录精确判定编辑安全,Lean机械化验证六种编辑形式。
共性方法
六篇都反对“一个模型加统一策略包打天下”:需求工程要按任务选型,反制言论按仇恨类别路由,XR缺陷按粒度设提示,长期记忆按三层图分级,代码验证只让神经部分做翻译和提案。共同动作是先把问题拆成可区分的部分,再分而治之,而不是端到端一锅端。
关键分歧
最大分歧在“凭什么信结果”。两篇形式验证(2608.22928的Lean检查、2608.21516的Dafny/CBMC裁决)要机器可复核的证明或反例;另外四篇则靠量化指标加人工评估,用修复率、F1、准确率、人类偏好来背书。前者给可审计的正确性,后者给经验性的效果,结论强度不在一个层级。
选择准则
如果你要机器可复核的正确性保证,读两篇形式验证;如果你要能落地的领域自动化和评测套路,读软件工程与知识治理四篇。先问自己:这个任务能不能接受只有人工评估和指标背书。

重点深读(6 / 6 篇)

形式化与程序验证(2 篇)

形式化与程序验证 6/30

When Can Agents Safely Checkpoint, Fork, Restore, and Merge? Exact Checking for Execution Edits

Agent执行编辑精确安全检查算法:提出精确算法判定Agent执行编辑(Checkpoint/Fork/Restore/Merge)是否安全,从执行记录推导必须保留的授权和结果,返回所有安全续行方式或不可行的可验证证明,Lean机械化验证六种编辑形式。

两句看懂

现有Agent运行时支持Checkpoint与分支合并,但均未从执行记录推导编辑安全条件,可导致同一工具动作被重复授权或仍需结果被丢弃。该研究提出精确算法,从受信任执行记录枚举合法完成路径并剪除危险路径,Lean机械化验证检查器正确性,可执行测试覆盖全部六种编辑形式。

核心判断

可从受信任执行记录精确判定任意执行编辑是否安全:算法枚举合法完成路径并删去危险路径,返回允许续行集合或不可行证明;Lean机械化证明和可执行测试覆盖六种编辑形式为此背书。

关键要点

1. 现有Agent运行时(含分支、事务和恢复机制)均未从运行执行记录推导编辑安全条件,而控制与合成方法又将该条件作为输入前提;两类遗漏分别导致同一一次性审批被重复触发和仍需工具结果被剪除,现有系统均无法检测。 2. 算法从受信任执行记录提取四类信息(任务结构、调用同一性、授权历史、重叠规则),枚举合法完成路径,删去使仍需结果无法满足的路径,覆盖Checkpoint及六种Fork/Restore/Merge;Lean机械化有限检查器和运行时不变量,可执行测试覆盖全部六种形式。 3. 精确检查器返回所有允许续行路径或输出可验证的不可行证明;四类记录缺少任一项均可改变判断结论,表明仅凭执行轨迹或授权日志单独决策不充分。

证据与结果

形式化结果覆盖Checkpoint及六种Fork/Restore/Merge编辑形式,以及扩展情形、原子执行和精确检查器所需信息。Lean对有限检查器和运行时不变量进行机械化证明,提供形式化正确性保证。可执行测试套件验证全部六种编辑形式。论文以购买笔记本场景(一次性审批→授权支付→恢复检查点→比较第二供应商→合并)说明四类记录缺失时的判断失败模式,但未报告规模基准测试数据或运行时间测量结果。

打开论文原文
它要解决什么
Agent运行时执行Checkpoint/Restore/Merge时,如何从执行记录精确判定哪些授权和结果必须保留,以保证后续执行不违反策略?
研究路径
编辑生效前,运行时从执行记录提取有限工具调用集合、可能执行顺序、授权记录和适用规则;算法枚举任务合法完成路径,删去使仍需结果无法满足的路径;若无路径剩余则构造可验证不可行证明,否则输出允许续行集合;原子规则更新保证授权创建与复用相对规则变更有序进行;Agent内部推理在编辑过程中保持不变。
这对工程意味着什么
为Agent运行时添加检查点支持时,应在编辑生效前从受信任执行记录(非Agent自身描述)运行精确检查,获取合法续行集合或不可行证明;不可仅凭执行轨迹或授权日志单独判定安全性,两者各自遗漏关键信息。
证据定位
Lean机械化证明有限检查器正确性和运行时不变量;可执行测试验证全部六种Fork/Restore/Merge编辑形式及Checkpoint;精确检查器能枚举所有安全续行路径或输出可验证的不可行证明。(筛选维度:形式化验证、软件工程方法)
适用边界
论文聚焦有限工具调用集合上的形式化检查,未提供运行时间或规模基准数据;测试覆盖六种编辑形式,但未报告在大规模真实Agent工作流上的实验;未讨论无限或动态扩展工具调用集合下的适用性。
方法与英文摘要

受信任运行时在编辑生效前从执行记录提取四类信息:任务结构与必需结果、工具调用同一性映射、授权历史与调用进度、编辑重叠适用规则。算法枚举任务所有合法完成路径,删去使仍需结果无法满足的路径;若无路径剩余则构造可验证的不可行证明,否则输出允许续行集合。Lean对有限检查器和运行时不变量进行机械化证明;可执行测试覆盖Checkpoint及六种Fork/Restore/Merge编辑形式。

Agent runtimes can Checkpoint an execution, Fork it, Restore a checkpoint, or Merge branches without restarting a task. We call these operations execution edits, with Checkpoint recording the current execution for later use and Fork, Restore, and Merge changing what the Agent will do next. An execution edit cannot undo an earlier authorization or a tool request already sent. An unsafe edit can therefore authorize the same tool action twice, discard a result the task still requires, or conflict with a call that began before the edit. The Agent is untrusted, so the runtime uses its execution record to determine which past actions an edit must account for and which required results it must preserve to keep the subsequent execution safe. Yet existing Agent systems support such operations without deriving what each edit must preserve from the running execution, whereas prior methods for computing safe behavior take that requirement as input. We give an algorithm that decides exactly whether an edit is safe. It returns all safe ways to continue, or proves that none exists. To make this decision, the algorithm lists every way the task can finish without violating policy. It removes any way that could make a still-required result impossible to finish later. If none remain, it returns a checkable proof that no safe implementation exists. Otherwise, the remaining ways describe exactly what the runtime may allow. Our formal results cover Checkpoint and the six forms of Fork, Restore, and Merge, together with extensions, atomic enforcement, and the information every exact checker needs. Lean mechanizes the finite checker and runtime invariant, and tests validate all six edit forms. The source code, Lean proofs, and executable tests are available in the public GitHub repository at https://github.com/eunomia-bpf/agent-check-restore-safety.

形式化与程序验证 6/30

Neuro-Formal Verification: Agentic Language-Agnostic Formal Program Reasoning

Python代码也能拿机器证明:NFV让Dafny/CBMC裁决,而不是靠LLM打分:如果你要审计AI生成代码,真正缺的不是“看起来更合理”,而是可被机器复核的证明或反例。NFV的做法是把Python程序和自然语言属性交给AI代理翻译为Dafny或CBMC输入,再由成熟验证器逐步判定;结果是57%条目拿到Dafny证明、精度92%,63%有缺陷程序拿到CBMC反例、精度90%。

两句看懂

主流语言缺少验证感知支持,过去只能靠审查和测试建立信心;NFV用AI代理把Python程序翻译进Dafny/CBMC,再由验证器判定。相对LLM-as-judge,它在Python数据集上做到57% Dafny证明覆盖、精度92%,以及63% CBMC反例覆盖、精度90%。

核心判断

AI代理能把主流语言程序翻译成验证器输入,并让成熟验证器输出机器可检验证明;支撑数字是57% Dafny证明覆盖、精度92%,以及63% CBMC反例覆盖、精度90%。

关键要点

1. 旧假设:形式验证要会Dafny/Lean和规范编写,主流Python只能靠审查、测试或LLM-as-judge。 2. 方法与受控点:神经部分只负责翻译和提案,Dafny/CBMC逐步独立裁决,数据集是Python正确/错误程序对。 3. 结果与动作:57%获Dafny证明(精度92%)、63%缺陷程序获CBMC反例(精度90%);审计时可用它替代LLM打分,但未覆盖条目不能算通过。

证据与结果

评测使用Python正确与错误程序对,基线是LLM-as-judge。Dafny路径对全量条目的证明覆盖为57%,精度92%;CBMC路径对有缺陷程序的反例覆盖为63%,精度90%。覆盖不到100% mainly卡在神经翻译失败或翻译歧义;作者承诺的是精度而非声音性,证明只对翻译后的形式模型成立。

打开论文原文
它要解决什么
开发者继续写Python等主流语言,不换语言、不学形式方法,能否仍由验证器给出机器可检验结论?
研究路径
输入是Python程序、自然语言属性断言和环境文档。代理先生成形式规范,再把程序与规范翻译成Dafny或CBMC输入,并反复补不变量、引理和策略;每个候选步骤都由验证器单独声音判定,最后把证明草图映回开发者原来的变量和术语。
这对工程意味着什么
第一步:把AI生成代码审计里的LLM-as-judge关口,换成“神经翻译+Dafny/CBMC裁决”的NFV流程。要避开的捷径:别把92%精度当成声音性,翻译失败导致未覆盖的条目不能当作已验证。
证据定位
对比LLM-as-judge:Dafny路径覆盖57%条目并返回正确性或缺陷证明,精度92%;CBMC路径覆盖63%有缺陷程序并返回反例,精度90%。(筛选维度:形式化验证、可复核评测)
适用边界
数据只覆盖Python编程题,不含系统级代码、重库调用或复杂环境建模。覆盖率受神经翻译质量上限约束;声音性只及于翻译后的形式模型,不及于原始Python程序语义。
方法与英文摘要

数据是Python正确/错误程序对。流水线分五步:AI代理从自然语言文档合成形式规范;把程序和规范神经翻译到Dafny或CBMC输入;代理迭代提出不变量、引理和策略;验证器对每个候选步骤独立作声音判定;最后把证明草图映射回原始变量。对照基线是LLM-as-judge。

Formal verification offers the strongest assurance available for software, and verification-aware languages have made its automation real. Yet the benefits reach few mainstream developers, most of whose languages have no verification support. Besides, specifying properties and modeling the environment require expertise in formal methods. Proof is therefore reserved for a few celebrated artifacts, while the production code that ships is attested only through review and testing. We introduce neuro-formal verification (NFV), which harnesses that automation for developers of mainstream programming languages: an AI coding agent translates, an established verifier decides, and a question posed in a mainstream language is answered push-button, at empirical accuracy rather than soundness, with a machine-checked proof. Results on a dataset of correct and incorrect solutions to Python programming problems are encouraging: NFV returns a Dafny proof of correctness or of a bug on 57% of the entries at 92% precision, and a CBMC counterexample for 63% of the buggy programs at 90% precision.

软件工程与仓库智能(2 篇)

软件工程与仓库智能 11/30

Large Language Models for Requirements Engineering: A Cross-Task Empirical Evaluation

LLM做需求工程:没有一款模型在所有任务上都领先,必须按任务选型:如果你想用一个LLM包揽需求工程里的分类、溯源、生成等所有活,这项研究提醒你此路不通:跨五类任务,模型表现从中等到高不等,且无一模型持续领先。研究用两项互补实证验证了这一点:一项受控实验(五款轻量开源LLM×三类任务),一项工业案例(两款前沿LLM×两类真实项目任务),并公开了复现材料。

两句看懂

以往LLM需求工程研究分散在单任务场景,缺乏跨任务对照;该研究用两项互补实证同时覆盖分类、溯源识别、规格与解释生成共五类活动,分别用五款开源LLM和两款前沿LLM。分类和溯源识别用量化指标衡量,生成任务用人工评估核验;结果显示性能依任务而定(中等至高),无单一模型跨任务持续领先。

核心判断

LLM在五类需求工程任务上表现依任务而异(中等至高),没有单一模型跨任务持续领先;证据来自两项实证:受控实验(五款开源LLM×三任务)和工业案例(两款前沿LLM×两任务)。

关键要点

1. 旧假设:以往研究只做单任务、单制品类型,默认单任务结论可推广到整个需求工程,这一假设从未被跨任务验证。 2. 方法与对照:受控实验用五款开源LLM跑三类反馈驱动任务(分类用量化指标、生成用人工评估),工业案例用两款前沿LLM在真实项目制品上跑溯源识别与解释生成,两条路径并行对照。 3. 决定性结论:五类任务性能中等到高、依任务而异,无模型持续领先——部署时必须逐任务选模型和提示策略。

证据与结果

研究一:数据来自用户反馈,任务为非功能需求分类、用户请求分类、需求规格生成,模型为五款轻量开源LLM,分类用量化指标,生成用人工评估。研究二:数据来自真实工业软件项目制品(问题票、开发讨论、仓库文档),任务为可追溯性链接识别和解释生成,模型为两款前沿LLM,识别用量化指标,解释生成用人工评估。摘录未给出具体精度或F1数值,整体性能区间只描述为中等至高。

打开论文原文
它要解决什么
LLM在需求分类、溯源链接识别、规格与解释生成等五类需求工程活动上,能力和局限分别如何?表现能否跨任务通用?
研究路径
研究团队先从用户反馈构建分类与规格生成数据集,用自然语言提示驱动五款开源LLM;再采集真实项目制品(问题票、开发讨论、仓库文档),驱动两款前沿LLM执行溯源链接识别和解释生成。分类和识别的输出用量化指标打分,规格与解释生成的输出由人工评估员评分。两条路径并行运行,从而实现跨任务对照。
这对工程意味着什么
第一步行动:在部署LLM辅助需求工程前,先按你的目标任务单独跑基线评测,分类/识别用量化指标,生成任务加人工评估。要避开的捷径:不要因为某模型在分类任务上得分高,就直接推断它在规格生成或溯源任务上也好用。
证据定位
跨五类任务,LLM性能从中等到高,且强烈依具体任务而定;没有任何单一模型在全部任务中持续优于其他模型。原摘录未提供具体精度数值。(筛选维度:形式化验证、可复核评测、软件工程方法)
适用边界
研究二是工业探索性案例,数据来自单一项目,可推广性有限;摘录未给出各任务的精确数值,中等至高的区间描述较粗略;提示策略的系统性对比细节需查阅完整论文。
方法与英文摘要

研究一是受控实验:五款轻量开源LLM分别执行三类反馈驱动任务——非功能需求分类、用户请求分类、需求规格生成;分类用量化指标,生成用人工评估。研究二是工业探索性案例:两款前沿LLM处理真实软件项目制品(问题票、开发讨论、仓库文档),执行可追溯性链接识别与解释生成;识别用量化指标,解释生成用人工评估。两项研究合计覆盖五类需求工程活动。

Requirements-related information is scattered across heterogeneous artefacts such as user feedback, developer discussions, and software repositories, making the extraction of actionable requirements knowledge labour-intensive and hard to scale. Large Language Models (LLMs) can support many Requirements Engineering (RE) activities, from classification and traceability identification to specification and explanation generation, but existing evidence is fragmented across tasks, artefact types, and evaluation settings, and studies rarely offer cross-task evaluations or replication packages. We present two complementary empirical studies evaluating LLMs across five RE-related activities. The first is a controlled experiment on five lightweight open-source LLMs for feedback-driven requirements classification and specification generation. The second is an exploratory industrial case study on two frontier LLMs for traceability link identification and traceability explanation generation using real project artefacts. Classification and traceability identification were assessed with quantitative metrics, and generation tasks through human evaluation. LLM performance is strongly task-dependent, ranging from moderate to high, and no single model consistently outperformed the others, indicating that effective adoption depends on selecting models and prompting strategies per task. Our contributions are: (i) the first cross-task empirical evaluation of LLMs spanning five RE-related activities, (ii) replication materials supporting reproducibility, and (iii) a broader understanding of the capabilities, limitations, and practical readiness of current LLMs for RE.

软件工程与仓库智能 7/30

XRFix: Exploring Performance Bug Repair of Extended Reality Applications with Large Language Models

XRFix:LLM修复XR应用性能缺陷:针对XR应用缺乏真实缺陷数据集、无专用检测和修复框架的问题,XRFix从23个开源XR项目整理104个真实缺陷,定制C#脚本与资产文件静态分析工具,按单行、函数、类三粒度设计提示词驱动LLM修复,修复率67.3%,超次优APR方法7.7个百分点。

两句看懂

现有APR框架面向传统软件设计,无法覆盖XR特有10类性能缺陷,XRFix以104个真实缺陷数据集、专用静态分析工具和三粒度提示词策略填补这一空白。在23个开源Unity XR项目上对五种LLM评测,经静态分析、答案对比和人工审查三重验证,修复率达67.3%,超次优SOTA方法7.7个百分点。

核心判断

现有APR方法不能有效修复XR性能缺陷;XRFix通过专用数据集、定制静态检测和三粒度提示词策略,修复率达67.3%,超次优基线7.7个百分点,此为决定性证据。

关键要点

1. 搜索式、模板式和NMT-APR等现有方法面向传统软件构建,无法处理XR应用3D渲染、实时动画、进程仿真等计算密集操作引发的性能缺陷;XR领域既无真实缺陷数据集,也无针对C#脚本与资产文件的专用静态检测工具,直接迁移已有APR框架存在系统性覆盖缺口。 2. 从23个开源Unity XR项目抽取代码库,综合论坛、MITRE CWE数据库和文献归纳10类缺陷(RWT、RCC、RLC、RD等),构建104个真实缺陷数据集;定制两款静态分析工具分别覆盖C#脚本和资产文件;按单行、函数、类三个粒度设计提示词,以缺陷复杂度为控制变量,驱动五种LLM修复。 3. XRFix修复率67.3%,超次优SOTA APR方法7.7个百分点;函数级与类级修复难度高于单行级,表明粒度是影响LLM修复成功率的关键边界变量;三重验证机制排除误报,确认修复结果可信。

证据与结果

数据集来自23个开源Unity XR项目,含104个真实性能缺陷,覆盖10类XR专有缺陷类型(RWT、RCC、RLC、RD等);按单行、函数、类三粒度分层评估;对五种现成LLM执行修复实验,与三种SOTA APR基线对比;主要指标为修复率,XRFix达67.3%,较次优方法高7.7个百分点;评估采用静态分析、标准答案对比和人工审查三重机制,兼顾自动与人工核查,减少误报干扰。

打开论文原文
它要解决什么
现有APR方法能否直接适用于XR应用性能缺陷修复,若不能,如何设计专用框架?
研究路径
静态分析工具扫描Unity项目C#脚本和资产文件,定位10类XR特定性能缺陷;按缺陷粒度(单行/函数/类)选择对应提示词模板,将缺陷上下文输入LLM;模型输出补丁后,依次通过静态分析合规检查、标准答案对比和人工审查三道验证,确认修复有效性。
这对工程意味着什么
在Unity XR项目中引入XRFix:先用定制静态工具定位C#脚本和资产文件中的性能缺陷,再按粒度选取提示词驱动LLM修复;避免直接套用通用APR工具,因其未对XR计算特性建模,覆盖率系统性偏低。
证据定位
XRFix修复率67.3%,超次优SOTA APR方法7.7个百分点;三重验证(静态分析、标准答案对比、人工审查)确认结果有效。(筛选维度:可复核评测、软件工程方法)
适用边界
数据集限于23个Unity开源XR项目的104个缺陷,平台和缺陷类型覆盖有限;评估以修复率为主,未报告运行时性能改善的量化数据;所用LLM为现成模型,未做XR领域微调。
方法与英文摘要

从23个开源Unity XR项目收集代码库,综合论坛、MITRE CWE数据库和研究文献归纳10类XR专有性能缺陷,构建104个真实缺陷数据集。定制两款静态分析工具分别针对C#脚本和资产文件进行缺陷检测。按单行、函数、类三种粒度设计差异化提示词,驱动五种现成LLM执行修复。通过静态分析合规检查、标准答案对比和人工审查三种方式评估修复效果,并与三种SOTA APR基线对比。

As an emerging technology, Extended Reality provides end-users with an immersive experience of interacting with virtual and physical environments. Unlike traditional software, the execution of XR applications involves more computationally complex operations, such as 3D scene rendering, real-time animation, and process simulations. Inefficient coding practices during the software development of XR applications may cause various performance bugs, degrading user experience and even causing motion sickness. Thus, it is an urgent need to develop an automated program repair framework for fixing performance bugs in complex XR programs. However, it is non-trivial to achieve this goal due to several technical challenges: (1) a lack of a real-world XR codebase and bug dataset, (2) no accurate bug detection tool, and (3) no effective bug-fixing tool designed for XR performance bugs. To tackle these challenges, we present a novel large language model-based framework, namely XRFix, to repair performance bugs for open-source XR programs. We first construct a corpus of domain-specific performance bugs built with a codebase from 23 open-source XR projects and a dataset of XR-related bugs containing 104 real-world bugs. Then, we tailor two static analysis tools for accurately detecting bugs in both C# scripts and asset files. Last, we design different prompts to instruct LLMs to fix XR bugs in three types of bug scenarios with different complexities, i.e., single-line level, function level, and class level. We conduct extensive experiments on five off-the-shelf LLMs to evaluate the bug-fixing performance of XRFix. We also compare our XRFix with three SOTA APR approaches. Through static analysis, reference answer comparison, and manual inspection, we demonstrate that our XRFix can effectively fix XR bugs, outperforming SOTA APR methods.

代码质量与优化(0 篇)

本轮没有通过深读证据门的重点论文。

UI 与 GUI Agent(0 篇)

本轮没有通过深读证据门的重点论文。

个人知识与本体(2 篇)

个人知识与本体 4/30

Counter with Evidence! A Multi-Agent Memory Efficient Reasoning Framework for Hate Category Informed Counterspeech Generation

把仇恨言论先分五类再反制,小于2B参数的智能体框架FIRE在事实准确率上比最强基线高…:如果你在做内容治理或反制言论生成,这条结论直接影响架构选型:不要把仇恨言论当成一类文本用统一策略处理。FIRE先把仇恨言论分为错误信息、刻板印象、阴谋、非人化、非事实五类,再路由到专用小模型智能体分别做推理和生成。结果是在28种基线配置评测中,事实准确率比最强基线提升约12%,毒性降低约11%。

两句看懂

现有反制言论系统把仇恨内容当作同质整体,用统一策略生成,无法针对错误信息、阴谋等不同类型分别反驳其核心前提;FIRE先把仇恨归入五类,再由小于2B参数的专用智能体解耦完成推理与生成。在28种基线配置评测中,FIRE相对最强基线事实准确率提升约12%、毒性降低约11%,人类评估也确认其输出更受偏好。

核心判断

把仇恨言论显式分成五种语义类别并路由到专用策略,比同质处理基线在三个指标上同时更好:事实准确率约+12%,类别特定准确率约+11%,毒性约-11%。这一结论由28种基线配置的系统评测和人类评估共同支撑。

关键要点

1. 旧假设失效:既有系统把仇恨言论视为同质实体、用统一策略生成,忽视错误信息要靠事实证据反驳、非人化要靠道德重构的差异;此前数据集也缺类别标注、推理轨迹和证据映射。 2. 方法与受控对比:FactualCS含4,784条仇恨-反制对、14个目标社区;FIRE执行分类→推理→生成三阶段流水线,推理与生成显式解耦,智能体参数全程小于2B,与28种基线配置对比。 3. 结果与动作:相对最强基线,事实准确率约+12%、类别特定准确率约+11%、毒性约-11%,人类评估显著偏好FIRE;做类似任务时先加分类路由再分策略生成,但要注意分类错误会让策略和仇恨类型错配。

证据与结果

评测基于FactualCS数据集:4,784条仇恨-反制对,14个目标社区,含类别标注、推理轨迹和证据映射。共对比28种基线配置,包括GPS、DialoGPT、CoARL等方法。指标为事实准确率、类别特定准确率、毒性得分。相对最强基线,FIRE事实准确率约+12%,类别特定准确率约+11%,毒性约-11%。额外的人类评估确认FIRE输出质量显著更受偏好。

打开论文原文
它要解决什么
仇恨言论的语义差异很大:错误信息需要事实证据反驳,非人化需要道德重构。那么,按类别分解仇恨并路由到专用智能体,能否在小于2B参数的规模下明显优于统一生成基线?
研究路径
FIRE按顺序执行三步。第一步,分类智能体把仇恨言论归入错误信息、刻板印象、阴谋、非人化、非事实五类。第二步,推理智能体根据类别构造检索查询、获取支撑证据并生成推理轨迹。第三步,生成智能体以类别标签、推理轨迹和检索证据为条件输出反制文本。每一步都由参数小于2B的专用轻量智能体承担,推理和生成在架构上显式解耦,因此每一类仇恨可以使用针对性的反驳策略。
这对工程意味着什么
第一个动作:在意图多样的文本生成任务里,先加一个分类路由步骤,再按类别分策略生成。要避免的捷径:不要假设单一模型能隐式学会所有类型的最优响应——在类别明确可分的场景(如事实性错误与情感性冒犯),这个假设会得到泛化但缺乏针对性的输出。
证据定位
在覆盖28种基线配置的评测中,对比GPS、DialoGPT、CoARL等方法,FIRE相对最强基线:事实准确率提升约12%,类别特定准确率提升约11%,毒性降低约11%。人类评估也显著偏好FIRE的输出。(筛选维度:可复核评测)
适用边界
摘录未报告各类别的样本分布比例,也未给出分类步骤的独立准确率;数据集的语种和平台覆盖范围在摘录中没有说明;跨语言及低资源语言下的泛化能力缺乏直接证据。
方法与英文摘要

先构建数据集FactualCS:4,784条仇恨-反制对,覆盖14个目标社区,标注类别、推理轨迹和证据映射。FIRE框架分三阶段运行:分类智能体把输入归入五类之一;推理智能体根据类别生成检索查询、获取证据并产生推理轨迹;生成智能体以类别、推理轨迹和证据为条件输出反制文本。所有智能体参数均小于2B,推理阶段与生成阶段显式解耦。

Counterspeech effectively neutralizes the impact of online hate. Although prior work explores automated counterspeech generation, it largely emphasizes stylistic control while treating hate speech as homogeneous, overlooking that distinct forms of abuse require fundamentally different counterspeech strategies. To address this gap, we introduce FIRE (Factuality Informed Multi-Agent Reasoning Framework) that first decomposes hate speech into one of the five distinct categories (misinformation, stereotype, conspiracy, dehumanizing, non-factual), and then maps it to a targeted counterspeech style. To facilitate FIRE, we curate FactualCS, a novel dataset of $4,784$ instances that provides the annotations regarding hate categories, reasoning traces, and evidence mappings, which are critical elements for grounded generation that are missing in prior work. A comprehensive evaluation across $28$ baseline configurations demonstrates that FIRE significantly surpasses existing methods, despite using compact agents ($<$2B). FIRE achieves a $\sim$ $12 \%$ and $\sim$ $11 \%$ improvements in factual and category-specific accuracy respectively, while simultaneously reducing toxicity by $\sim$ $11 \%$ relative to the strongest baselines. Further human evaluation confirms that responses generated by FIRE are significantly preferred over the strongest baselines, underscoring its effectiveness for real-world deployment. These findings show that decomposing the underlying intent of hate speech is essential for generating safe, effective, and contextually precise counterspeech.

个人知识与本体 4/30

HERO: Human-profile Enhanced Retrieval Optimization Framework for Long-term Agent Memory

保留对话原文、用人物画像导航图检索,长期记忆两个基准都超过强基线:做长期对话记忆的工程师都头疼两件事:压缩丢细节、改写跑偏语义。HERO 的思路是不压缩、不改写,把原始对话轮次存进三层异质图,检索时拿用户画像当导航信号往下钻,最后直接返回原文做推理证据。结果:LoCoMo 上 F1 56.06%,PERSONAMEM 上准确率 70.63%,均优于压缩/改写类强基线。

两句看懂

现有长期记忆靠 LLM 压缩或改写对话,细粒度细节丢了,语义还漂移;HERO 改为建三层异质图、保留原文、用人物画像引导检索。LoCoMo F1 56.06%、PERSONAMEM 准确率 70.63%,均超强基线,画像引导的迭代遍历明显减少了无关内容干扰。

核心判断

保留原始对话文本并以人物画像引导图检索,能同时消除压缩信息损失和改写语义漂移;LoCoMo F1 56.06%、PERSONAMEM 准确率 70.63% 超越强基线验证了这一点。

关键要点

1. 旧路线的失败:压缩按写入时重要性过滤,丢时间引用、数值事实和偏好变化;改写削弱原始语气和归因,摘要幻觉还会跨层传播。 2. 方法与对照:HERO 建 Trace/Unit/Cue 三层异质图保留原文,检索时融合画像迭代扩展、查询条件过滤约束漂移,并在 LoCoMo 和 PERSONAMEM 上与压缩/改写类强基线对比。 3. 结果与行动:LoCoMo F1 56.06%、PERSONAMEM 准确率 70.63% 均超基线;工程上应用画像定位后取原文轮次做推理,不要用摘要当证据。

证据与结果

在 LoCoMo(复杂事实问答,按 F1 计分)和 PERSONAMEM(个性化推理,按准确率计分)上评测,对手是压缩/改写类强基线。HERO 拿到 LoCoMo F1 56.06%、PERSONAMEM 准确率 70.63%,两项都赢。论文给出的失败诊断是:压缩在写入时按重要性过滤导致细节丢失,改写产生语义漂移且摘要幻觉跨层传播。数据集规模和完整基线名单在摘录中未列出。

打开论文原文
它要解决什么
长期对话记忆里,压缩带来的信息损失和改写带来的语义漂移,能不能用"保留原文 + 画像引导图检索"同时解决?
研究路径
构建阶段把对话历史解析成三层:Trace 是逐轮原文,Unit 是话题粒度段落,Cue 是实体/关键词;三层用结构包含边、语义索引边、时序链接边相连,画像预提取后存为图节点。检索阶段从查询抽锚点激活 Cue 节点,融合画像信号逐层下钻到 Unit 和 Trace,查询条件剪枝冗余节点,最终返回 Trace 层原文供推理。
这对工程意味着什么
第一步行动:跨多轮追踪用户偏好时,先用画像引导图遍历定位相关区域,再把原始对话轮次文本送进推理。要避免的捷径:不要图省事把摘要或改写文本当最终推理证据,语义漂移和幻觉会在推理阶段被放大。
证据定位
LoCoMo(事实问答)上 F1 达 56.06%,PERSONAMEM(个性化推理)上准确率达 70.63%,两项都超过压缩/改写类强基线。系统输出的是可溯源的原始对话轮次文本,摘要幻觉不会从低层向高层传播。(筛选维度:可复核评测)
适用边界
摘录未报告数据集具体规模和完整基线列表。图构建依赖 LLM 做实体/关系抽取,这一步的误差对最终检索质量的影响没有系统量化。实验覆盖的语言和领域范围也未说明。
方法与英文摘要

HERO 建三层异质图:Episodic Trace 存原始对话轮次文本,Episodic Unit 存话题粒度片段,Episodic Cue 存关键词/实体节点。三层之间用结构包含、语义索引、时序链接三种边连接,人物画像预先提取存入图节点。检索时先从查询抽出锚点激活 Cue 节点,再融合画像信号迭代扩展到 Unit 和 Trace 层,查询条件负责过滤剪枝、约束主题漂移,最后返回 Trace 层原文。画像只做导航,不替换记忆内容。

Long-term memory is crucial for personalized responses and long-horizon agent interactions. Existing methods often rely on LLMs to compress or rewrite dialogue histories and use the transformed memories as retrieval evidence. Despite the progress in organizing fragmented contexts, two major drawbacks persist: (1) information loss from compression, which discards fine-grained but later useful details, and (2) semantic drift from rewriting, which erodes the original tone and situated context. In this work, we propose a novel Human-profile Enhanced Retrieval Optimization framework for long-term agent memory (HERO). Specifically, HERO converts the dialogue history into a traceable heterogeneous memory graph that preserves raw dialogue text as evidence for reasoning, thereby mitigating information loss. For retrieval, HERO extracts initial anchors from the current query and incorporates human profiles via an iterative graph traversal; these anchors and profiles provide guidance signals that adaptively activate the most informative regions of the graph. Experiments on two benchmark datasets show that HERO outperforms strong baselines on both factual and personalized reasoning, while providing more faithful access to raw dialogue evidence.

人机协同与对齐(0 篇)

本轮没有通过深读证据门的重点论文。

本轮分类概览

同一论文只归入一个最先命中的赛道,避免重复计数;“新增候选”只统计首次展示的论文。

赛道新增候选重点
形式化与程序验证32
软件工程与仓库智能42
代码质量与优化10
UI 与 GUI Agent10
个人知识与本体82
人机协同与对齐00

近一个季度监测日历

北京时间。绿色表示有可阅读的新候选,灰蓝表示已监测但无新增,橙色表示部分降级;“无记录”不等于失败。

2026 年 6 月

1无记录2无记录3无记录4无记录5无记录6无记录7无记录8无记录9无记录10无记录11无记录12无记录13无记录14无记录15无记录16无记录17无记录18无记录19无记录20无记录21无记录22无记录23无记录24无记录25无记录26无记录27无记录28无记录29无记录30无记录

2026 年 8 月

近 14 次监测窗口

仅展示公开源的聚合运行状态,不含提示词、全文或个人数据。

本轮新增候选(17 篇)

按赛道、评分和日期展开;中文标签用于导航,英文摘要用于核验。已展示过的旧候选不会每日重复。

形式化与程序验证(3 篇)

形式化与程序验证 · 6/30 · 2026-08-24智能体执行编辑的精确安全检查为智能体运行时的检查点、分支、恢复与合并操作提供精确安全检查,防止重复授权、丢弃必需结果或与既有调用冲突When Can Agents Safely Checkpoint, Fork, Restore, and Merge? Exact Checking for Execution Edits

Agent runtimes can Checkpoint an execution, Fork it, Restore a checkpoint, or Merge branches without restarting a task. We call these operations execution edits, with Checkpoint recording the current execution for later use and Fork, Restore, and Merge changing what the Agent will do next. An execution edit cannot undo an earlier authorization or a tool request already sent. An unsafe edit can therefore authorize the same tool action twice, discard a result the task still requires, or conflict with a call that began before the edit. The Agent is untrusted, so the runtime uses its execution record to determine which past actions an edit must account for and which required results it must preserve to keep the subsequent execution safe. Yet existing Agent systems support such operations without deriving what each edit must preserve from the running execution, whereas prior methods for computing safe behavior take that requirement as input. We give an algorithm that decides exactly whether an edit is safe. It returns all safe ways to continue, or proves that none exists. To make this decision, the algorithm lists every way the task can finish without violating policy. It removes any way that could make a still-required result impossible to finish later. If none remain, it returns a checkable proof that no safe implementation exists. Otherwise, the remaining ways describe exactly what the runtime may allow. Our formal results cover Checkpoint and the six forms of Fork, Restore, and Merge, together with extensions, atomic enforcement, and the information every exact checker needs. Lean mechanizes the finite checker and runtime invariant, and tests validate all six edit forms. The source code, Lean proofs, and executable tests are available in the public GitHub repository at https://github.com/eunomia-bpf/agent-check-restore-safety.

阅读 arXiv 原文
形式化与程序验证 · 5/30 · 2026-08-23Go 程序的演绎式形式验证系统提出 VeGo,以非侵入式注释在标准 Go 源码上支持 Hoare 契约、循环不变式与良基递归度量,面向教学VeGo: Direct Deductive Formal Verification of Go Programs for Computer Science Education

As formal methods are rapidly becoming accessible and practical due to AI coding agents, priority passes to assisting developers and students in generating specifications. Leveraging native HMX/SSA verifiers provide that support with rigorous mathematical guardrails. We present VeGo (Verified Go), a deductive formal verification system that enables direct verification of standard Go source code. VeGo incorporates Hoare-style contracts, loop invariants and integer variants, well-founded recursive measures, block-level scope invariants, and equational reasoning chains with primed variables directly as non-intrusive Go comments. We detail the language selection rationale justifying Go as an ideal balance over C, C++, Java, and Rust, strategically adopting Go's native multiple return values. We detail the tool architecture, exploiting the theoretical equivalence between Static Single Assignment (SSA) form and first-order functional programming to annotate code, desugar of clopen interval quantifiers, add Reynolds' skip statement, provide weakest precondition calculus, and native Hindley-Milner constraint inference, and verification condition resolution over the SSA form. We formalize contract-precision checking (weakest precondition vs. strongest postcondition) using an explicit analogy to type inference. Finally, we evaluate VeGo across educational textbooks and outline a roadmap for formal concurrency specifications using epistemic temporal logic.

阅读 arXiv 原文
形式化与程序验证 · 6/30 · 2026-08-21神经-形式化验证:语言无关的程序推理提出神经形式化验证范式,由编码智能体转译、既有验证器裁决,让主流语言开发者以经验性准确率获得机器检查证明Neuro-Formal Verification: Agentic Language-Agnostic Formal Program Reasoning

Formal verification offers the strongest assurance available for software, and verification-aware languages have made its automation real. Yet the benefits reach few mainstream developers, most of whose languages have no verification support. Besides, specifying properties and modeling the environment require expertise in formal methods. Proof is therefore reserved for a few celebrated artifacts, while the production code that ships is attested only through review and testing. We introduce neuro-formal verification (NFV), which harnesses that automation for developers of mainstream programming languages: an AI coding agent translates, an established verifier decides, and a question posed in a mainstream language is answered push-button, at empirical accuracy rather than soundness, with a machine-checked proof. Results on a dataset of correct and incorrect solutions to Python programming problems are encouraging: NFV returns a Dafny proof of correctness or of a bug on 57% of the entries at 92% precision, and a CBMC counterexample for 63% of the buggy programs at 90% precision.

阅读 arXiv 原文

软件工程与仓库智能(4 篇)

软件工程与仓库智能 · 6/30 · 2026-08-24需求驱动的候选人搜寻智能体将模糊找人请求视为需求工程任务,提出交互式候选搜寻智能体与配套基准,强调先获取并验证需求再检索An Interactive Agent for Requirement-Driven Candidate Sourcing

Finding people from a natural-language description (``ML engineers transitioning to research roles in biotech'') is increasingly delegated to LLM agents and framed as information retrieval. We argue that it is fundamentally a requirements engineering task: such a request is an under-determined requirement with implicit constraints, many valid answers, and no acceptance criterion, so useful answers require eliciting, validating, and verifying the requirement before search can matter. We present \sys{}, to our knowledge the first interactive, requirements-driven candidate-sourcing agent (it elicits, validates, retrieves, and verifies a vague people-request into a justified slate through bounded elicitation, workflow templates, a two-stage commit protocol, and bidirectional termination guards) and \bench{}, a benchmark that runs the requirements lifecycle (criteria-anchored validation, multi-model evidence-grounded oracle construction, and cost-aware verification). Across $21$ systems and all $691$ requirements, \sys{} dominates breadth ($100%$ coverage at $2.5\times$ the yield) and is \emph{near-orthogonal} to the field, with $90%$ of the people it returns are surfaced by \emph{none} of $20$ strong LLM-plus-web baselines combined. Beyond breadth, an evidence-grounded judging of every system shows \sys{} \emph{recalls} the most relevant real people: $0.241$ of the union pool, $1.9\times$ the next system, with a bootstrap $95%$ interval disjoint from every baseline. \sys{} is thus the strongest \emph{sourcing} engine (the deepest real, reachable candidate pool), while precision-ranking LLMs serve as~complementary verifiers.

阅读 arXiv 原文
软件工程与仓库智能 · 6/30 · 2026-08-24社会技术流程的公平性危害分析提出公平性危害分析方法,在需求工程阶段系统识别公平风险并推导缓解措施,经焦点小组与多案例研究验证Fairness Hazard Analysis for Socio-Technical Processes: A Multiple-Case Study in Bias-sensitive Organisational Settings

Fairness is increasingly recognised as a first-class requirement in socio-technical processes, where interactions among human actors, software systems, and AI technologies may lead to unfair outcomes in decision-making workflows. If left unaddressed, fairness hazards may accumulate and reinforce systemic bias, highlighting the need to engineer fairness proactively. Despite growing interest in fairness-aware systems, systematic methods for identifying fairness hazards in socio-technical processes and deriving requirements-level mitigations remain limited. To support fairness-by-design during requirements engineering (RE), Fairness Hazard Analysis (FHA) is introduced as a methodology for systematically identifying, analysing, and mitigating fairness hazards. FHA is first assessed through a proof-of-concept validation conducted via two focus groups. Then, a qualitative multiple-case study involving two organisations examines its applicability in real-world settings. The proof-of-concept validation highlighted the benefits derived from the structured nature of the method, and suggested the need to include iterative, dialogic reflection with domain experts. In the multiple case-study where FHA was applied, the practitioners involved were positively impressed by the results and confirmed the relevance of the identified fairness hazards (spanning up to 27% of the process elements), as well as the appropriateness of most of the proposed mitigations, while noting that contextual factors might hinder their implementation. The evaluation also highlighted mitigation patterns, such as independent review and collective decision-making, which can be transferred to different organisations. This paper contributes a structured and empirically validated methodology for integrating fairness considerations in RE and preventing systemic bias in socio-technical processes.

阅读 arXiv 原文
软件工程与仓库智能 · 7/30 · 2026-08-22用大模型修复 XR 应用性能缺陷探索以大语言模型自动化修复扩展现实应用性能缺陷,针对真实代码库、缺陷检测与修复工具缺失等挑战XRFix: Exploring Performance Bug Repair of Extended Reality Applications with Large Language Models

As an emerging technology, Extended Reality provides end-users with an immersive experience of interacting with virtual and physical environments. Unlike traditional software, the execution of XR applications involves more computationally complex operations, such as 3D scene rendering, real-time animation, and process simulations. Inefficient coding practices during the software development of XR applications may cause various performance bugs, degrading user experience and even causing motion sickness. Thus, it is an urgent need to develop an automated program repair framework for fixing performance bugs in complex XR programs. However, it is non-trivial to achieve this goal due to several technical challenges: (1) a lack of a real-world XR codebase and bug dataset, (2) no accurate bug detection tool, and (3) no effective bug-fixing tool designed for XR performance bugs. To tackle these challenges, we present a novel large language model-based framework, namely XRFix, to repair performance bugs for open-source XR programs. We first construct a corpus of domain-specific performance bugs built with a codebase from 23 open-source XR projects and a dataset of XR-related bugs containing 104 real-world bugs. Then, we tailor two static analysis tools for accurately detecting bugs in both C# scripts and asset files. Last, we design different prompts to instruct LLMs to fix XR bugs in three types of bug scenarios with different complexities, i.e., single-line level, function level, and class level. We conduct extensive experiments on five off-the-shelf LLMs to evaluate the bug-fixing performance of XRFix. We also compare our XRFix with three SOTA APR approaches. Through static analysis, reference answer comparison, and manual inspection, we demonstrate that our XRFix can effectively fix XR bugs, outperforming SOTA APR methods.

阅读 arXiv 原文
软件工程与仓库智能 · 11/30 · 2026-08-21需求工程中 LLM 的跨任务实证评估通过受控实验与探索性工业案例研究,评估 LLM 在需求分类、规范生成等五项需求工程活动上的表现Large Language Models for Requirements Engineering: A Cross-Task Empirical Evaluation

Requirements-related information is scattered across heterogeneous artefacts such as user feedback, developer discussions, and software repositories, making the extraction of actionable requirements knowledge labour-intensive and hard to scale. Large Language Models (LLMs) can support many Requirements Engineering (RE) activities, from classification and traceability identification to specification and explanation generation, but existing evidence is fragmented across tasks, artefact types, and evaluation settings, and studies rarely offer cross-task evaluations or replication packages. We present two complementary empirical studies evaluating LLMs across five RE-related activities. The first is a controlled experiment on five lightweight open-source LLMs for feedback-driven requirements classification and specification generation. The second is an exploratory industrial case study on two frontier LLMs for traceability link identification and traceability explanation generation using real project artefacts. Classification and traceability identification were assessed with quantitative metrics, and generation tasks through human evaluation. LLM performance is strongly task-dependent, ranging from moderate to high, and no single model consistently outperformed the others, indicating that effective adoption depends on selecting models and prompting strategies per task. Our contributions are: (i) the first cross-task empirical evaluation of LLMs spanning five RE-related activities, (ii) replication materials supporting reproducibility, and (iii) a broader understanding of the capabilities, limitations, and practical readiness of current LLMs for RE.

阅读 arXiv 原文

代码质量与优化(1 篇)

代码质量与优化 · 0/30 · 2026-08-24细粒度跨方法移动重构的形式化形式化语句级 Move 重构为前置条件与步骤,覆盖数据可达性、执行次数、副作用与语法约束,并适配 Java 多Formalizing and Automating Fine-Grained Move Refactorings Across Methods

Developers use automated Move refactorings to improve the modular structure of source code and the assignment of responsibilities. Class- and method-level Move refactorings are automated in modern IDEs, but statement- and expression-level moves that adjust method boundaries remain largely unautomated. We formalize five variants of Move Statement refactoring as preconditions and steps grounded in four basic conditions covering data reachability, execution count, side effects, and syntactic constraints required for compilation, of which all but the side-effect condition are checked statically. Combined with existing techniques, this also yields finer-grained moves of expressions and partial expressions. We further refine the formalization iteratively against a real project, deriving twenty additional preconditions and steps that handle Java syntactic diversity in practice. We evaluate applicability and compilability on ten projects, and behavior preservation in a case study on one of them: Move Statement refactorings yield compilable code in 93.3-97.0% of applicable cases, and the case study shows that the observed behavioral changes stem from side-effect reordering left to developer judgment, not from defects in the statically checked conditions.

阅读 arXiv 原文

UI 与 GUI Agent(1 篇)

UI 与 GUI Agent · 0/30 · 2026-08-24情感驱动的自适应 AI 人设交互提出 AffAdapt 框架,协调语音识别、话轮管理、人设响应、情感状态与具身输出,实现无缝多模态交互AffAdapt: AFFect-driven ADAPTive AI Personas for Seamless Conversations

AI-generated personas are being increasingly used for support, training and simulations. While generative AI models possess abilities to generate affect-aware responses, their embodiment into visual personas is an active area of investigation. Naturalistic exchanges require understanding of the conversational partners' turn completions, whether the agent should respond or keep listening and rely on non-verbal cues aligned with one's emotional states. Seamless human-AI conversation in a multimodal setting requires all modalities being generated to act in coordination. We present AffAdapt, a seamless interaction design framework for AI-personas, which coordinates streaming speech recognition, proactive turn-management, persona-grounded response generation, a persistent emotional state, and synchronized embodied output into a single interaction loop. We demonstrate the architecture in the context of practicing sensitive, high-stakes conversations, and report an initial case study showing fluid turn management and adaptive, persona-consistent behavior, alongside open challenges in interruption handling, open-ended dialogue, and multimodal affective alignment. AffAdapt's interaction loop is a generalizable pattern for coordinating timing, identity, and affect in real-time AI personas - applicable to training, coaching, education, and simulation contexts wherever believable, responsive interaction matters.

阅读 arXiv 原文

个人知识与本体(8 篇)

个人知识与本体 · 3/30 · 2026-08-24面向智能体记忆系统的注入攻击提出 InjecMEM 记忆注入攻击,仅需一次交互即可影响后续相关查询输出,利用高召回锚点与对抗指令实现定向引InjecMEM: Memory Injection Attack on LLM Agent Memory Systems

Memory is becoming a default subsystem in deployed LLM agents to provide persistent personalization and continuity. This naturally prompts a question: will memory system introduce new vulnerabilities into agents? Thus we propose InjecMEM, a novel memory injection attack paradigm that requires only a single interaction (no read/edit access to memory store) to steer later responses of related queries toward a pre-specified output. Guided by the retrieval-then-generate mechanism of memory systems, we craft the injection with a retriever-agnostic anchor and an adversarial command. The anchor contains high-recall topical cues so that downstream retrieval consistently associates the record with the target topic. The command is a short sequence optimized to remain effective under uncertain fused contexts, variable placements, and long prompts so that it reliably steers outputs once retrieved. We learn the command via gradient-based coordinate search, averaging over synthetic prompt templates and insertion positions, and extend it to joint optimization across backbones to study transfer. Evaluated across multiple memory systems and backbone models, InjecMEM achieves reliable topic-conditioned retrieval and targeted generation, remains effective under memory drift, and leaves non-target queries unaffected. Our results underscore the need to harden memory systems and provide a reproducible framework for studying agent memory.

阅读 arXiv 原文
个人知识与本体 · 4/30 · 2026-08-24面向仇恨类别的多智能体反驳生成提出 FIRE 框架,先将仇恨言论分为五类再映射对应反驳策略,并构建含 4784 条实例的 FactualCSCounter with Evidence! A Multi-Agent Memory Efficient Reasoning Framework for Hate Category Informed Counterspeech Generation

Counterspeech effectively neutralizes the impact of online hate. Although prior work explores automated counterspeech generation, it largely emphasizes stylistic control while treating hate speech as homogeneous, overlooking that distinct forms of abuse require fundamentally different counterspeech strategies. To address this gap, we introduce FIRE (Factuality Informed Multi-Agent Reasoning Framework) that first decomposes hate speech into one of the five distinct categories (misinformation, stereotype, conspiracy, dehumanizing, non-factual), and then maps it to a targeted counterspeech style. To facilitate FIRE, we curate FactualCS, a novel dataset of $4,784$ instances that provides the annotations regarding hate categories, reasoning traces, and evidence mappings, which are critical elements for grounded generation that are missing in prior work. A comprehensive evaluation across $28$ baseline configurations demonstrates that FIRE significantly surpasses existing methods, despite using compact agents ($<$2B). FIRE achieves a $\sim$ $12 \%$ and $\sim$ $11 \%$ improvements in factual and category-specific accuracy respectively, while simultaneously reducing toxicity by $\sim$ $11 \%$ relative to the strongest baselines. Further human evaluation confirms that responses generated by FIRE are significantly preferred over the strongest baselines, underscoring its effectiveness for real-world deployment. These findings show that decomposing the underlying intent of hate speech is essential for generating safe, effective, and contextually precise counterspeech.

阅读 arXiv 原文
个人知识与本体 · 0/30 · 2026-08-24经验摊销的长期智能体记忆重排序提出 EARM 框架,将重排序器已有的相关性分数作为可复用检索经验,借在线矩阵与因果补全降低评分开销The Retriever Should Remember: Experience-Amortized Reranking for Long-Term Agent Memory

Long-term language-model agents accumulate memories across interactions, but their retrievers typically do not accumulate retrieval experience. Semantic retrieval is efficient, but embedding similarity does not always reflect whether a memory contains evidence relevant to the current query. Large language model (LLM) rerankers provide stronger query-conditioned relevance scores, yet stateless reranking repeatedly scores a large candidate pool and discards these scores after each query. We introduce EARM, an experience-amortized reranking framework that treats previously acquired LLM relevance scores as reusable retrieval experience. EARM stores sparse query--memory relevance scores in an online matrix, learns their shared structure through causal matrix completion, and combines a small set of newly observed scores with estimated scores to rerank the remaining candidates. The scoring budget decreases as experience accumulates, changing LLM reranking from a repeated per-query expense into a retrieval capability learned over an agent's lifetime. Experiments on long-term conversational memory show that mixed observed-and-estimated reranking improves answer accuracy over semantic retrieval by up to 6.62% and remains effective when only 17.5% of candidates receive direct LLM relevance scores, thereby substantially reducing the inference overhead of LLM reranking. These results motivate a broader view of agent memory: a long-lived agent should remember not only past content, but also how that content has proved useful for retrieval.

阅读 arXiv 原文
个人知识与本体 · 3/30 · 2026-08-24长期智能体记忆的压缩悬崖发现上下文压缩导致安全规则保留率骤降(一轮 53%、五轮 10%),提出知识分流治理框架The Compaction Cliff in Long-Running AI Agent Memory

A safety rule and an episodic log compete for the same tokens in an AI agent's context. When the budget overflows, both are summarized at the same rate; only the rule needs exact wording to remain enforceable. On 20 production agent configurations, Claude Code's /compact prompt on Sonnet 4.6 preserves 53\% of safety rules after one compaction round and 10\% after five. We name this the Compaction Cliff. We address it with Knowledge Triage, a framework that classifies each line of an agent's knowledge base by type and routes each type through its own retention policy. Three deterministic operators implement this triage across the three context-management operations: TypeCompact rewrites items in place under per-type fidelity, TypeDecompose partitions a topic too large to compact safely, replicating in-scope safety rules across partitions, and TypeRetrieve fetches items from external storage with in-scope rules pinned ahead of relevance. On five public corpora, TypeCompact preserves 2--4$\times$ more safety rules than the strongest single-shot LLM compactor at every ratio, with 96\% recall over five rounds. TypeDecompose reaches 0\% locality violations against 93\% under uniform partitioning. TypeRetrieve reaches 100\% recall@50 against 73\% for the best single-shot LLM retriever. On three downstream behavioral benchmarks, we outperform the production Sonnet compactor on medical compliance (paired McNemar $p < 10^{-8}$ on preservation, $N = 200$), the full-policy and hierarchical baselines on retail task pass rate ($p < 0.01$, $N = 115$), and the hierarchical compaction on the airline domain ($p = 0.024$). We release AgentArtifactCorpus (396{,}934 agent configurations from 54{,}628 public GitHub repositories), the classifier, and the reference implementation.

阅读 arXiv 原文
个人知识与本体 · 4/30 · 2026-08-23人设增强的长期智能体记忆检索优化提出 HERO 框架,将对话历史转为保留原文证据的可追踪异构记忆图,并结合查询锚点与用户画像优化检索HERO: Human-profile Enhanced Retrieval Optimization Framework for Long-term Agent Memory

Long-term memory is crucial for personalized responses and long-horizon agent interactions. Existing methods often rely on LLMs to compress or rewrite dialogue histories and use the transformed memories as retrieval evidence. Despite the progress in organizing fragmented contexts, two major drawbacks persist: (1) information loss from compression, which discards fine-grained but later useful details, and (2) semantic drift from rewriting, which erodes the original tone and situated context. In this work, we propose a novel Human-profile Enhanced Retrieval Optimization framework for long-term agent memory (HERO). Specifically, HERO converts the dialogue history into a traceable heterogeneous memory graph that preserves raw dialogue text as evidence for reasoning, thereby mitigating information loss. For retrieval, HERO extracts initial anchors from the current query and incorporates human profiles via an iterative graph traversal; these anchors and profiles provide guidance signals that adaptively activate the most informative regions of the graph. Experiments on two benchmark datasets show that HERO outperforms strong baselines on both factual and personalized reasoning, while providing more faithful access to raw dialogue evidence.

阅读 arXiv 原文
个人知识与本体 · 6/30 · 2026-08-23双层智能体记忆:快写入路由与慢整合借鉴互补学习系统理论,将记忆管理前置到写入阶段,按成本感知路由分类信息,并周期性参数化整合以抑制冗余Dual-Layer Agentic Memory with Fast Write Routing and Slow Consolidation

Large language model (LLM) agents operate in dynamic environments where knowledge continuously evolves. Existing memory systems typically treat external memory as a monotonically growing repository, inevitably leading to retrieval degradation and increasing computational costs over time. We argue that the core challenge is not retrieval alone, but managing the knowledge lifecycle: deciding what to externalize, update, or ultimately internalize. Inspired by Complementary Learning Systems (CLS) theory in neuroscience, we propose Dual-Layer Agentic Memory, a framework that shifts memory management to the write phase through cost-aware epistemic routing and periodic parametric consolidation. Incoming information is categorized as non-write, write-new, or write-update, and routed through a small-to-large model cascade that minimizes routing overhead while filtering redundant memories. A subsequent write-back phase selectively consolidates high-value external memories into model parameters via supervised fine-tuning. Experiments demonstrate the dual efficiency of our approach: a 1.7B/8B cascade prunes up to 68% of redundant external memory while escalating fewer than 50% of inputs, yet retains over 98% of the downstream QA Exact Match (EM) achieved by an exhaustive retention baseline. We further show that periodic consolidation successfully internalizes external knowledge, allowing the router to adaptively suppress redundant writes as the model's epistemic boundaries evolve. Overall, our framework presents a unified paradigm for agent memory: selective externalization followed by selective internalization. Code and dataset will be released upon acceptance.

阅读 arXiv 原文
个人知识与本体 · 3/30 · 2026-08-22经由社交媒体源的间接偏见注入提出 IBIA 间接偏见注入攻击,借外部内容消费在智能体记忆中植入指定立场,结合评论伪装、水印与类别锚定MEMORY Wins All: Indirect Bias Injection Attacks via Social Media Feeds

Personal AI agents routinely consume external content while performing tasks such as web browsing, email processing, and SNS feed summarization, and they retain selected information or execution results in persistent memory for later use. We show that this ordinary ingestion of external content opens an indirect path for manipulating subsequent agent behavior. Based on this observation, we present IBIA, an Indirect Bias Injection Attack that plants an adversary-aligned stance on a specific topic into a victim agent's memory through external content, without direct access to the agent, its memory, or future user queries. For this, IBIA combines three mechanisms: comment cloaking, which keeps the crafted content consistent with the surrounding discussion, comment watermarking, which enables lightweight identification during curation, and category anchoring, which makes the retained stance salient under later related requests. We evaluate IBIA on BiasBench, a benchmark of 6,000 adversary-crafted social comments and 120 email instances. The watermark-based curation identifies 95.9% of the injected comments. Under the OpenClaw setting, IBIA achieves adversary-aligned response rates (AARs) of 91.2% on average across four downstream tasks, including 86.6% on the frontier GPT-5.5. We further propose a memory boundary defense that detects the injected bias and reduces AARs to 80.6%.

阅读 arXiv 原文
个人知识与本体 · 6/30 · 2026-08-22智能体记忆治理的验证信号持久化提出 MemGuard,将验证器输出转为奖励、置信度、标签与不确定性等持久化生命周期元数据,治理记忆准入与漂移MemGuard: Persisting Verifier Signals for LLM-Agent Memory Governance

LLM agents are moving from single-prompt use to long task streams in which reusable memory becomes a core capability for terminal, software-engineering, and web tasks. Such memory is useful only when stored experience remains reliable across hundreds of interactions, but two failure modes break that assumption in practice. The first is unreliable admission: failed trajectories,accidental successes, and misleading observations enter memory because they appear relevant, then mislead later decisions. The second is memory drift: long-running banks accumulate duplicate, stale, and conflicting records that retrieval alone cannot repair. MemGuard's key distinction is to treat verifier output not as a one-shot filter, but as persistent lifecycle metadata. It converts multi-criteria score-token verification into reward, confidence, label, and uncertainty descriptors that are attached to every candidate before activation and reused during retrieval, conflict resolution, summarization, and archival. We evaluate MemGuard on Terminal-Bench 2.0, SWE-Bench Verified, WebArena, and Mind2Web across four backbones, comparing against four memory baselines plus a verifier-only control under matched runtime budgets. Averaged over five seeds, MemGuard achieves the best success metric and lowest average steps in all 16 backbone-benchmark settings, improving over ReasoningBank, the strongest prior baseline among the memory methods we evaluate, with a largest gain of 7.9 success-rate points on WebArena, 5.6 step-success-rate points on Mind2Web, and 2.4-3.5 points on terminal and software-engineering benchmarks. Code is available at https://github.com/whyyyyy123/MemGuard.

阅读 arXiv 原文

人机协同与对齐(0 篇)

本轮该赛道没有候选论文。