Auto-sync
This commit is contained in:
33
wiki/concepts/Multi-Agent-Hierarchy.md
Normal file
33
wiki/concepts/Multi-Agent-Hierarchy.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
title: "Multi-Agent Hierarchy"
|
||||
type: concept
|
||||
tags: [multi-agent, architecture, reliability]
|
||||
last_updated: 2026-04-15
|
||||
---
|
||||
|
||||
## Definition
|
||||
一种多智能体架构模式,模拟人类组织的层级结构:Supervisor(主管)制定计划、分解任务、分配给 Worker(工作节点)执行,Validator(验证器)检查结果。
|
||||
|
||||
## Components
|
||||
- **Planner(规划器)**:智能模型(如 Opus)将用户目标分解为原子步骤
|
||||
- **Worker(工作节点)**:专用 Agent,每节点只做一件事,可使用更小更快的模型
|
||||
- **Validator(验证器)**:检查点,使用确定性代码(单元测试、JSON Schema)或 LLM 进行验证
|
||||
|
||||
## Execution Flow
|
||||
```
|
||||
Planner → Worker → Validator
|
||||
↑__________________|
|
||||
(验证失败则打回重做)
|
||||
```
|
||||
|
||||
## Why It Works
|
||||
依赖图(Dependency Graph)强制各节点协作:Worker 在 Planner 喂任务前无法开始,且 Validator 会捕获作弊。
|
||||
|
||||
## Trade-offs
|
||||
- **优点**:上下文分离,适合复杂工作流
|
||||
- **缺点**:顺序执行,速度慢,成本高
|
||||
|
||||
## Related Concepts
|
||||
- [[Multi-Agent-Consensus]]:另一种多 Agent 可靠性模式
|
||||
- [[Multi-Agent-Adversarial-Debate]]:对抗式架构
|
||||
- [[Multi-Agent-Knock-out]]:淘汰制架构
|
||||
Reference in New Issue
Block a user