跳到正文
返回论文列表
cs.AI提交于 已译

重构企业级 RAG:面向多智能体系统、先组织后检索的知识层

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

Garima Agrawal · Prasun Das · Akshay Sarvade · Priyanka L · Minisha N · Sravani Joshna · et al.

中文摘要

企业正将智能体式 AI 部署到软件开发生命周期,所需的是系统实际运行的行为逻辑,而非面向干系人的文档。一套七智能体逆向工程流程处理了 18 个服务中的 241 个代码库,生成数千项描述范围、用户旅程、规则和验收标准的制品;但仅恢复逻辑并不等于可用。offer、eligibility、activation 等实体在各服务间共享词汇,名称相近但运行语义不同,一条端到端旅程可能牵涉上千条相似规则,不能混为一谈。扁平向量检索会高相似度返回错误服务的同一规则,且没有错误信号。知识层将被机器生成的制品按生产者、组件、服务、领域和类型组织,再通过自描述目录、稀疏元数据注册表及制品级导航超图检索。查询先解析为制品标识以约束向量搜索,使其他服务的竞争规则从结果中结构性缺席,而非仅降低排名。该层在一周内建成,并可通过约定接入新服务;其支持根因分析及 100+ 个生产缺陷的解决,经开发者验证,还把 35 个发布回归失败归因到具体规则和服务。

关键要点

  1. 01七智能体逆向工程流程处理 18 个服务、241 个代码库,生成数千项行为制品。
  2. 02跨服务同名实体在运行语义上不同,扁平向量检索易返回错误服务的相似规则。
  3. 03知识层置于制品级,保留生产者、组件、服务、领域、类型等来源元数据。
  4. 04查询先解析为制品标识并约束向量搜索,使竞争规则结构性缺席而非依赖降权。
  5. 05知识层在一周内建成,支持解决 100+ 个生产缺陷,并定位 35 个发布回归失败。

解读

尚无解读。

原始英文摘要

arXiv:2610.32851v1 Announce Type: new Abstract: 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.

同方向论文 · cs.AI

查看全部 →

反向发现 · 这篇论文相关的工具与提示词

去交叉发现 →

关联提示词 · 6

研究github.com/f/awesome-chatgpt-prompts·外部收录·

Paper to Practice

You turn research papers into practical takeaways for the user. - Topics are set by the user (edit this list): e.g. retrieval, agents, evaluation. - Each run, find new papers on arXiv and well-known lab blogs. Pick at most 5 that are likel…

智能体github.com/f/awesome-chatgpt-prompts·外部收录·

hermes agent desktop default system prompt

You are Hermes Agent, an intelligent AI assistant created by Nous Research. You are helpful, knowledgeable, and direct. You assist users with a wide range of tasks including answering questions, writing and editing code, analyzing informati…

智能体github.com/f/awesome-chatgpt-prompts·外部收录·

Personal Knowledge & Narrative Tool

Build a personal knowledge and narrative tool called "Thread" — a second brain that connects notes into a living story. Core features: - Note capture: fast input with title, body, tags, date, and an optional "life chapter" label (user-defi…

智能体github.com/f/awesome-chatgpt-prompts·外部收录·

xcode-mcp (for pi agent)

--- name: xcode-mcp-for-pi-agent description: Guidelines for efficient Xcode MCP tool usage via mcporter CLI. This skill should be used to understand when to use Xcode MCP tools vs standard tools. Xcode MCP consumes many tokens - use only f…