用测试驱动的主动机制替代被动修复,提升AI系统长期泛化能力
Position: Stop Reactively Patching Your Model Every Time and Start Proactive Test-Driven AI Development

- 构建测试空间,将用户反馈映射到任务目标,实现主动预判
- 数学证明主动飞轮迭代次数更少,长期扩展性更好
- 适合关注AI系统可持续维护与泛化能力的研究者
许多现代AI系统需在多样、开放的应用场景中运行。当前主流的维护流程依赖反应式AI飞轮,通过用户行为反馈(错误)来修补模型。然而,这种机制常忽略错误背后的系统目标背景,无法提前识别潜在边缘情况,导致频繁迭代。同时,由于开放世界用例的长尾特性,剩余错误越来越难收集。本文主张采用主动测试驱动飞轮,以克服反应式飞轮的局限。我们提出构建“测试空间”,将反馈数据技术性映射至任务目标,推动飞轮从被动响应转向主动预防。并通过数学证明,主动飞轮在长期扩展中迭代次数更少,性能更优。
原文摘要 · Abstract (English)
Many modern AI systems are designed to operate under diverse, open-ended, use-cases. To help generalize deployed systems, many deployed-system maintenance pipelines use a reactive AI flywheel that observes emerging feedback from user behavior (errors) and patches the model accordingly. However, when used as the primary maintenance mechanism, these flywheels often ignore the broader context of these errors within the system's objectives, failing to preempt potential future edge cases, which leads to more unnecessary flywheel iterations. Also, it is statistically increasingly difficult to collect remaining errors due to the long-tail nature of open-world use-cases. This position paper argues that a proactive test-driven flywheel is required to address reactive flywheel's limitations and to approach a generalizable system. We advocate for creating a "test space" to technically map feedback data to task objectives, evolving the flywheel from reactive to proactive. We augment our position by mathematically proving a proactive one achieves better long-term scaling with fewer iterations than the reactive flywheel.
Thank you to arXiv for use of its open access interoperability. PaperDance 不是 arXiv 官方产品;中文卡片由大模型生成,请以原文为准。