[{"data":1,"prerenderedAt":413},["ShallowReactive",2],{"insight-rag-knowledge-gap":3,"insight-related-rag-knowledge-gap":146},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":8,"description":7,"slug":9,"date":10,"duration":11,"category":12,"author":13,"tags":14,"body":18,"_type":140,"_id":141,"_source":142,"_file":143,"_stem":144,"_extension":145},"\u002Finsights\u002F04-rag-knowledge-gap","insights",false,"","RAG 在企业内的\"知识断层\"——为什么准确率上不去","rag-knowledge-gap","2026-03-22",11,"AI 工程","浩途技术团队",[15,16,17],"RAG","企业知识库","LLM",{"type":19,"children":20,"toc":133},"root",[21,29,43,47,53,65,75,78,84,104,113,116,121],{"type":22,"tag":23,"props":24,"children":26},"element","h2",{"id":25},"引子",[27],{"type":28,"value":25},"text",{"type":22,"tag":30,"props":31,"children":32},"p",{},[33,35,41],{"type":28,"value":34},"把 PDF 制度、Wiki、邮件归档全部 embedding 进 RAG 系统后，业务部门用了一周回来反馈：\n\"答案看起来对，细节都不对\"。我们复盘了 4 个项目的 RAG 准确率数据，得出的结论是\n——问题不在 embedding 模型，而在",{"type":22,"tag":36,"props":37,"children":38},"strong",{},[39],{"type":28,"value":40},"企业知识本身的断层",{"type":28,"value":42},"。",{"type":22,"tag":44,"props":45,"children":46},"hr",{},[],{"type":22,"tag":23,"props":48,"children":50},{"id":49},"断层-1切片粒度不匹配业务粒度",[51],{"type":28,"value":52},"断层 1：切片粒度不匹配业务粒度",{"type":22,"tag":30,"props":54,"children":55},{},[56,58,63],{"type":28,"value":57},"文档切片用 token 长度分块，业务问题却以\"任务\"为单位。一个\"如何提报年终预算\"\n跨 3 份文档：制度、流程图、表格模板。RAG 召回的 3 个 chunk 来自 3 份文档，但\n",{"type":22,"tag":36,"props":59,"children":60},{},[61],{"type":28,"value":62},"chunk 之间没有上下文链接",{"type":28,"value":64},"——LLM 无法重组成完整答案。",{"type":22,"tag":30,"props":66,"children":67},{},[68,73],{"type":22,"tag":36,"props":69,"children":70},{},[71],{"type":28,"value":72},"做法",{"type":28,"value":74},"：按业务任务建知识图谱，chunk 之上加\"任务-文档\"映射。",{"type":22,"tag":44,"props":76,"children":77},{},[],{"type":22,"tag":23,"props":79,"children":81},{"id":80},"断层-234占位",[82],{"type":28,"value":83},"断层 2、3、4（占位）",{"type":22,"tag":85,"props":86,"children":87},"ul",{},[88,94,99],{"type":22,"tag":89,"props":90,"children":91},"li",{},[92],{"type":28,"value":93},"部门术语演化：同一个词在 IT 和业务部分别意指不同",{"type":22,"tag":89,"props":95,"children":96},{},[97],{"type":28,"value":98},"时间维度断层：旧规章和新规章并存，RAG 不知道哪个生效",{"type":22,"tag":89,"props":100,"children":101},{},[102],{"type":28,"value":103},"隐性知识缺失：流程之外的\"惯例\"从来没写进文档",{"type":22,"tag":105,"props":106,"children":107},"blockquote",{},[108],{"type":22,"tag":30,"props":109,"children":110},{},[111],{"type":28,"value":112},"（详细案例与方法论由后续内容运营展开）",{"type":22,"tag":44,"props":114,"children":115},{},[],{"type":22,"tag":23,"props":117,"children":119},{"id":118},"写在最后",[120],{"type":28,"value":118},{"type":22,"tag":30,"props":122,"children":123},{},[124,126,131],{"type":28,"value":125},"RAG 不是把文档塞进向量库就行。",{"type":22,"tag":36,"props":127,"children":128},{},[129],{"type":28,"value":130},"先治理知识，再做 RAG",{"type":28,"value":132},"——这才是企业落地 LLM 的正确顺序。",{"title":7,"searchDepth":134,"depth":134,"links":135},2,[136,137,138,139],{"id":25,"depth":134,"text":25},{"id":49,"depth":134,"text":52},{"id":80,"depth":134,"text":83},{"id":118,"depth":134,"text":118},"markdown","content:insights:04-rag-knowledge-gap.md","content","insights\u002F04-rag-knowledge-gap.md","insights\u002F04-rag-knowledge-gap","md",[147,288],{"_path":148,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":149,"description":7,"slug":150,"date":151,"duration":152,"category":12,"author":13,"cover":153,"tags":154,"featured":157,"body":158,"_type":140,"_id":285,"_source":142,"_file":286,"_stem":287,"_extension":145},"\u002Finsights\u002F01-agent-pitfalls","把 Agent 接进真实业务系统时，我们踩过的 7 个坑","agent-7-pitfalls","2026-04-18",14,"\u002Fimages\u002Finsights\u002Fagent-pitfalls-cover.png",[155,17,15,156],"Agent","业务系统",true,{"type":19,"children":159,"toc":278},[160,164,169,172,178,186,191,208,211,217,222,225,231,259,262,266],{"type":22,"tag":23,"props":161,"children":162},{"id":25},[163],{"type":28,"value":25},{"type":22,"tag":30,"props":165,"children":166},{},[167],{"type":28,"value":168},"2024 年起，浩途陆续把 LLM Agent 嵌入到客户的真实业务系统里——审批流、知识问答、\n工单分发、报表分析等。一年下来，复盘了 7 类反复踩过的坑，写下来给同行做避雷参考。",{"type":22,"tag":44,"props":170,"children":171},{},[],{"type":22,"tag":23,"props":173,"children":175},{"id":174},"坑-1权限边界没想清楚就让-agent-全能",[176],{"type":28,"value":177},"坑 1：权限边界没想清楚就让 Agent \"全能\"",{"type":22,"tag":105,"props":179,"children":180},{},[181],{"type":22,"tag":30,"props":182,"children":183},{},[184],{"type":28,"value":185},"现象：Agent 调用 API 时，能看到不属于本用户的数据。",{"type":22,"tag":30,"props":187,"children":188},{},[189],{"type":28,"value":190},"业务系统的权限模型通常是基于\"会话用户\"的，但 Agent 工作时是另一个身份。\n我们最早的做法是给 Agent 一个\"超级账号\"——很快就出问题：审批流里，Agent 帮 A 用户\n看了 B 用户的工单详情。",{"type":22,"tag":30,"props":192,"children":193},{},[194,199,201,206],{"type":22,"tag":36,"props":195,"children":196},{},[197],{"type":28,"value":198},"Plan B",{"type":28,"value":200},"：让 Agent ",{"type":22,"tag":36,"props":202,"children":203},{},[204],{"type":28,"value":205},"以调用者身份",{"type":28,"value":207},"访问业务 API，所有权限控制由原系统继承。",{"type":22,"tag":44,"props":209,"children":210},{},[],{"type":22,"tag":23,"props":212,"children":214},{"id":213},"坑-2上下文窗口一旦满了行为就开始抖",[215],{"type":28,"value":216},"坑 2：上下文窗口一旦满了，行为就开始抖",{"type":22,"tag":30,"props":218,"children":219},{},[220],{"type":28,"value":221},"（… 因篇幅省略，正文未来由内容运营补齐 …）",{"type":22,"tag":44,"props":223,"children":224},{},[],{"type":22,"tag":23,"props":226,"children":228},{"id":227},"坑-37占位",[229],{"type":28,"value":230},"坑 3—7：（占位）",{"type":22,"tag":85,"props":232,"children":233},{},[234,239,244,249,254],{"type":22,"tag":89,"props":235,"children":236},{},[237],{"type":28,"value":238},"幻觉与业务规则的协调",{"type":22,"tag":89,"props":240,"children":241},{},[242],{"type":28,"value":243},"工具调用的失败重试",{"type":22,"tag":89,"props":245,"children":246},{},[247],{"type":28,"value":248},"多轮对话状态管理",{"type":22,"tag":89,"props":250,"children":251},{},[252],{"type":28,"value":253},"成本失控与模型路由",{"type":22,"tag":89,"props":255,"children":256},{},[257],{"type":28,"value":258},"灰度上线与可回滚",{"type":22,"tag":44,"props":260,"children":261},{},[],{"type":22,"tag":23,"props":263,"children":264},{"id":118},[265],{"type":28,"value":118},{"type":22,"tag":30,"props":267,"children":268},{},[269,271,276],{"type":28,"value":270},"把 LLM 接进业务系统，难的不是模型，而是 ",{"type":22,"tag":36,"props":272,"children":273},{},[274],{"type":28,"value":275},"业务约束如何被表达成 Agent 能理解的规则",{"type":28,"value":277},"。\n浩途下一篇会写\"如何把审批流的 50 条规则，结构化喂给 Agent 而不超 token\"。",{"title":7,"searchDepth":134,"depth":134,"links":279},[280,281,282,283,284],{"id":25,"depth":134,"text":25},{"id":174,"depth":134,"text":177},{"id":213,"depth":134,"text":216},{"id":227,"depth":134,"text":230},{"id":118,"depth":134,"text":118},"content:insights:01-agent-pitfalls.md","insights\u002F01-agent-pitfalls.md","insights\u002F01-agent-pitfalls",{"_path":289,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":290,"description":7,"slug":291,"date":292,"duration":293,"category":12,"author":13,"tags":294,"body":298,"_type":140,"_id":410,"_source":142,"_file":411,"_stem":412,"_extension":145},"\u002Finsights\u002F05-llm-domain-ontology","让 LLM 读懂业务术语：从 Prompt 工程到企业本体","llm-domain-ontology","2026-02-15",9,[17,295,296,297],"Prompt","企业本体","ontology",{"type":19,"children":299,"toc":404},[300,304,316,319,324,358,363,366,372,377,385,388,392],{"type":22,"tag":23,"props":301,"children":302},{"id":25},[303],{"type":28,"value":25},{"type":22,"tag":30,"props":305,"children":306},{},[307,309,314],{"type":28,"value":308},"为某银行做信贷智能助手时，反复调试 Prompt 让 LLM 理解\"客户经理\"和\"产品经理\"\n的区别——失败。意识到：",{"type":22,"tag":36,"props":310,"children":311},{},[312],{"type":28,"value":313},"业务术语的歧义不是 Prompt 能解决的",{"type":28,"value":315},"，需要从源头注入\n企业本体（ontology）。",{"type":22,"tag":44,"props":317,"children":318},{},[],{"type":22,"tag":23,"props":320,"children":322},{"id":321},"业务术语的三种歧义",[323],{"type":28,"value":321},{"type":22,"tag":325,"props":326,"children":327},"ol",{},[328,338,348],{"type":22,"tag":89,"props":329,"children":330},{},[331,336],{"type":22,"tag":36,"props":332,"children":333},{},[334],{"type":28,"value":335},"同名异义",{"type":28,"value":337},"：客户经理（银行）vs 客户经理（地产）",{"type":22,"tag":89,"props":339,"children":340},{},[341,346],{"type":22,"tag":36,"props":342,"children":343},{},[344],{"type":28,"value":345},"异名同义",{"type":28,"value":347},"：业务员 \u002F 客户经理 \u002F 销售代表 在同一企业并存",{"type":22,"tag":89,"props":349,"children":350},{},[351,356],{"type":22,"tag":36,"props":352,"children":353},{},[354],{"type":28,"value":355},"关系隐含",{"type":28,"value":357},"：A 部门的\"主管\"对 B 部门的人是否有审批权？",{"type":22,"tag":30,"props":359,"children":360},{},[361],{"type":28,"value":362},"LLM 默认按通用语料解读，95% 场景能蒙对，关键 5% 决策上会翻车。",{"type":22,"tag":44,"props":364,"children":365},{},[],{"type":22,"tag":23,"props":367,"children":369},{"id":368},"解法业务本体显式建模-检索增强",[370],{"type":28,"value":371},"解法：业务本体显式建模 + 检索增强",{"type":22,"tag":30,"props":373,"children":374},{},[375],{"type":28,"value":376},"把企业的角色 \u002F 实体 \u002F 关系 \u002F 流程做成结构化本体，作为系统级 Prompt 的固定上下文，\n或在 RAG 时优先召回相关本体片段。",{"type":22,"tag":105,"props":378,"children":379},{},[380],{"type":22,"tag":30,"props":381,"children":382},{},[383],{"type":28,"value":384},"（具体本体格式、注入策略、性能取舍待后续）",{"type":22,"tag":44,"props":386,"children":387},{},[],{"type":22,"tag":23,"props":389,"children":390},{"id":118},[391],{"type":28,"value":118},{"type":22,"tag":30,"props":393,"children":394},{},[395,397,402],{"type":28,"value":396},"Prompt 是表达力工具，本体是知识基础设施。",{"type":22,"tag":36,"props":398,"children":399},{},[400],{"type":28,"value":401},"两件事不能互相替代",{"type":28,"value":403},"——这是把 LLM 接进\n企业的核心方法论。",{"title":7,"searchDepth":134,"depth":134,"links":405},[406,407,408,409],{"id":25,"depth":134,"text":25},{"id":321,"depth":134,"text":321},{"id":368,"depth":134,"text":371},{"id":118,"depth":134,"text":118},"content:insights:05-llm-domain-ontology.md","insights\u002F05-llm-domain-ontology.md","insights\u002F05-llm-domain-ontology",1780542368305]