为运行时自治智能体设计五项核心管控机制,解决企业部署中的突发性、不可预测和开放接入问题。
Five Primitives for Governing Autonomous AI Agents at Runtime
- 提出发现、身份、治理、验证和供应链五项运行时管控原语
- 实测四项已部署于私有试点,第五项作为独立工具暂未集成
- 通过策略校验与可验证日志链保障安全,适合高风险自主系统场景
企业部署的自治智能体沿用针对人类用户和长期服务的控制模型,但存在三方面不匹配:代理主体瞬时出现与消失,快于资源分配;其行为由模型选择而非编程决定,可能操作范围未知;且代理群体为动态发现而非预置,任何调用API者均可创建。我们主张此类治理是运行时问题,非模型对齐或构建时问题,并推导出五个必要原语:发现、身份、治理、验证和供应链。每项缺失将导致特定失效,且其他原语无法结构上替代。实现中,每个动作在执行前经策略审查,依据租户级动作词汇授权,并记录于第三方可验证的哈希链接签名账本。架构代价包括:强制点位于请求关键路径、每个工作负载需侧车身份组件、故障闭锁机制将可用性故障转为拒绝服务。当前四项已建成并运行于私有试点,第五项作为独立工具开发,尚未集成至请求路径。作者明确指出,这一五部分分解并非通用分类,而是对其实际代码实现的描述。
原文摘要 · Abstract (English)
Enterprise deployments of autonomous AI agents inherit a control model built for human users and long-lived services, and the fit fails in three specific ways: agent principals are ephemeral, appearing and vanishing faster than provisioning; their actions are selected by a model rather than programmed, so the set of things they may attempt is not known in advance; and the population is discovered rather than provisioned, because anyone who can call an API can create one. We argue that governing such agents is a runtime problem -- not a model-alignment problem and not a build-time problem -- and we derive five primitives from the questions that must be answered before an action takes effect and after it has: discovery, identity, governance, attestation, and supply chain. For each we state what fails if it is absent and why the others cannot structurally supply it. We describe an implementation in which an agent's action is mediated against policy before it takes effect, authorised against a per-tenant action vocabulary, and recorded in a hash-linked signed ledger a third party can verify with the vendor out of the loop. We report what the architecture costs: the enforcement point sits on the request's critical path, identity requires a sidecar per workload, and fail-closed mediation converts availability incidents into denial. We are explicit about implementation status: four primitives are built and running in private pilots, and the fifth is built as separate tooling and not yet integrated into the request path. We keep it in the set deliberately: a five-part decomposition that exactly matches what its authors happened to build is not a taxonomy but a description of a codebase.
Thank you to arXiv for use of its open access interoperability. PaperDance 不是 arXiv 官方产品;中文卡片由大模型生成,请以原文为准。