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