智能体主管-工作者架构
Architecture
主管-工作者多智能体架构,其中编排器智能体接收高级目标,将其分解为子任务,委派给专业工作者智能体(研究员、写作者、QA),监控执行、处理故障并综合结果。编排器管理但不亲自执行任务。
Architecture
多智能体协调模式,其中编排器将工作分解为子任务,专业智能体从共享状态存储中拉取和推送,编排器从该共享状态组合最终答案。多智能体设置感觉连贯,而不是每个助手都有自己的不一致记忆。
Orchestrator {
n1: circle label="Complex task arrives"
n2: rectangle label="Request shared context"
n3: rectangle label="Create research subtask"
n4: rectangle label="Create action subtask"
n5: rectangle label="Receive findings and results"
n6: rectangle label="Compile final answer"
n1.handle(right) -> n2.handle(left)
n2.handle(bottom) -> SharedMemory.n7.handle(top) [label="Read state"]
n3.handle(right) -> n4.handle(left)
n3.handle(bottom) -> Researcher.n9.handle(top) [label="Research task"]
n4.handle(bottom) -> Operator.n13.handle(top) [label="Action task"]
n5.handle(right) -> n6.handle(left)
Researcher.n12.handle(top) -> n5.handle(left) [label="Finding"]
Operator.n17.handle(top) -> n5.handle(right) [label="Result"]
}
Researcher {
n9: rectangle label="Receive research task"
n10: rectangle label="Read shared memory"
n11: rectangle label="Analyze with context"
n12: rectangle label="Return finding"
n9.handle(right) -> n10.handle(left)
n10.handle(right) -> n11.handle(left)
n11.handle(right) -> n12.handle(left)
n10.handle(bottom) -> SharedMemory.n7.handle(left) [label="Read state"]
}
Operator {
n13: rectangle label="Receive action task"
n14: rectangle label="Read shared memory"
n15: rectangle label="Execute with context"
n16: rectangle label="Write result to memory"
n17: rectangle label="Return result"
n13.handle(right) -> n14.handle(left)
n14.handle(right) -> n15.handle(left)
n15.handle(right) -> n16.handle(left)
n16.handle(bottom) -> SharedMemory.n8.handle(left) [label="Write state"]
n15.handle(bottom) -> n17.handle(top)
}
SharedMemory {
n7: rectangle label="Resolve memory request"
n8: rectangle label="Update shared state"
n7.handle(right) -> n8.handle(left)
}
Architecture
主管-工作者多智能体架构,其中编排器智能体接收高级目标,将其分解为子任务,委派给专业工作者智能体(研究员、写作者、QA),监控执行、处理故障并综合结果。编排器管理但不亲自执行任务。
Architecture
编排器-工作者架构,其中编排器智能体将目标分解为子任务,分派给专业工作者,然后综合最终响应。这是最常见的"智能体编排"架构——强大,但随着工作者数量增长,编排器可能成为瓶颈。
Architecture
竞争式/生成器-评判者架构,多个生成器产生独立答案,然后评估器智能体评分并选择最佳输出。这种方法提高质量并减少单模型脆弱性。它更昂贵(多次LLM调用),但当正确性或创造力比延迟更重要时值得。