20260720
This commit is contained in:
48
concepts/four-paradigms-agent-engineering.md
Normal file
48
concepts/four-paradigms-agent-engineering.md
Normal file
@@ -0,0 +1,48 @@
|
||||
---
|
||||
title: "Agent 工程四范式 (Four Paradigms of Agent Engineering)"
|
||||
created: 2026-07-13
|
||||
updated: 2026-07-13
|
||||
type: concept
|
||||
tags: [agent, agent-engineering, paradigm-evolution]
|
||||
sources:
|
||||
- arxiv:2606.20683
|
||||
---
|
||||
|
||||
# Agent 工程四范式
|
||||
|
||||
## 定义
|
||||
|
||||
Agent Harness Survey (2026) 提出的 Agent 工程**演化性分析框架**,将 Agent 系统的发展组织为四个范式阶段。每阶段因前阶段的局限性而涌现,每阶段突出不同的性能杠杆。
|
||||
|
||||
## 四阶段
|
||||
|
||||
### Phase 1: [[prompt-engineering|提示工程]]
|
||||
- **瓶颈**:表达问题(how to ask)
|
||||
- **手段**:few-shot、CoT、self-consistency、ToT
|
||||
- **局限**:不解决信息问题——无法提供缺失知识、管理动态状态、维持长序列一致性
|
||||
|
||||
### Phase 2: [[context-engineering|上下文工程]]
|
||||
- **瓶颈**:信息生命周期管理
|
||||
- **手段**:RAG、记忆管理、工具定义、技能渐进披露、上下文压缩
|
||||
- **核心转变**:优化目标从"单个答案正确"变为"组装的上下文能否支撑多步任务完成"
|
||||
- **局限**:本质是前馈性——优化每步推理的输入但不提供结构性机制来检测漂移、验证中间结果、恢复错误
|
||||
|
||||
### Phase 3: [[harness-engineering|脚手架工程]]
|
||||
- **瓶颈**:执行稳定性(detect drift, maintain stable execution, recover from errors)
|
||||
- **手段**:闭环反馈执行、sandboxing、状态 checkpoint、验证循环、错误恢复、子 Agent 协调
|
||||
- **核心转变**:从"给模型展示什么"变为"如何保持整个系统在轨道上"
|
||||
- **子趋势**:[[multi-model-harness|多模型脚手架]] + [[learnable-harness|可学习脚手架]]
|
||||
|
||||
### Phase 4: [[agent-native-training|Agent 原生训练]] & [[model-harness-coevolution|协同演化]]
|
||||
- **瓶颈**:行为内化 + 全栈持续改进
|
||||
- **方向1**:Internalization — 规划/工具使用/验证通过交互环境训练进模型参数
|
||||
- **方向2**:Co-evolution — 模型、脚手架、改进策略在部署中联合更新
|
||||
|
||||
## 关键洞察
|
||||
|
||||
这四个阶段是**概念性演化透镜**而非严格时间分区——四者在实践中共存。分析目的不是引入另一种组件分类法,而是追踪**主导性能瓶颈如何在各阶段间迁移**,以及为什么脚手架设计已成为 Agent 工程的核心对象。
|
||||
|
||||
## 参考
|
||||
- [[agent-harness-survey-2026|Agent Harness Survey (2026)]]
|
||||
- [[harness-engineering|脚手架工程]]
|
||||
- [[agent-native-training|Agent 原生训练]]
|
||||
Reference in New Issue
Block a user