<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>RAG on C.CUI's Log</title><link>https://cuicaihao.github.io/zh/tags/rag/</link><description>Recent content in RAG on C.CUI's Log</description><generator>Hugo</generator><language>zh-Hans</language><lastBuildDate>Sun, 23 Aug 2026 07:00:00 +1000</lastBuildDate><atom:link href="https://cuicaihao.github.io/zh/tags/rag/index.xml" rel="self" type="application/rss+xml"/><item><title>企业 RAG 值不值得做：从场景选择到持续治理</title><link>https://cuicaihao.github.io/zh/posts/2026-08-23-is-enterprise-rag-worth-implementing-from-scenario-selection-to-ongoing-governance/</link><pubDate>Sun, 23 Aug 2026 07:00:00 +1000</pubDate><guid>https://cuicaihao.github.io/zh/posts/2026-08-23-is-enterprise-rag-worth-implementing-from-scenario-selection-to-ongoing-governance/</guid><description>这篇博客文章深入探讨了企业实施检索增强生成（RAG）系统时的关键考量，涵盖了从识别合适的业务场景到建立健全的持续治理框架。文章通过一个差旅政策的实际案例，阐述了RAG如何能够为员工提供精确、情境化的答案，从而解决复杂的内部查询，超越了传统搜索的局限。它强调成功的RAG部署不仅需要评估商业价值和成本效益，还必须妥善处理知识版本、访问权限和答案责任等挑战。</description></item></channel></rss>