跳到正文
返回论文列表
cs.AI提交于 已译

自主 AI 智能体在证明形式化中系统性偏离人类偏好

Autonomous AI Agents Systematically Diverge From Human Preferences in Proof Formalization

B\'alint Gyevn\'ar · Simon DeDeo

中文摘要

AI 系统带来了证明数量激增的新时代,但帮助人类理解这些证明需要重新关注 AI 智能体与人类在证明构建任务上的差异。提出“模拟协作”(simulated collaboration)方法,考察两个关键问题:(1)AI 智能体对表层语法与深层语义的相对关注程度;(2)AI 智能体对下一步操作的偏好如何、在何处偏离人类偏好。基于 Lean 中九项重要人类协作、超过 6K 次提交、4.7M 条定义的数据,发现:在证明构建过程中,AI 智能体(1)比人类更强烈地被显式标记的缺口吸引;(2)相对回避密集连接的证明中心以及复杂或意外的证明目标;(3)相对偏好意外的证明体,并倾向于将其正则化到基线。结果揭示了未来数学人机协作中的重要盲点与潜在干预方向。

关键要点

  1. 01提出“模拟协作”方法,对比 AI 智能体与人类在 Lean 证明构建中的偏好差异。
  2. 02数据涵盖九项人类协作、4.7M 条定义、超过 6K 次提交。
  3. 03AI 智能体更关注显式标记的缺口,回避密集连接中心与复杂目标。
  4. 04AI 智能体偏好意外的证明体,但倾向于将其正则化到基线。
  5. 05结果指出人机数学协作的盲点与潜在干预方向。

解读

尚无解读。

原始英文摘要

arXiv:2611.06995v1 Announce Type: new Abstract: Artificial intelligence (AI) systems have ushered in a new age of proof abundance, but helping humans understand these proofs requires new attention to the differences in how AI agents and humans pursue a proof-making task. We present "simulated collaboration", a methodology that allows us to examine two key questions: (1) the relative attention AI agents pay to surface syntax or, conversely, deeper underlying semantics, and (2) how and where AI agent preferences for what to do next diverge from human preferences. On a set of nine major human collaborations in Lean with 4.7M definitions across more than 6K commits, we find that, over the course of proof construction, AI agents (1) are far more strongly drawn than humans to explicitly marked gaps; (2) show a relative aversion to densely connected proof centers and to complex or surprising proof goals; and (3) are relatively attracted to surprising proof bodies, which they tend to regularize toward baseline. Our results highlight important blind spots and potential interventions for future human-AI collaboration in mathematics.

同方向论文 · cs.AI

查看全部 →

反向发现 · 这篇论文相关的工具与提示词

去交叉发现 →

关联工具 · 1

Reddit · r/artificial86

Google DeepMind 的 AlphaProof Code 用 4 周证明 Signal 实际编译代码安全,人工仅复核 1%

Google DeepMind 的 AlphaProof Code 在 4 周内对 Signal 的实际编译代码完成安全证明,覆盖实现而非仅协议设计。Gemini 驱动的智能体编写了超过 600 万行 Lean 证明并由 Lean 检查,人类专家只复核了智能体标记的约 1%。

推荐理由:材料呈现了从协议规范延伸到实际编译代码的验证路径,以及规范仍需人工撰写这一前提。