用Kubernetes式架构管理企业AI知识,确保安全可控的智能体协作。
Context Kubernetes: Declarative Orchestration of Enterprise Knowledge for Agentic AI Systems
- 基于YAML声明式配置,实现知识资源的自动化编排与权限管控。
- 三重权限模型可防御全部五种攻击,比传统RBAC多拦截邮件泄密漏洞。
- 适用于需要高安全性的企业级AI系统设计者与架构师。
我们提出Context Kubernetes,一种面向企业级智能体AI系统的知识编排架构,包含原型实现与八项实验。核心观点是:在组织范围内,将正确的知识以恰当权限和时效性交付给合适的智能体,其结构上类似于十年前Kubernetes解决的容器编排问题。该架构形式化了六项核心抽象,包括基于YAML的声明式知识架构代码、一个协调循环,以及三层智能体权限模型——智能体权限始终严格低于人类权限。在合成种子数据上,对比四种治理基线:无治理的RAG、ACL过滤检索、RBAC感知路由,及完整架构。各层贡献不同能力:ACL过滤消除跨域泄露,意图路由降低噪声19个百分点,仅三层模型可完全阻止五种测试攻击场景——其中一种攻击(智能体通过邮件发送机密定价)是RBAC无法识别的普通邮件行为。使用TLA+模型检验,在460万可达状态中验证零违规。对微软、Salesforce、AWS、谷歌四大平台的调研显示,均未在架构层面隔离智能体审批通道。我们识别出四项使上下文编排比容器编排更复杂的特性,并论证这使解决方案更具价值。
原文摘要 · Abstract (English)
We introduce Context Kubernetes, an architecture for orchestrating enterprise knowledge in agentic AI systems, with a prototype implementation and eight experiments. The core observation is that delivering the right knowledge, to the right agent, with the right permissions, at the right freshness -- across an entire organization -- is structurally analogous to the container orchestration problem Kubernetes solved a decade ago. We formalize six core abstractions, a YAML-based declarative manifest for knowledge-architecture-as-code, a reconciliation loop, and a three-tier agent permission model where agent authority is always a strict subset of human authority. On synthetic seed data, we compare four governance baselines of increasing strength: ungoverned RAG, ACL-filtered retrieval, RBAC-aware routing, and the full architecture. Each layer contributes a different capability: ACL filtering eliminates cross-domain leaks, intent routing reduces noise by 19 percentage points, and only the three-tier model blocks all five tested attack scenarios -- the one attack RBAC misses is an agent sending confidential pricing via email, which RBAC cannot distinguish from ordinary email. TLA+ model-checking verifies safety properties across 4.6 million reachable states with zero violations. A survey of four major platforms (Microsoft, Salesforce, AWS, Google) documents that none architecturally isolates agent approval channels. We identify four properties that make context orchestration harder than container orchestration, and argue these make the solution more valuable.
Thank you to arXiv for use of its open access interoperability. PaperDance 不是 arXiv 官方产品;中文卡片由大模型生成,请以原文为准。