<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>NivaMind Insights</title>
    <link>https://nivamind.com/insights</link>
    <description>Practical writing on building AI systems that hold up in production.</description>
    <language>en</language>
    <atom:link href="https://nivamind.com/rss.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>Why most RAG systems fail in production</title>
      <link>https://nivamind.com/insights/why-most-rag-systems-fail-in-production</link>
      <guid isPermaLink="true">https://nivamind.com/insights/why-most-rag-systems-fail-in-production</guid>
      <description>Retrieval-augmented generation demos are easy and production RAG is not. The failures are predictable, and almost all of them happen in retrieval rather than generation.</description>
      <pubDate>Tue, 11 Aug 2026 09:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Evaluating LLM features without fooling yourself</title>
      <link>https://nivamind.com/insights/evaluating-llm-features-without-fooling-yourself</link>
      <guid isPermaLink="true">https://nivamind.com/insights/evaluating-llm-features-without-fooling-yourself</guid>
      <description>A practical evaluation stack: golden sets, LLM-as-judge with its known biases, regression gates in CI, and the metrics that actually correlate with user trust.</description>
      <pubDate>Tue, 28 Jul 2026 09:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The real cost of an AI feature</title>
      <link>https://nivamind.com/insights/the-real-cost-of-an-ai-feature</link>
      <guid isPermaLink="true">https://nivamind.com/insights/the-real-cost-of-an-ai-feature</guid>
      <description>Token pricing is the smallest line in the budget. Here is the cost model we use with clients, covering inference, retrieval infrastructure, evaluation, human review and the ongoing maintenance nobody scopes.</description>
      <pubDate>Tue, 14 Jul 2026 09:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
