公开论文雷达

公开 arXiv 研究简报 · 2026-09-10T00:59:47.784569+00:00

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

别拿好测的信号当结论:八张卡的共同毛病

这八张卡都在说同一件事的不同版本:手里最好测的那个数,往往不是你真正想知道的那件事。先读06213,它用数字和因果方向把这个毛病摆得最清楚;之后按证据硬度往下读。最后两篇只有思路、结果数字缺失,别照着改流程。

推荐阅读顺序

  1. 2609.06213:数字最全还判了因果方向:词法指标F1仅0.485不如猜多数类,语言变化滞后于批准率。
  2. 2609.07282:把"生成不崩"和"还记得"拆成稳定、访问、效用三个视界分开测,概念切得最干净。
  3. 2609.07340:单案例无数字,但戳中盲点:访谈能确认需求好坏,确认不了它和旧系统功能怎么对上。
  4. 2609.05692:同一篇里既报仿真的好数字,也报7个模型只2个见效的坏数字,作者自称初步证据。
  5. 2609.07779:换注意力拓扑做执行前初筛,跨基准跨模型迁移稳,但准确率、AUC数值没给。
  6. 2609.08558:结论具体但场景窄:十用户共享设备,CALFW上owner与non-owner的F1差27.29%。
  7. 2609.05529:指标数字漂亮,但样本量、恶意注入比例、消融组成都没给,先当设计思路看。
  8. 2609.07586:只有流程和80题的评测设计,准确率和拒答率一个数都没有,放最后。
共性方法
八篇都在质疑一个替身指标:测试能不能跑通、生成崩不崩、需求有没有达成共识、用词有没有退化、模型自己会不会拒答——这些好测的量被当成了真正想要的那个性质。处理方式也一致:先把替身和目标拆开,再分别测。
关键分歧
分歧在证据有多硬。06213给了相关、分类、因果三层数字;07282主要靠一个构造性证明;07340是单案例定性、没有量化;05692敢把自己失效的那一半也报出来;05529数字齐但统计口径缺;07586连结果数字都没有。
选择准则
按"能不能改你明天的做法"排:有数字且交代了失效边界的先读;只有定性但戳中盲点的次之;数字漂亮却没说清口径的、以及没有结果数字的放最后,只当思路参考,别直接照搬。

重点深读(8 / 8 篇)

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

形式化与程序验证 4/30

DART: A DAG-Based Reputation and Incentive Framework via Blockchain-Enabled Governance for Trustworthy LLM Multi-Agent Collaboration

多智能体要抗作恶,DART把声誉激励接进DAG编排和链上问责:如果你在做多智能体协作,集中式调度缺少可验证的可靠性与问责,恶意节点会持续破坏输出;DART用DAG编排、声誉激励和区块链智能合约治理,GSM8K Pass@1达93.6%,恶意输出遏制率99.3%,系统成功率恢复到99.8%。

两句看懂

集中式多智能体编排没有对智能体可靠性与行为对齐的正式验证,容易被恶意或不合作智能体破坏;DART加入DAG工作流、声誉与激励评分、区块链智能合约问责机制。五次独立150轮纵向试验与恶意注入测试显示,Full DART任务成功率93.33%±2.26%,输出遏制率99.3%,系统成功率恢复到99.8%。

核心判断

DART能保证的是:用DAG编排+声誉激励+区块链智能合约,把信誉直接绑到任务质量;五次150轮试验任务成功率93.33%,恶意智能体输出遏制率99.3%,说明可验证且抗攻击的协作可行。

关键要点

1. 旧假设失效:集中式编排缺形式化验证,已有链上框架多看交易完整性、少看智能推理,声誉激励也难绑定任务质量。 2. 方法与对照:DART整合DAG编排、能力/声誉感知分配、动态行为更新、多因子激励、智能合约+IPFS问责,并用GSM8K、双智能体142秒全栈构建、五次150轮Full/消融对比、恶意注入四类检查。 3. 结果与动作:GSM8K Pass@1 93.6%,Full DART成功率93.33±2.26%、质量0.9357±0.0117,恶意输出遏制99.3%、成功率恢复99.8%;需要抗作恶时按这个闭环设计。

证据与结果

四类评测对应四类指标:GSM8K数学题Pass@1为93.6%;双智能体142秒完成全栈应用构建,优于集中式基线;五次独立各150轮纵向试验中,Full DART任务成功率93.33±2.26%、输出质量0.9357±0.0117、重试率0.2307±0.0816、分配延迟1.1153±0.0408秒,均优于消融组;持续性与间歇性恶意智能体注入下,输出遏制率99.3%,系统成功率恢复到99.8%。

打开论文原文
它要解决什么
集中式编排的多智能体系统缺少形式化验证,怎样同时保证可靠性、参与度、行为对齐,并抵御持续或间歇性恶意智能体?
研究路径
任务先按DAG拆解;系统按能力匹配度、历史声誉和当前负载动态选执行者。任务执行后,系统依据行为证据校准声誉分数,并改写下一次被选中的概率。多因子激励或惩罚同步写入智能合约,结果与日志存入IPFS,留下可追溯问责记录。
这对工程意味着什么
第一步先把执行后的行为证据写回声誉分数和选取概率,形成闭环反馈;要避开的捷径是只把区块链当交易记录式事后审计,因为它不改变后续任务分配,难以遏制持续作恶节点。
证据定位
五次独立150轮纵向试验中,Full DART任务成功率93.33±2.26%、输出质量0.9357±0.0117,均优于消融版本;注入持续/间歇性恶意智能体后,输出遏制率达99.3%,系统成功率由受攻击状态恢复到99.8%。(筛选维度:形式化验证)
适用边界
摘录未给出GSM8K具体样本量、试验中智能体总数、恶意智能体注入比例与具体作恶方式的详细定义,消融配置的具体组成也未在摘录中列出。
方法与英文摘要

评测按四个场景展开:GSM8K数学推理看Pass@1;两智能体协作构建全栈应用,计时142秒;五次独立150轮纵向试验对比Full DART与消融配置,记录任务成功率、输出质量、重试率、分配延迟;再注入持续性与间歇性恶意智能体,测试隔离与遏制能力。

Large language model (LLM)-based multi-agent systems (MAS) predominantly rely on centralized orchestration and lack formal verification mechanisms for agent reliability, participation, and system-level behavioral alignment. These shortcomings leave open environments severely vulnerable to uncooperative or malicious agents. This work proposes DART, a Directed Acyclic Graph (DAG)-based reputation and incentive regulation framework for trustworthy multi-agent collaboration, combining centralized operational orchestration with blockchain-enabled decentralized governance and accountability. DART unifies DAG workflow orchestration, capability and reputation-aware task allocation, dynamic behavior updates, multi-factor incentives, and smart contract accountability paired with IPFS storage. Under this paradigm, agent selection dynamically balances task alignment, historical reputation, and workload, while post-execution behavioral evidence continuously calibrates agent trust and the probability of future participation. Evaluated across four axes, DART achieves 93.6% Pass@1 on GSM8K and builds a full-stack application in 142 s using two agents, outperforming centralized baselines. Across five independent 150-round longitudinal trials, Full DART achieves a mean task success rate of 93.33 +/- 2.26%, output quality of 0.9357 +/- 0.0117, retry rate of 0.2307 +/- 0.0816, and allocation delay of 1.1153 +/- 0.0408 s, consistently outperforming its ablated configurations DART isolates persistent and intermittent malicious agents, obtaining a 99.3% output containment rate and restoring system success to 99.8%. These results demonstrate the potential of coupling reputation, incentives, DAG-based coordination, and verifiable blockchain-enabled governance to support adaptive and accountable multi-agent collaboration.

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

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

CodeTD: Topology of Attention Detects Hallucinations in Code LLMs

不跑测试也能预警:注意力拓扑可在执行前检出代码大模型幻觉:如果你的场景里功能测试跑不了、跑不全、太贵或不安全,你就缺一个执行前的正确性判断手段。CodeTD用注意力图的拓扑结构量化提示与生成代码的错位程度,在4个基准、10个模型、5种语言上优于CodeJudge等现有基线,且可跨基准迁移。

两句看懂

功能测试常不可用、不完整、成本高或不安全,难以在执行前判断生成代码是否功能正确,CodeTD改用注意力图的拓扑结构量化提示与生成代码的错位程度。研究在10个至多34B参数的代码大模型、HumanEval/MBPP/BigCodeBench/MultiPL-E四个基准、5种编程语言上测试,结果显示该方法优于现有基线,且可跨基准迁移。

核心判断

预执行阶段可以判断生成代码是否功能正确:CodeTD用注意力图拓扑结构量化提示与代码的错位程度,在4个基准、10个模型上优于现有基线,且可跨基准迁移。

关键要点

1. 旧假设:功能测试是唯一可靠的正确性校验;但在UI、分布式/微服务、实时系统、随机行为的机器学习系统中,测试常不可用、不完整、成本高或不安全,静态分析对约占78%的逻辑错误也无能为力。2. 方法:CodeTD计算注意力图中提示与生成代码的拓扑散度作为预执行幻觉分数,在10个至多34B模型、4个基准、5种语言上与CodeJudge、TOHA等基线做受控对比,并测跨基准迁移。3. 结果:检测效果优于基线且跨基准、跨模型迁移稳定,工程师可在测试不可行场景用它做执行前初筛。

证据与结果

评测用HumanEval、MBPP、BigCodeBench、MultiPL-E四个基准,覆盖5种编程语言,测试10个至多34B参数的Code LLM。标签依据功能测试的可执行正确性,功能不正确即视为幻觉;错误案例中逻辑错误约占78%(Appendix O)。评测含基准内检测与跨基准迁移两种模式,对比CodeJudge和TOHA(检测RAG幻觉的注意力图结构方法)等基线。结果:CodeTD优于基线,跨基准、跨模型迁移性能稳定。

打开论文原文
它要解决什么
功能测试不可用、不完整、成本高或不安全时,能否在执行前判断生成代码是否功能正确?这是CodeTD要回答的问题:用注意力图的拓扑特征做预执行幻觉检测。
研究路径
生成代码时,模型注意力图里提示部分与生成代码部分的连通模式反映两者的对齐程度。CodeTD对这两部分做拓扑数据分析,计算拓扑散度作为幻觉分数:错位越大,幻觉风险越高。与熵等标量指标不同,拓扑特征捕捉的是结构层面的错位。研究还发现部分注意力头在多种语言上都能稳定指示幻觉。
这对工程意味着什么
第一步行动:在功能测试不可行的场景,把生成模型注意力图的拓扑散度接入流水线,做执行前的代码正确性初筛。要避免的捷径:不要只依赖静态代码分析——它对约占78%的逻辑错误无能为力;也要记住该分数只是风险信号,不能替代最终功能测试或安全审查。
证据定位
CodeTD在10个模型、4个基准上的检测效果优于CodeJudge、TOHA等最新基线。分类器跨基准迁移(如HumanEval/MBPP/BigCodeBench/MultiPL-E之间)仍保持有效,跨模型迁移也不明显掉点。部分注意力头在多种编程语言上都是稳定的幻觉指示信号。(筛选维度:可复核评测、软件工程方法)
适用边界
幻觉定义仅限功能不正确,不覆盖安全、健壮性问题的全部形态。方法依赖可访问注意力图的白盒模型。具体准确率、AUC等数值结果未在提供文本中给出。
方法与英文摘要

从Code LLM生成代码时的注意力图中取出提示与生成代码两部分,做拓扑数据分析,计算两部分连通模式的拓扑散度,作为幻觉分数。实验用HumanEval、MBPP、BigCodeBench、MultiPL-E四个基准,覆盖5种编程语言,测试10个至多34B参数的Code LLM,与CodeJudge、TOHA等基线比较,并做跨基准、跨模型迁移测试。

As AI-code assistant tools become widespread, automatic assessment of the correctness of generated code becomes a significant challenge. Code LLMs are prone to hallucinations, which may lead to code that does not solve the required problem, or even to code with severe security vulnerabilities. In this paper, we introduce CodeTD -- the first approach to pre-execution assessment of code correctness based on topological data analysis (TDA) of Code LLMs' attention maps. Our method quantifies prompt-generation mismatch using topological patterns of attention maps. We carry out experiments with common benchmarks (HumanEval, MBPP, BigCodeBench, MultiPL-E), 5 programming languages and 10 Code LLMs of size up to 34B parameters. The experimental results show that the proposed method outperforms recent baselines. Moreover, CodeTD is transferable between coding benchmarks.

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

When Stakeholder-centric Requirements Engineering is Not Enough: An Action Research Study on Legacy System Modernisation

做遗留系统差距分析,只靠访谈收集需求不够:需求再正确,也对不上旧系统功能:如果你负责遗留系统改造,习惯用访谈加排序来定需求,这个案例值得先看:一家跨国能源企业用完整的利益相关者方法做差距分析,需求被认为正确易懂,但需求和旧系统功能怎么对应,大家始终谈不拢,差距分析失去基线。方法本身没问题,问题是它管不到系统那一侧。

两句看懂

以往有个隐含假设:访谈式需求工程足以支撑遗留系统的差距分析,这项研究在一家跨国能源企业用访谈、Delphi、MoSCoW的完整流程检验了它。结果是需求本身被评为正确易懂,但需求与遗留系统功能的映射未达成一致,说明这套方法必要但不充分。

核心判断

以利益相关者为中心的需求工程,对遗留系统改造是必要条件但不是充分条件。证据就一条:需求本身被评为正确易懂,但需求与遗留系统功能的映射未能达成一致,差距分析缺乏可靠基线。

关键要点

1. 旧假设:以往改造研究多谈重写、云迁移、微服务拆分,背后假设是只要收齐利益相关者知识就能拿需求比对现状,但这个假设没被验证过。2. 方法与检验:在一家跨国能源企业(排放数据分析系统、多国部署、系统异质)做行动研究,依次做利益相关者识别、半结构化访谈、Delphi多轮共识、MoSCoW排序,再用共识需求映射遗留系统功能。3. 结果与做法:需求被一致认可为可理解、正确,但需求-功能映射未达成一致,差距分析无可靠基线;结论是利益相关者中心法必要但不充分,需补充迭代式、证据驱动、人工加工具辅助的系统分析。

证据与结果

评估是定性判断,看两个'一致':一是利益相关者是否一致认可需求可理解、正确,二是需求到遗留系统功能的映射能否达成一致。结果前者达成、后者未达成,差距分析因此没有可靠基线。案例是单一跨国能源企业的排放数据分析遗留系统(支持可持续统计与外部审计,多国部署导致异质性),原文未提供参与人数等样本规模,也没有量化指标或数值。

打开论文原文
它要解决什么
以利益相关者为中心的需求工程(访谈、Delphi、MoSCoW),能不能独自支撑遗留系统的现状与目标差距分析?
研究路径
机制分五步,问题出在最后一步:1)识别利益相关者;2)半结构化访谈,获取系统现状与未来需求;3)Delphi法多轮反馈,让各方对需求达成共识;4)MoSCoW法给需求分级排序;5)把共识需求与遗留系统实际功能做映射。前四步都顺利,共识也形成了,但第五步映射时各方意见合不拢——人能对'想要什么'达成一致,不代表能对'旧系统现在有什么'达成一致。
这对工程意味着什么
第一步行动:在做差距分析时,在访谈类需求收集之外,追加对遗留系统的工具辅助功能核验,并迭代校正映射结果,直到需求-功能映射达成一致。要避开的捷径:把'需求被各方认可'当成'差距分析已可靠'的信号——访谈只能确认需求好懂正确,确认不了它与现状系统的对应关系。
证据定位
参与者普遍认为最终得到的需求可理解、正确,这一点达成了一致。但在需求与遗留系统现有功能的映射上,参与者未能达成一致意见,差距分析因此缺乏可靠基线。研究为单案例定性评估,原文没有给出量化指标或参与人数。(筛选维度:置信度与不确定性、软件工程方法)
适用边界
这是单一案例研究:一家跨国能源企业、一个排放数据分析类遗留系统,没有量化指标和样本规模。结论能否推广到其他行业、其他类型的改造项目,原文未展开,引用时需谨慎。
方法与英文摘要

行动研究,案例是一家跨国能源企业的排放数据分析与可持续统计遗留系统,系统在多国部署、彼此有异质性。做法是五步:先识别利益相关者;再做半结构化访谈,收集现状与未来需求;然后用Delphi法多轮反馈让各方对需求达成共识;接着用MoSCoW法给需求排优先级;最后把共识需求与遗留系统的实际功能做映射,检验能否支撑差距分析。

Legacy system modernisation is a major challenge in digital transformation, especially when organisations depend on long-lived, business-critical systems that are only partly understood. In such context, organisations must define future needs while determining what current systems actually do and which functions to retain, adapt, or replace. Modernisation is therefore not only a technical challenge but also a requirements engineering (RE) problem, shaped by stakeholder perspectives. This study examines how far stakeholder-centric RE can support gap analysis between the system-as-is and the system-to-be in a legacy modernisation context. We conducted an action research study in a multinational energy company engaged in system modernisation. In the study, we applied stakeholder-centric RE practices, including stakeholder identification, semi-structured elicitation interviews, agreement-building through the Delphi method, and prioritisation with the MoSCoW method. The results show that this process was effective in producing requirements stakeholders generally viewed as understandable and correct, but less effective in achieving agreement on how elicited requirements mapped to legacy system functionality. The findings suggest that stakeholder-centric RE is necessary but not sufficient, pointing to the need for uncertainty-aware, iterative, and evidence-based modernisation practices that combine stakeholder perspectives with manual and tool-assisted analysis of legacy systems.

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

Regret Dominates Surprise: Design-Time Requirements Engineering for Agentic-AI Safety

设计时安全门控:放大而非替代训练:MS-RGR用惊讶和后悔两信号在GORE需求模型中选择常规自主、反思或升级人工。仿真使静默失败趋零、风险探测提速17.5倍;对7个LLM的事后门控仅在预门控拒绝率超80%时提升拒绝率,其余5个模型无效。

两句看懂

GORE类需求框架缺乏应对认知不确定性的机制,MS-RGR用惊讶与后悔双信号在设计时门控智能体的常规自主、反思推理与升级人工三态。仿真中静默失败趋零、风险探测提速17.5倍;对208个AGENTHARM场景7个LLM的事后门控仅使预门控拒绝率超80%的模型提升(84.1%→90.9%),其余5个模型无变化。

核心判断

能否在部署前为智能体自主设置可验证安全边界?可以,但效果有限:仿真中风险探测提速17.5倍、静默失败趋零;对7个LLM的事后测试显示门控仅放大已有安全能力(84.1%→90.9%),对弱基线模型无效。

关键要点

1. GORE等主流需求工程框架缺乏在认知不确定性下评估、规约与操作化安全自主的机制;既有的惊讶或后悔信号多是事后或运行时使用,在决策瞬间不可逆时保护有限,升级人工与否被留给运行时启发式而非可验证工程约束。 2. MS-RGR在GORE目标模型上叠加两信号(认知新颖性/惊讶、评估风险/后悔),区分常规自主、反思推理、升级人工三态;先在养老监护与自动驾驶两域做100种子随机仿真并做结构消融,再把DRI门控事后套用到208个AGENTHARM场景(8类危害)、7个LLM录制的执行轨迹上做代理测试。 3. 仿真结果显示静默失败降至近零、风险探测比纯传感器基线快约17.5倍且可用LTL安全属性追溯;但事后门控测试中只有预门控拒绝率超80%的2个模型拒绝率提升(如84.1%→90.9%),其余5个模型无变化,说明该机制放大而非替代模型自身安全训练,尚属初步可行性证据。

证据与结果

仿真:养老监护+自动驾驶两工作流域,100随机种子+结构消融,域无关;指标为静默失败率与风险探测时延,对比对象为纯传感器基线,MS-RGR探测提速约17.5倍,失败率趋零,LTL可追溯。代理测试:AGENTHARM基准208个场景、8类危害,覆盖7个LLM,DRI门控事后应用于录制的执行轨迹,比较门控前后拒绝率;仅预门控拒绝率超80%的2个模型提升(如84.1%→90.9%),其余5个模型无变化,表明门控依赖模型自身安全基线。

打开论文原文
它要解决什么
在需求工程层面,如何在部署前为智能体自主行为设置可验证的安全边界,而不仅依赖模型自身的安全训练?
研究路径
步骤:1)在GORE目标模型中定义惊讶(新颖性检测)与后悔(评估风险)两信号阈值;2)按信号组合判定走常规自主/反思推理/升级人工(Goal Sacrificing,替换为人工看护);3)在养老监护、自动驾驶两域跑100种子随机仿真+结构消融,记录静默失败率与风险探测时延,并用LTL验证安全属性;4)把DRI门控离线套用到208个AGENTHARM场景、7个LLM的执行轨迹上,比较门控前后拒绝率。
这对工程意味着什么
工程上应把此类门控当作对已有安全训练的补充,部署前用执行轨迹重放测试门控在不同基线安全水平模型上的效果;不要把'加了门控'当作可替代模型安全训练的捷径,因为对弱基线模型门控测试显示无效。
证据定位
仿真:静默失败降至近零,风险探测比纯传感器基线快约17.5倍,且可用LTL安全属性追溯。事后门控:仅2/7个预门控拒绝率超80%的LLM提升(如84.1%→90.9%),其余5个模型无改善。(筛选维度:置信度与不确定性、软件工程方法)
适用边界
AGENTHARM部分为事后代理实例化,基于录制执行轨迹而非实时运行时门控;仅7个LLM、208个场景,门控增益仅体现在预门控拒绝率超80%的2个模型上,作者称其为初步可行性证据,尚待进一步验证。
方法与英文摘要

MS-RGR基于GORE目标模型,用epistemic surprise(新颖性检测)与cognitive regret(评估风险)两信号判断走常规自主/反思推理/升级人工三态。先在养老监护与自动驾驶两个工作流域做100种子随机仿真并做结构消融;再将DRI门控事后应用于208个AGENTHARM场景(8类危害)在7个LLM上录制的执行轨迹,比较门控前后拒绝率。

Requirements engineers for agentic-AI domains face challenges in evaluating, specifying, and operationalizing safe autonomy. Mainstream frameworks, such as Goal-Oriented Requirements Engineering (GORE), lack mechanisms to systematically address these challenges under epistemic uncertainty. We contribute an approach that builds on GORE to model and simulate safe autonomy in agentic-AI systems. We introduce a novel Regret-Dominance Mechanism (MS-RGR) to operationalize safe autonomy. MS-RGR uses two signals: epistemic surprise (novelty detection) and cognitive regret (evaluative risk) to address the trilemma problem: should the agent operate in routine autonomy, undergo reflective reasoning, or escalate to human? We instantiate MS-RGR in elderly care monitoring and autonomous driving. A 100-seed stochastic simulation shows MS-RGR reduces silent failures to near-zero and detects risk approximately 17.5 times faster than a sensor-only baseline, remaining formally traceable via LTL safety properties. A retrospective proxy instantiation applying the DRI gate post-hoc over execution traces from 208 AGENTHARM scenarios across seven LLMs shows the gate improves harmful-task refusal only for models with strong baseline safety (over 80% pre-gate refusal, e.g., 84.1% to 90.9%), indicating MS-RGR amplifies rather than substitutes for model-level safety training. We discuss threats to validity, positioning MS-RGR as initial feasibility evidence for design-time safety constraints in agentic-AI requirements engineering.

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

A Tool-Augmented, GPT-4 Chatbot for Real-Time Repository Data Analysis

GPT-4加工具调用做仓库问答,思路可行但准确率尚无数字支撑:如果你在维护仓库问答机器人,这条思路值得看一眼:它用解析意图、选工具、调GitHub实时API替代了嵌入检索管道,省去向量库维护;但注意,摘录没有给出准确率,能不能替代检索式架构还没有数字证明。

两句看懂

以往多组件仓库问答依赖向量检索和文档匹配,该工作改为解析查询意图后选择工具、调用GitHub REST API取实时数据、由GPT-4生成回答。评测用80道题覆盖五类问题并加入域外拒答测试,但摘录未披露具体准确率结果。

核心判断

该架构用解析查询、选工具、调用GitHub REST API、GPT-4生成回答来处理仓库问题,但能否替代检索式架构尚未被数字证实:80题5类评测的具体准确率未在摘录中给出。

关键要点

1.旧架构靠嵌入模型加文档检索器拼接答案,该工作假设解析意图后选工具可省去检索管道,但摘录未给出两种架构的直接对比数字。2.方法是固定系统提示词和工具清单,解析查询、按意图选GitHub REST API工具取实时数据、交GPT-4生成回答;对照检查用80题分5类,外加域外问题测试拒答行为。3.决定性结果缺失:摘录未列出准确率或拒答成功率,结论只能是思路可试,实际采用前须以完整正文数字为准。

证据与结果

自建评测集共80道GitHub仓库相关问题,分5类:Issues、Pull Requests、Commits、复合问题、仓库总体信息,另加入域外问题测试拒答行为。摘录未给出各类问题的准确率、拒答成功率,也未说明是否与嵌入检索式基线做同条件对比。

打开论文原文
它要解决什么
能否用解析查询意图、选择工具、实时调用API的方式,替代嵌入检索式多组件仓库问答系统,准确回答GitHub仓库问题?
研究路径
1)系统提示词声明智能体为Github-chatbot并绑定仓库URL占位符;2)解析用户自然语言查询提取相关参数;3)按查询意图从工具清单中选择对应工具;4)调用GitHub REST API获取实时仓库数据;5)将数据交给GPT-4生成详细回答。
这对工程意味着什么
第一步行动:搭仓库问答原型时,先固定工具清单和系统提示词做意图路由,再调真实API取数据交LLM生成,跑通流程再看效果。要避开的捷径:不要仅凭这份摘录就认定该方案准确率超过检索式基线,摘录没有提供任何对比数字。
证据定位
摘录只描述了评测设计:80道题覆盖5类问题,另有域外拒答测试。摘录没有给出各类问题的准确率、拒答成功率,也没有与嵌入检索式基线的同条件对比数字。(筛选维度:软件工程方法)
适用边界
评测集仅80题且为自建,未说明仓库来源、语言分布及问题采样方法;摘录未提供准确率、拒答率等结果数字,也未说明是否与检索式基线做同条件对比;工具选择在参数解析出错或意图不明确时的失败模式也未给出。
方法与英文摘要

流程分五步:系统提示词声明智能体为Github-chatbot并绑定仓库URL占位符;解析自然语言查询提取参数;按意图从固定工具清单中选工具;调用GitHub REST API取实时数据;交GPT-4生成详细回答。评测集为自建80题,分Issues、Pull Requests、Commits、复合问题、仓库总体信息5类,另加域外问题测试拒答。

Software repositories contain vast amounts of data on code contributions, bug reports, and project activities, yet this information remains challenging for non-technical stakeholders and developers to access due to limited expertise in querying repositories. To address this, we introduce a novel chatbot architecture leveraging OpenAI's GPT-4 model for automated extraction and analysis of repository data. In contrast, our architecture takes a structured path first by parsing the user's query to extract relevant parameters, then selecting the correct tool to employ based on that analysis, and finally invoking the GPT-4 model to create a highly detailed response. In contrast to previous work based on multi-component systems with embedding models and document retrievers, our architecture inverts the process by relying on prompt engineering and tool selection to fit with the query intent. To validate our approach, we conducted experiments on various question types, including Issues, Pull Requests, Commits, Compound Questions, and General Repository Information, evaluating our target prompts' ability to improve the accuracy of responses from the model. Beyond demonstrating the utility of this architecture to a diverse set of users, our findings suggest that this architecture can make repository data more accessible to technical and non-technical audiences through the production of actionable insights.

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

Beyond Lexical Metrics: Sentence-Embedding Detection of Reviewer Habituation in AI Code Review

审稿人松没松懈,词法指标测不出,句向量能测出:如果你负责监控AI代码评审的质量退化,只看评论用词会漏报:审稿人批准率确实随经验上升(30.5%→36.6%,p=8.6e-8),但四项词法特征全部平坦。真正有效的方法是用句向量质心漂移检测,再用格兰杰因果检验判断方向——结果显示语言变化滞后于批准行为,不是先兆。

两句看懂

审稿人批准率随经验从30.5%升到36.6%(p=8.6e-8),但四项词法特征在经验分组间全部平坦,分类F1仅0.485,低于多数类基线。改用all-MiniLM-L6-v2句向量后,质心漂移显著(p<0.001),MLP分类F1达0.74;格兰杰检验进一步显示批准率变化领先语言变化(四个滞后阶p<0.001,反向仅一个阶显著),语言是滞后指标而非先兆。

核心判断

审稿人对AI代码的“橡皮图章”式松懈真实存在(批准率30.5%→36.6%),但词法指标完全测不出(F1=0.485低于基线),句向量质心漂移能测出(MLP F1=0.74);且格兰杰检验方向不对称表明,语言退化是批准行为变化的滞后结果,不能用作早期预警。

关键要点

1. 旧假设失效:原以为审查语言会随经验退化、可提前预警松懈,但四项词法特征(词汇多样性、香农熵、技术具体性、可操作性)在207天11429次评审中无单调下降(|ρ|≤0.53,p≥0.11),逻辑回归F1=0.485低于多数类基线。 2. 方法与对照:按审稿人经验十分位数分组,用all-MiniLM-L6-v2提取早晚期评论句向量质心,以每位审稿人内部随机置换作为零假设基线,再做双向格兰杰因果检验(各四个滞后阶)。 3. 决定性结果与行动:批准率30.5%→36.6%(p=8.6e-8),句向量MLP F1=0.74对词法MLP的0.59;格兰杰检验显示批准率变化领先语言变化(p<0.001)——监控应盯批准行为和句向量漂移,别指望词法预警。

证据与结果

数据:AIDev语料库,5个AI编码智能体,207天,400名重复审稿人,11429次评审,10104条人工行内评论。词法特征按经验十分位数比较:|ρ|≤0.53,p≥0.11,Bonferroni校正后Mann-Whitney p≥0.36。分类:词法特征逻辑回归F1=0.485(低于多数类基线);句向量MLP(五折分层交叉验证)F1=0.74;同样MLP换词法特征仅0.59。因果:批准率→技术具体性四个滞后阶均p<0.001,反向仅1/4阶显著(p=0.036)。

打开论文原文
它要解决什么
一个实际问题:审稿人对AI生成代码越审越熟之后,会不会开始放松?传统思路是看评论用词有没有退化,并假设语言变化会先于批准行为出现,可以当预警信号。这个假设成立吗?
研究路径
机制上分三步。第一步证伪:按经验十分位数算四项词法特征均值,做Spearman相关与Mann-Whitney检验,结果平坦,逻辑回归也分不出早晚期。第二步测漂移:用all-MiniLM-L6-v2把评论编码成向量,算每位审稿人早期与晚期质心的距离,再与该审稿人内部随机打乱时间顺序得到的置换分布比较——真实漂移显著大于随机(p<0.001),说明评论语义结构真的变了。第三步定方向:把批准率和技术具体性信号分成50个百分位箱,做双变量格兰杰检验,批准率→语言在四个滞后阶全部显著(p<0.001),语言→批准率仅一阶显著(p=0.036),因果方向是行为先变、语言后跟。
这对工程意味着什么
第一个行动:给评审流水线采集评论的句向量,定期算每位审稿人早晚期质心漂移并做置换检验,同时直接监控批准率变化。要避开的捷径:不要图省事只统计词汇多样性、香农熵这类表面词法指标当预警——本研究中它们分类效果差于随机猜多数类,而且语言信号本身滞后于行为变化,等它在用词里显形时,松懈早已发生。
证据定位
批准率从30.5%升至36.6%(Wilcoxon p=8.6e-8,d=0.25),松懈确实存在。但四项词法特征无单调下降(|ρ|≤0.53,p≥0.11,Bonferroni校正后p≥0.36);词法特征逻辑回归F1=0.485,低于多数类基线,连随机猜多数类都不如。句向量侧:质心漂移显著大于随机置换零假设(p<0.001);嵌入特征MLP达F1=0.74,同样MLP用词法特征仅0.59。(筛选维度:软件工程方法)
适用边界
数据仅来自AIDev语料库的207天窗口、400名重复审稿人和5个AI智能体,评论均为人工行内评论。结论对更长时间跨度、其他平台或其他智能体的适用性未验证。
方法与英文摘要

研究基于AIDev语料库,覆盖207天内400名重复审稿人的11429次评审和10104条人工行内评论,涉及5个AI编码智能体。词法侧:计算词汇多样性(MTLD)、香农熵、技术具体性、建设性可操作性四项特征,按审稿人经验十分位数分组比较,并训练逻辑回归分类早晚期。向量侧:用all-MiniLM-L6-v2编码评论,计算每位审稿人早期/晚期质心距离,与其内部随机置换分布做Wilcoxon配对检验,再用质心距离等三项统计量训练小型MLP做五折分层交叉验证。最后对50个百分位分箱信号做双向格兰杰因果检验,各测四个滞后阶。

Code review is a key quality checkpoint between AI-generated code and production. As AI coding agents submit pull requests at scale, it is unclear whether reviewers reduce scrutiny with repeated exposure and whether review comments reveal this change. We study 11,429 reviews from 400 repeat reviewers over 207 days, paired with 10,104 human-authored inline comments from AIDev. Approval rates rise from 30.5% in reviewers' early periods to 36.6% in late periods (Wilcoxon p = 8.6 x 10^-8; Cohen's d = 0.25). However, four hand-crafted linguistic features - lexical diversity, Shannon entropy, technical specificity, and constructive actionability - show no monotonic decline across exposure deciles (all Spearman absolute rho <= 0.53, p >= 0.11; Bonferroni-corrected Mann-Whitney p >= 0.36). A logistic-regression classifier based on these features reaches F1 = 0.485, below the majority-class baseline. Sentence-embedding structure does carry signal: reviewers' late-period comment centroids shift farther from their early-period centroids than under within-reviewer random permutations (Wilcoxon p < 0.001), and a small MLP using three embedding statistics reaches F1 = 0.74 under 5-fold reviewer-stratified cross-validation. Granger analysis shows that approval-rate changes predict later shifts in technical specificity at all tested lags (p < 0.001), while the reverse direction is significant at only one of four lags. Reviewer adaptation is therefore detectable in latent distributional structure rather than in classical lexical metrics, and language shifts follow rather than precede changes in approval behavior.

代码质量与优化(0 篇)

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

UI 与 GUI Agent(0 篇)

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

个人知识与本体(2 篇)

个人知识与本体 6/30

Separating Stream Stability from Long-Term Recall in Language Models

生成长期稳定不等于模型记住了早期内容:如果把流式生成“不崩溃”当成“有长期记忆”,长上下文系统会被误判并留下不可用风险。论文提出ThreeH,在同一状态和算力预算下分别测稳定、访问、效用三种视界,避免用一个结果代替记忆能力。

两句看懂

以往评测容易把流式生成的“无限稳定”直接当成“长期记忆”,但命题1证明滑动窗口W之外的历史对输出没有因果影响。128K token流和延迟回忆实验显示,注意力锚点能让稳定视界趋于无穷,却把访问、效用视界限制在窗口W内;循环状态与检索机制才能扩大这些视界。

核心判断

流式生成稳定不等价于长期记忆。注意力锚点只稳定生成过程,不扩大模型可利用的历史;命题1证明访问、效用视界受滑动窗口W约束,128K token流实验也表明窗口外信息对锚点方案如同已经遗忘。

关键要点

1. 旧判断把“流式生成不崩溃”误当成“长期记忆有效”,但困惑度、needle检索和下游任务准确率衡量的并非同一种能力。 2. ThreeH在同一状态预算与算力预算下分别测稳定、访问、效用视界,并用128K token长流、延迟绑定回忆和延迟决策任务作控制检查。 3. 注意力锚点的稳定视界可趋于无穷,但访问和效用视界被限制在窗口W内;部署前应补测这两个视界,必要时加入循环状态或检索。

证据与结果

ThreeH在同一状态和算力预算下,对同一模型分别测预测损失偏差、反事实干预下的因果影响范围,以及任务准确率随信息保留距离的变化。实验覆盖128K token长流、延迟绑定回忆和延迟决策任务。纯注意力锚点方案采用StreamingLLM式滑动窗口加sink token,其稳定视界趋于无穷,但访问与效用视界被压缩到窗口W内;加入循环状态或检索机制后,访问与效用视界明显扩大。摘录未提供具体数值表。

打开论文原文
它要解决什么
注意力锚点让流式生成保持无限稳定,但这是否意味着模型仍能访问并利用已经滑出缓存的历史内容?
研究路径
论文将流式系统写成状态更新Mt=U(Mt-1,xt),并限制状态大小|Mt|≤B。稳定视界衡量预测损失偏差不超过ε的最长流长度,访问视界通过反事实干预检查token xi能否因果影响输出yt,效用视界衡量维持指定任务表现所需的最大信息保留距离。论文进一步构造平稳阶数为W的token过程和只使用最近W个token的模型,证明其稳定视界可为无穷,而访问与效用视界不超过W。
这对工程意味着什么
第一步:部署前用ThreeH分别测出访问视界和效用视界的实际窗口范围。要避免的捷径:不要只因模型长时间生成不崩溃,就认定它仍记得早期内容。
证据定位
命题1表明,滑动窗口W之外的内容对输出因果无关,因此稳定视界可以为无穷,而访问视界和效用视界不超过W。128K token流实验显示,注意力锚点能保持局部语言建模稳定,但无法利用窗口外内容。加入循环状态或检索机制后,语义视界明显延长。(筛选维度:形式化验证、可复核评测)
适用边界
命题1是构造性形式化证明,基于理想化的有界状态模型和平稳token过程,并不是直接的大规模实测数值。实验场景限于128K token流、延迟绑定回忆和延迟决策任务,摘录也未给出具体准确率或损失数值。
方法与英文摘要

论文先证明有界状态自回归流式模型的命题1:定长滑动窗口W之外的历史对输出没有因果影响。随后提出ThreeH评测协议,在相同状态大小和计算预算下,对同一模型分别测量稳定视界、访问视界和效用视界。实验使用128K token长流、延迟绑定回忆任务和延迟决策任务,并比较纯注意力锚点(StreamingLLM式)方案与加入循环状态或检索机制的方案。

Methods for streaming language models are often discussed alongside long-context and memory systems, although they solve different problems. An attention sink can stabilize autoregressive generation over an indefinitely long stream while the model remains unable to use content that has left its recent-token cache. We argue that this distinction should be explicit in system claims and evaluation. We introduce three horizons: the stability horizon, over which predictive behavior remains well behaved; the access horizon, over which past content can still causally affect the output; and the utility horizon, over which a task retains acceptable performance. We show constructively that the stability horizon can be infinite while the access and utility horizons are finite. We then propose ThreeH, an evaluation contract that measures all three horizons under a common state and compute budget. Applying the framework to attention-sink streaming clarifies its strength, constant-memory, stable generation, without treating anchor tokens as semantic memory. The framework exposes roles for cache policies, recurrent state, retrieval, and external memory. Experiments on 128K-token streams, delayed binding recall, and delayed decisions show that attention sinks preserve local modeling but not content beyond the active cache; recurrent and retrieval state extend the semantic horizon.

个人知识与本体 4/30

Personalizing LLM Agent Memory Using Biometrics

共享助手防串记:检索前先匹配人脸或掌纹,CALFW上F1差距27.29%:多人共用一台智能设备时,账号和会话都分不清当前说话的人是谁,记忆就会串用、隐私会泄露。Bio-Memory的做法是给每条记忆绑上生物特征嵌入,检索时先做人脸或掌纹匹配,再做语义排序。测试显示,人脸库CALFW上owner与non-owner的F1差距达27.29%,身份区分效果明显。

两句看懂

共享设备下账号或会话无法保证请求者与记忆归属者一致,Bio-Memory为A-Mem每条记忆加生物特征嵌入,检索先匹配生物特征再排语义。LoCoMo十用户场景测试7个人脸库、10个掌纹协议,CALFW上owner/non-owner的F1差距达27.29%,验证方法有效。

核心判断

生物特征能作为共享环境记忆检索的有效身份控制信号:CALFW人脸场景F1差距达27.29%,MS_Blue掌纹场景F1差距25.75%,owner与non-owner查询被明显区分。

关键要点

1. 旧假设是身份由账号、用户ID或会话边界外部提供,但共享设备中账号可共用、会话可保持激活,无法保证当前物理请求者就是记忆归属者。 2. Bio-Memory在A-Mem每条记忆上附加生物特征嵌入,检索先用生物特征探针筛出候选池再做语义排序;在LoCoMo十用户场景下用7个人脸基准库和10个掌纹协议做了受控评测。 3. 人脸CALFW上owner/non-owner的F1差27.29%、BLEU-1差21.15%,掌纹MS_Blue上F1差25.75%、BLEU-1差19.22%;共享设备的记忆检索应加生物特征前置过滤。

证据与结果

评测基于LoCoMo构建10用户共享助手场景,叠加7个公开人脸识别基准(如CALFW)和10个掌纹识别协议(如MS_Blue)。对比owner与non-owner查询的回答质量,指标为F1和BLEU-1。人脸场景CALFW差距最大:F1差27.29%、BLEU-1差21.15%;掌纹场景MS_Blue差距最大:F1差25.75%、BLEU-1差19.22%。

打开论文原文
它要解决什么
共享代理场景下,记忆检索能否只靠语义相似度确定请求者身份,还是必须引入生物特征作为额外识别信号?
研究路径
Bio-Memory基于A-Mem,分五步:①给每条记忆笔记附加生物特征嵌入(人脸或掌纹);②推理时提取当前请求者的生物特征探针;③将探针与已存嵌入匹配,筛出匹配的候选记忆池;④只在候选池内做语义相似度排序;⑤生成回答。
这对工程意味着什么
第一步行动:给共享设备的记忆系统加一层生物特征匹配前置过滤,再做语义检索。要避免的捷径:只靠账号或会话状态判断身份,这条捷径不可靠。
证据定位
人脸库CALFW上owner与non-owner差距最大:F1差27.29%、BLEU-1差21.15%。掌纹协议MS_Blue上差距F1 25.75%、BLEU-1 19.22%。两组数字说明生物特征匹配能有效区分请求者身份。(筛选维度:可复核评测)
适用边界
评测基于LoCoMo对话与公开人脸/掌纹基准的组合构造,场景限定10用户共享设置;未见针对真实采集噪声或生物特征欺骗攻击的说明。
方法与英文摘要

基于LoCoMo构建10用户共享助手场景。在A-Mem每条记忆笔记上附加生物特征嵌入。检索分两步:先用人脸(7个基准库)或掌纹(10个协议)做生物特征匹配,筛出候选记忆池;再对候选池做语义相似度排序,生成回答。

Personalized memory helps LLM agents deliver stable, tailored assistance by storing and reusing user-specific data across interactions. In multi-user scenarios, however, retrieval must consider not only semantic similarity but also whether the current requester matches the identity associated with the stored memory. We propose Bio-Memory, a biometric-aware memory architecture that conditions memory retrieval on both semantic similarity and biometric matching. Built on top of A-Mem, Bio-Memory augments each atomic memory note with a biometric embedding and uses biometric matching to form the retrieval candidate pool before semantic ranking. We evaluate Bio-Memory on LoCoMo in a 10-user shared-agent setting over 7 face benchmarks and 10 palmprint protocols. Across datasets, Bio-Memory consistently separates owner and non-owner queries. Under face-based personalization, the largest average gap reaches 27.29% / 21.15% in F1 / BLEU-1 on CALFW; under palmprint-based personalization, the corresponding gap is 25.75% / 19.22% on MS_Blue. These results support biometrics as a practical control signal for personalized memory retrieval in shared environments.

人机协同与对齐(0 篇)

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

本轮分类概览

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

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

近一个季度监测日历

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

近 14 次监测窗口

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

本轮新增候选(16 篇)

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

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

形式化与程序验证 · 4/30 · 2026-09-01DART:DAG与区块链的多智能体信任治理面向恶意或不合作的智能体,将集中编排与链上治理结合:DAG工作流、声誉感知分配与智能合约问责。DART: A DAG-Based Reputation and Incentive Framework via Blockchain-Enabled Governance for Trustworthy LLM Multi-Agent Collaboration

Large language model (LLM)-based multi-agent systems (MAS) predominantly rely on centralized orchestration and lack formal verification mechanisms for agent reliability, participation, and system-level behavioral alignment. These shortcomings leave open environments severely vulnerable to uncooperative or malicious agents. This work proposes DART, a Directed Acyclic Graph (DAG)-based reputation and incentive regulation framework for trustworthy multi-agent collaboration, combining centralized operational orchestration with blockchain-enabled decentralized governance and accountability. DART unifies DAG workflow orchestration, capability and reputation-aware task allocation, dynamic behavior updates, multi-factor incentives, and smart contract accountability paired with IPFS storage. Under this paradigm, agent selection dynamically balances task alignment, historical reputation, and workload, while post-execution behavioral evidence continuously calibrates agent trust and the probability of future participation. Evaluated across four axes, DART achieves 93.6% Pass@1 on GSM8K and builds a full-stack application in 142 s using two agents, outperforming centralized baselines. Across five independent 150-round longitudinal trials, Full DART achieves a mean task success rate of 93.33 +/- 2.26%, output quality of 0.9357 +/- 0.0117, retry rate of 0.2307 +/- 0.0816, and allocation delay of 1.1153 +/- 0.0408 s, consistently outperforming its ablated configurations DART isolates persistent and intermittent malicious agents, obtaining a 99.3% output containment rate and restoring system success to 99.8%. These results demonstrate the potential of coupling reputation, incentives, DAG-based coordination, and verifiable blockchain-enabled governance to support adaptive and accountable multi-agent collaboration.

阅读 arXiv 原文

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

软件工程与仓库智能 · 6/30 · 2026-09-07CodeTD:注意力拓扑预检代码幻觉基于注意力图的拓扑数据分析,在代码执行前判断生成是否正确;在多个基准、5种语言与10个代码LLM上优于基线。CodeTD: Topology of Attention Detects Hallucinations in Code LLMs

As AI-code assistant tools become widespread, automatic assessment of the correctness of generated code becomes a significant challenge. Code LLMs are prone to hallucinations, which may lead to code that does not solve the required problem, or even to code with severe security vulnerabilities. In this paper, we introduce CodeTD -- the first approach to pre-execution assessment of code correctness based on topological data analysis (TDA) of Code LLMs' attention maps. Our method quantifies prompt-generation mismatch using topological patterns of attention maps. We carry out experiments with common benchmarks (HumanEval, MBPP, BigCodeBench, MultiPL-E), 5 programming languages and 10 Code LLMs of size up to 34B parameters. The experimental results show that the proposed method outperforms recent baselines. Moreover, CodeTD is transferable between coding benchmarks.

阅读 arXiv 原文
软件工程与仓库智能 · 4/30 · 2026-09-07工具增强的仓库数据问答机器人先解析用户查询提取参数并选择合适工具,再调用GPT-4生成详尽回答;不同于嵌入与检索的多组件方案。A Tool-Augmented, GPT-4 Chatbot for Real-Time Repository Data Analysis

Software repositories contain vast amounts of data on code contributions, bug reports, and project activities, yet this information remains challenging for non-technical stakeholders and developers to access due to limited expertise in querying repositories. To address this, we introduce a novel chatbot architecture leveraging OpenAI's GPT-4 model for automated extraction and analysis of repository data. In contrast, our architecture takes a structured path first by parsing the user's query to extract relevant parameters, then selecting the correct tool to employ based on that analysis, and finally invoking the GPT-4 model to create a highly detailed response. In contrast to previous work based on multi-component systems with embedding models and document retrievers, our architecture inverts the process by relying on prompt engineering and tool selection to fit with the query intent. To validate our approach, we conducted experiments on various question types, including Issues, Pull Requests, Commits, Compound Questions, and General Repository Information, evaluating our target prompts' ability to improve the accuracy of responses from the model. Beyond demonstrating the utility of this architecture to a diverse set of users, our findings suggest that this architecture can make repository data more accessible to technical and non-technical audiences through the production of actionable insights.

阅读 arXiv 原文
软件工程与仓库智能 · 3/30 · 2026-09-07开源项目AI贡献政策全景分析281份开源AI贡献政策:83.3%允许或鼓励AI,67.3%要求高人工参与,48.8%要求披露AI。"We Permit the Use of AI, but [...]": The Landscape of AI Policies in Popular Open Source Projects

Open source communities are converging on a new governance artifact: the AI contribution policy. These policies barely existed a few months ago and are now being written and adopted. We analyzed 281 AI contribution policies, and manually classified them along the six dimensions; to study how policies change, we also tracked 92 dedicated AI policy files over time. We answer four research questions on (1) AI usage allowance, (2) AI disclosure practices, (3) AI slop countermeasures, and (4) AI policy evolution. We find that, first, permission is the norm rather than the exception: 83.3% of policies permit or encourage AI in code contributions. But permission comes with conditions, as 67.3% require a high level of human involvement and 43.4% assign accountability. Second, AI disclosure is required by 48.8% of policies, most often in pull request descriptions and commit messages, but what must be disclosed varies widely. Third, we identify ten countermeasures against AI slop, targeting pull requests, users, and autonomous agents. Finally, policies are not static: half of the dedicated AI policy files have already been revised since creation. Our results give maintainers and researchers a baseline and a labeled corpus for studying the impact of AI policies.

阅读 arXiv 原文
软件工程与仓库智能 · 6/30 · 2026-09-07遗留系统现代化中的需求工程局限在跨国能源企业开展行动研究,结论是仅靠以利益相关者为中心的需求工程不足以支撑现状与目标系统的差距分析。When Stakeholder-centric Requirements Engineering is Not Enough: An Action Research Study on Legacy System Modernisation

Legacy system modernisation is a major challenge in digital transformation, especially when organisations depend on long-lived, business-critical systems that are only partly understood. In such context, organisations must define future needs while determining what current systems actually do and which functions to retain, adapt, or replace. Modernisation is therefore not only a technical challenge but also a requirements engineering (RE) problem, shaped by stakeholder perspectives. This study examines how far stakeholder-centric RE can support gap analysis between the system-as-is and the system-to-be in a legacy modernisation context. We conducted an action research study in a multinational energy company engaged in system modernisation. In the study, we applied stakeholder-centric RE practices, including stakeholder identification, semi-structured elicitation interviews, agreement-building through the Delphi method, and prioritisation with the MoSCoW method. The results show that this process was effective in producing requirements stakeholders generally viewed as understandable and correct, but less effective in achieving agreement on how elicited requirements mapped to legacy system functionality. The findings suggest that stakeholder-centric RE is necessary but not sufficient, pointing to the need for uncertainty-aware, iterative, and evidence-based modernisation practices that combine stakeholder perspectives with manual and tool-assisted analysis of legacy systems.

阅读 arXiv 原文
软件工程与仓库智能 · 4/30 · 2026-09-05句嵌入检测AI代码评审习惯化对11,429次评审的分析显示,批准率随时间上升而词法特征无单调下降;作者改用句嵌入检测评审习惯化。Beyond Lexical Metrics: Sentence-Embedding Detection of Reviewer Habituation in AI Code Review

Code review is a key quality checkpoint between AI-generated code and production. As AI coding agents submit pull requests at scale, it is unclear whether reviewers reduce scrutiny with repeated exposure and whether review comments reveal this change. We study 11,429 reviews from 400 repeat reviewers over 207 days, paired with 10,104 human-authored inline comments from AIDev. Approval rates rise from 30.5% in reviewers' early periods to 36.6% in late periods (Wilcoxon p = 8.6 x 10^-8; Cohen's d = 0.25). However, four hand-crafted linguistic features - lexical diversity, Shannon entropy, technical specificity, and constructive actionability - show no monotonic decline across exposure deciles (all Spearman absolute rho <= 0.53, p >= 0.11; Bonferroni-corrected Mann-Whitney p >= 0.36). A logistic-regression classifier based on these features reaches F1 = 0.485, below the majority-class baseline. Sentence-embedding structure does carry signal: reviewers' late-period comment centroids shift farther from their early-period centroids than under within-reviewer random permutations (Wilcoxon p < 0.001), and a small MLP using three embedding statistics reaches F1 = 0.74 under 5-fold reviewer-stratified cross-validation. Granger analysis shows that approval-rate changes predict later shifts in technical specificity at all tested lags (p < 0.001), while the reverse direction is significant at only one of four lags. Reviewer adaptation is therefore detectable in latent distributional structure rather than in classical lexical metrics, and language shifts follow rather than precede changes in approval behavior.

阅读 arXiv 原文
软件工程与仓库智能 · 6/30 · 2026-09-04遗憾主导的智能体安全需求机制提出MS-RGR:以惊讶检测新异、以遗憾评估风险,决定自主运行、反思或上报人类;仿真中静默失败近零。Regret Dominates Surprise: Design-Time Requirements Engineering for Agentic-AI Safety

Requirements engineers for agentic-AI domains face challenges in evaluating, specifying, and operationalizing safe autonomy. Mainstream frameworks, such as Goal-Oriented Requirements Engineering (GORE), lack mechanisms to systematically address these challenges under epistemic uncertainty. We contribute an approach that builds on GORE to model and simulate safe autonomy in agentic-AI systems. We introduce a novel Regret-Dominance Mechanism (MS-RGR) to operationalize safe autonomy. MS-RGR uses two signals: epistemic surprise (novelty detection) and cognitive regret (evaluative risk) to address the trilemma problem: should the agent operate in routine autonomy, undergo reflective reasoning, or escalate to human? We instantiate MS-RGR in elderly care monitoring and autonomous driving. A 100-seed stochastic simulation shows MS-RGR reduces silent failures to near-zero and detects risk approximately 17.5 times faster than a sensor-only baseline, remaining formally traceable via LTL safety properties. A retrospective proxy instantiation applying the DRI gate post-hoc over execution traces from 208 AGENTHARM scenarios across seven LLMs shows the gate improves harmful-task refusal only for models with strong baseline safety (over 80% pre-gate refusal, e.g., 84.1% to 90.9%), indicating MS-RGR amplifies rather than substitutes for model-level safety training. We discuss threats to validity, positioning MS-RGR as initial feasibility evidence for design-time safety constraints in agentic-AI requirements engineering.

阅读 arXiv 原文
软件工程与仓库智能 · 4/30 · 2026-09-04需求工程成为GenAI时代重心综述AI for RE、提示编程与通用SE智能体,认为实现变便宜后工程重心转向表达、筛选、验证与评估需求。The Impact of GenAI on the Future of Requirements Engineering

Recent advances in artificial intelligence (AI), particularly large language models (LLMs), are transforming how we design and build systems by increasing access to domain knowledge and by providing automation support to software engineering (SE). As implementation becomes less expensive through generalist SE agents, engineering effort shifts away from writing correct code and toward expressing, curating, verifying, and evaluating requirements. In this paper, we survey the state of the art in AI for requirements engineering (RE) research leading up to the transformation, before reviewing advances in LLMs. We survey two subsequent research areas: prompt programming, which treats LLM instructions as a program in SE vernacular, and generalist SE agents, which combine multiple LLM advances to yield semi-autonomous processes that complete SE tasks. Finally, we explore the future of requirements engineering along two axes: matters changing how we interact with requirements through the SE process, and matters changing how requirements are experienced by software developers and stakeholders more broadly, including end-users. This article aims to inform how RE researchers can navigate this transformation in the selection of future research priorities.

阅读 arXiv 原文

代码质量与优化(1 篇)

代码质量与优化 · 3/30 · 2026-09-05整文件生成优于迭代diff编辑在Flutter/Dart代码数据集上,整文件直接生成全面优于迭代diff编辑式生成。Diffs vs. Whole Files: An Empirical Comparison of Iterative Edit-Based and Direct Generation for Flutter/Dart Code Models

Large language models used for code editing can be trained and deployed in at least two output regimes: direct generation, where the model emits the entire modified file in one shot, and iterative diff-based generation ("steps"), where the model emits a sequence of localized search/replace edits applied one at a time until it signals completion or a step budget is exhausted. The diff-based regime is attractive because it mirrors how developers edit code and should require far fewer generated tokens per turn. We train two code models - a 100M-parameter model trained from scratch (Rainbow-Pony-100M) and a fine-tuned Qwen2.5-Coder-0.5B - in both regimes on a shared Flutter/Dart dataset, and evaluate all four resulting models on a held-out set of approx 1,790 tasks per model. Direct generation substantially outperforms diff-based generation on every metric we measure - compilation/static-analysis pass rate, bits-per-byte, character-level similarity to the reference, and blinded LLM-judge ratings of goal fulfillment, correctness, and code quality - and the gap persists after controlling for task difficulty via a matched-ID comparison and when restricting to code that compiles on both sides. We then identify a single, architecture-independent mechanism behind the conditions where diff-based generation does win: it is competitive on short, spatially localized edits, and its category-level wins concentrate in exactly the two task categories - refactoring and error-handling/edge-case fixes - with the lowest mean edit-step count in our dataset. We term this task locality and discuss its implications for when an edit-based training regime is and is not the right choice for a code-editing model.

阅读 arXiv 原文

UI 与 GUI Agent(0 篇)

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

个人知识与本体(7 篇)

个人知识与本体 · 4/30 · 2026-09-08生物特征匹配的智能体记忆个性化提出Bio-Memory,检索时先用生物特征匹配筛选候选,再做语义排序,以区分记忆所有人与非所有人。Personalizing LLM Agent Memory Using Biometrics

Personalized memory helps LLM agents deliver stable, tailored assistance by storing and reusing user-specific data across interactions. In multi-user scenarios, however, retrieval must consider not only semantic similarity but also whether the current requester matches the identity associated with the stored memory. We propose Bio-Memory, a biometric-aware memory architecture that conditions memory retrieval on both semantic similarity and biometric matching. Built on top of A-Mem, Bio-Memory augments each atomic memory note with a biometric embedding and uses biometric matching to form the retrieval candidate pool before semantic ranking. We evaluate Bio-Memory on LoCoMo in a 10-user shared-agent setting over 7 face benchmarks and 10 palmprint protocols. Across datasets, Bio-Memory consistently separates owner and non-owner queries. Under face-based personalization, the largest average gap reaches 27.29% / 21.15% in F1 / BLEU-1 on CALFW; under palmprint-based personalization, the corresponding gap is 25.75% / 19.22% on MS_Blue. These results support biometrics as a practical control signal for personalized memory retrieval in shared environments.

阅读 arXiv 原文
个人知识与本体 · 3/30 · 2026-09-08智能体记忆逐出的反事实审计提出恢复反事实干预,将错误分为可恢复、不可逆与残余三类,以区分逐出损失与可恢复的检索失败。What Eviction Destroys: A Restore-Counterfactual Audit of Forgetting in Agent Memory

Agent memory systems must discard stored information when their history exceeds a fixed token budget. Existing budget-accuracy frontiers quantify the resulting loss in accuracy, but do not distinguish irreversible losses caused by eviction from recoverable retrieval failures. We introduce the restore counterfactual, a per-question paired intervention that reinstates the question's gold evidence in the read-time context and reruns the same reader. Combining the change in correctness with whether the evidence was retained after eviction classifies each oracle-answerable error as recoverable, irreversible, or residual; in the residual case, the answer remains incorrect after restoration. We evaluate FIFO, random, redundancy-aware, and LLM-importance eviction on LongMemEval-S at three budgets and under two retrieval regimes, using GPT-4o-mini as the primary reader and judge and GPT-5.4-mini as a robustness reader. Under top-k retrieval at an 80k-token budget, the irreversible share among errors corrected by restoration is 0.67-0.73 for FIFO, random, and redundancy-aware eviction, compared with 0.60 for LLM-importance. At 8k tokens, it reaches 1.00 for all four policies. Recoverable errors occur under top-k retrieval at 80k tokens but are absent under forced-gold injection by construction, so budget-accuracy results are not directly comparable unless the retrieval regime is reported. An exploratory matched-accuracy analysis detects no difference in irreversible rate among accuracy-matched policy pairs at a resolution of 1.2-6 percentage points. The same analysis detects the deliberately destructive control. To our knowledge, this is the first per-item, per-question restore-counterfactual audit of eviction for external agent-memory stores on a standard conversational benchmark.

阅读 arXiv 原文
个人知识与本体 · 3/30 · 2026-09-08MemForest事件树渐进合并记忆记忆压缩框架:切分事件单元并建最大生成树,渐进合并冗余节点;锚点引导从关键节点邻域检索。MemForest: Efficient Agent Memory Management via EventTree Partitioning and Progressive Merging

Agent memory systems have demonstrated significant potential in long-term dialogue, personalized assistants, and video understanding. However, continuously accumulated memory introduces substantial storage and retrieval costs during inference. To address this issue, we propose \textbf{MemForest}, a general memory compression framework adaptable to various agent memory systems. Specifically, MemForest partitions historical memory into event-centric units by leveraging global semantic similarity and local temporal continuity. For each unit, it constructs a maximum spanning tree, termed an EventTree, and progressively merges redundant memory nodes by selecting high-weight edges, reducing storage overhead. Furthermore, we introduce an anchor-guided propagation retrieval mechanism that retrieves relevant memory nodes from the temporal neighborhoods of key nodes, improving retrieval accuracy. Extensive experiments demonstrate the effectiveness of MemForest. Under the unimodal Mem0 framework, MemForest retains \textbf{97.1%} of the original performance while compressing \textbf{50%} of historical memory across three benchmarks (LoCoMo, LongMemEval, and PersonaMem), achieving a \textbf{1.89x} retrieval speedup. Under the multimodal M3-Agent framework, it preserves \textbf{99.7%} of the original performance with a \textbf{50%} compression ratio across two benchmarks (M3-Bench-robot and M3-Bench-web), achieving a \textbf{2.24x} retrieval speedup. \textcolor{RoyalBlue}{\textit{Our code is available at [https://github.com/Celina-love-sweet/MemForest.}}](https://github.com/Celina-love-sweet/MemForest.}})

阅读 arXiv 原文
个人知识与本体 · 0/30 · 2026-09-08撤销事实在记忆检索中仍占优实测五个记忆系统都未默认执行撤销:被撤销事实仍被返回并可导向不安全行动;作者增设守卫拦截这类记录。Revoked but Still Authoritative: An Empirical Study of Revocation Enforcement in Agent-Memory Systems

Long-running language-model agents depend on persistent memory. Many agent-memory systems preserve history through soft revocation: a contradicted fact is marked invalid and retained rather than deleted. However, whether that mark is enforced at retrieval time is unexamined. In this paper, we measure five such systems: we load each with a revoked policy and its replacement, track whether the revoked fact is returned at retrieval and whether the agent then acts on it across nine policy scenarios and nine models, and score every trial under six defense conditions. We find that no system enforces revocation by default: the revoked fact is returned wherever the revocation label is visible to the retrieval layer, outranks its replacement, and leads agents to the unsafe action. Based on these findings, we develop a guard that sits between the agent and any memory backend and withholds records that are revoked or conflict with their replacement.

阅读 arXiv 原文
个人知识与本体 · 3/30 · 2026-09-07长程智能体的多模态证据记忆摘要仅讨论文本与视觉记忆读取的权衡,尚未展开具体方案与实验,证据有限。MEMO: Multimodal Evidence Memory Organization for Long-Horizon LLM Agents

Long-running LLM agents rely on external memory to store and reuse information beyond a single context window, yet there is a fundamental tension between the continuous accumulation of interaction trajectories and the limited context capacity. The key challenge in agent memory is therefore not only to retrieve relevant records, but also to select necessary evidence under a given budget and organize it in an appropriate modality. Existing memory readout methods mainly use textual or visual forms. Text preserves high fidelity, but its linear token representation makes contents with different importance compete for the limited context at nearly uniform unit cost. Visual readout renders text into document-like images, which can use two-dimensional layouts to expose structure and emphasize key information, but it may lose fine-grained details during rendering and compression. To address this issue, we propose MEMO, a multimodal evidence memory organization method for LLM agents. MEMO first uses a trained evidence extractor to select relevant memory blocks and form evidence units with source information and presentation requirements. A trained query-conditioned memory manager assigns each unit to a textual, visual, or dual-channel carrier and selects a layout that matches the evidence structure. A deterministic memory construction module then generates the textual package and visual pages. The memory manager is trained with feedback from an offline reader that measures the utility of the guided memory plan, so that retention and presentation decisions align with downstream usage. We evaluate MEMO on four benchmarks, HotpotQA, 2WikiMultiHopQA, LoCoMo, and ALFWorld, with multiple reader backends. The results show that MEMO presents memory more efficiently with fewer memory tokens, improves downstream task performance, and builds more effective working memory under constrained budgets.

阅读 arXiv 原文
个人知识与本体 · 6/30 · 2026-09-07流式稳定不等于有长期记忆提出稳定、访问、效用三视界与评估契约ThreeH,构造性证明稳定视界可无限而访问与效用视界有限。Separating Stream Stability from Long-Term Recall in Language Models

Methods for streaming language models are often discussed alongside long-context and memory systems, although they solve different problems. An attention sink can stabilize autoregressive generation over an indefinitely long stream while the model remains unable to use content that has left its recent-token cache. We argue that this distinction should be explicit in system claims and evaluation. We introduce three horizons: the stability horizon, over which predictive behavior remains well behaved; the access horizon, over which past content can still causally affect the output; and the utility horizon, over which a task retains acceptable performance. We show constructively that the stability horizon can be infinite while the access and utility horizons are finite. We then propose ThreeH, an evaluation contract that measures all three horizons under a common state and compute budget. Applying the framework to attention-sink streaming clarifies its strength, constant-memory, stable generation, without treating anchor tokens as semantic memory. The framework exposes roles for cache policies, recurrent state, retrieval, and external memory. Experiments on 128K-token streams, delayed binding recall, and delayed decisions show that attention sinks preserve local modeling but not content beyond the active cache; recurrent and retrieval state extend the semantic horizon.

阅读 arXiv 原文
个人知识与本体 · 3/30 · 2026-09-03EdgeMem多锚点超图免LLM记忆保留原始交互轮次为证据,用轻量局部处理构建多锚点超图;检索直取源证据,把LLM留给最终答案生成。EdgeMem: LLM-Free Agent Memory Construction and Retrieval via Evidence-Preserving Multi-Anchor Hypergraph

Agent memory allows LLM agents to use earlier interactions when answering new queries. Existing methods often compress interaction histories into summaries or other LLM-generated representations. Repeated generation adds cost and can discard answer-bearing details before the system knows what a future query will require. We propose EdgeMem, an agent-memory method built around a simple principle: preserve original interaction turns and organize them through complementary content, temporal, and episodic cues. EdgeMem realizes this principle with a multi-anchor hypergraph constructed by lightweight local processing. Retrieval directly returns source evidence and reserves LLM use for final answer generation, combining structured access to multi-session histories with faithful retention of the original conversation. Experiments on LoCoMo and LongMemEval-S show strong retrieval and memory-grounded question answering; on LoCoMo, EdgeMem achieves the highest strict-judge score among seven reproduced systems under a shared prompt (61.01 versus 58.70), while construction and retrieval require no generative-LLM calls. Overall, EdgeMem shows that preserving and organizing source evidence provides an effective and efficient foundation for agent memory without generative memory management.

阅读 arXiv 原文

人机协同与对齐(0 篇)

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