论文

面向多智能体系统的企业 RAG 知识层:先组织再检索

Reimagining Enterprise RAG for Multi-Agent Systems: A Knowledge Layer That Organizes Before It Retrieves

精选理由

一篇工程味很浓的 RAG 论文:7 个智能体逆向工程 241 个仓库,再靠 artifact 级元数据让检索不再靠相似度猜,做了 100+ 缺陷修复验证。

这篇论文提出一个面向多智能体系统的企业级知识层,处理了 241 个仓库、18 个服务,生成数千个带元数据的 artifact。针对扁平向量检索会把其他服务的相似规则误返回的问题,它把本体放在 artifact 层级,用自描述目录、稀疏元数据注册表和 artifact 级导航超图实现结构性消歧。该层在一周内建成,支撑了 100+ 生产缺陷的根因分析与修复,并定位了 35 次发布回归失败对应的具体规则和服务。

原文 · arXiv cs.AI

Reimagining Enterprise RAG for Multi-Agent Systems: A Knowledge Layer That Organizes Before It Retrieves

Enterprises are deploying agentic AI across the software development lifecycle, and they need the behavioral logic of the systems they act on, not stakeholder documentation. A seven-agent reverse-engineering pipeline recovered this logic, processing 241 repositories across 18 services into thousands of artifacts describing scope, journeys, rules and acceptance criteria. Recovery does not confer usability. Entities like offer, eligibility, and activation recur across services under a shared vocabulary, related in name but operationally distinct, so one end-to-end journey implicates over a thousand near-identical rules that must not be conflated. Flat vector retrieval fails, returning an identical rule from the wrong service at high similarity with no signal of error. Content-level ontology, the traditional remedy, did not exist, and relating every occurrence of recurring entities would have cost more than the engagement and not survived a release cycle. We place the ontology at the artifact level. In this machine-generated corpus, each artifact retains its producer, component, service, domain and type, provenance that disambiguates before content is read. We present a knowledge layer that organizes before retrieving: a self-describing catalog, a sparse metadata registry, and a navigation hypergraph defined over artifacts rather than extracted entities. Queries resolve to artifact identifiers that constrain vector search, so the competing rule from another service is absent rather than outranked, making disambiguation structural, not statistical. Built in under a week and admitting new services by convention, the layer serves SDLC agents, developers, quality engineers and analysts. It supported root-cause analysis and resolution of 100+ production defects with developer verification and attributed 35 release regression failures to specific rules and services.