提出AOS架构,让智能体系统可管理、可追溯、跨平台协同。
The Agent Operating System (AOS): A Reference Operating Architecture for Distributed Agentic Systems
- 分控管与运行两层,统一治理智能体意图与行为
- 明确接口规范,支持异构组件组合部署
- 适合构建可信、可观测的分布式智能体系统
大语言模型已将人工智能从孤立的预测服务,转变为能推理、调用工具、检索外部状态、委派任务并代表用户和组织行动的长期运行、分布式系统。现有生态涌现了代理框架、工作流引擎、模型服务化平台、记忆系统、通信协议和可观测性工具,虽提升了执行效率,但缺乏一个稳定、与实现无关的运营架构来管理意图、选择能力、维持授权、控制不确定性、协调运行行为,并重构关键操作的原因。本文提出代理操作系统(AOS),一种面向分布式代理系统的厂商中立参考操作系统架构。AOS包含两个内部平面:控制与治理平面,负责意图、策略、信任、授权、置信度、审计性、可观测性和人工监督;运行与协调平面,负责代理生命周期、工作流协调、模型与工具路由、上下文与记忆协调、调度、流量管理及运行时保障。平台服务、操作系统、容器运行时和物理基础设施均在AOS边界之外,通过明确定义接口集成。本文阐明了AOS的概念、不变性、接口对象、优化目标、部署模式和可靠性责任,并识别出权衡与未解研究问题。AOS并非取代现有框架或基础设施,而是作为异构组件组合为可管理、可靠、可观测、可互操作的代理系统的操作系统架构。
原文摘要 · Abstract (English)
Large language models have transformed artificial intelligence from isolated prediction services into components of long-running, distributed systems that reason, invoke tools, retrieve external state, delegate tasks, and act on behalf of users and organizations. The surrounding ecosystem has responded with agent frameworks, workflow engines, model-serving platforms, memory systems, communication protocols, and observability tools. These technologies improve execution, but they do not provide a stable, implementation-independent operating architecture for governing intent, selecting capabilities, preserving authority across delegation, controlling uncertainty, coordinating runtime behavior, and reconstructing why consequential actions occurred. This paper proposes the Agent Operating System (AOS), a vendor-neutral reference operating architecture for distributed agentic systems. AOS contains two internal planes: a Control & Governance Plane responsible for intent, policy, trust, authority, confidence, auditability, observability, and human oversight; and a Runtime & Coordination Plane responsible for agent lifecycle, workflow coordination, model and tool routing, context and memory coordination, scheduling, traffic management, and runtime assurance. Platform services, Linux or Windows, container runtimes, and physical infrastructure remain outside the AOS boundary and are integrated through explicit interfaces. The paper specifies AOS concepts, invariants, interface objects, optimization objectives, deployment profiles, and reliability responsibilities. It also identifies tradeoffs and unresolved research questions. AOS is not presented as a replacement for existing frameworks or infrastructure; it is proposed as the operating architecture through which heterogeneous components can be composed into governable, reliable, observable, and interoperable agentic systems.
Thank you to arXiv for use of its open access interoperability. PaperDance 不是 arXiv 官方产品;中文卡片由大模型生成,请以原文为准。