<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kodex Writing</title>
    <link>https://kodexlabs.dev/blog</link>
    <atom:link href="https://kodexlabs.dev/rss.xml" rel="self" type="application/rss+xml" />
    <description>Essays on building AI systems, shipping product, and the infrastructure behind them, from the Kodex team.</description>
    <language>en-us</language>
    <item>
      <title>How to vet a development agency</title>
      <link>https://kodexlabs.dev/blog/how-to-vet-a-development-agency</link>
      <guid isPermaLink="true">https://kodexlabs.dev/blog/how-to-vet-a-development-agency</guid>
      <description>Polished answers are cheap. When you vet a development agency, the useful signal is not whether they have answers. It is whether their answers have edges.</description>
      <pubDate>Sun, 01 Nov 2026 00:00:00 GMT</pubDate>
      <category>Delivery</category>
    </item>
    <item>
      <title>AI agents in production: the parts nobody demos</title>
      <link>https://kodexlabs.dev/blog/ai-agents-in-production</link>
      <guid isPermaLink="true">https://kodexlabs.dev/blog/ai-agents-in-production</guid>
      <description>Every demo works on a clean input. Production runs on mess — missing context, adversarial users, and the long tail of edge cases. This is what it actually takes to put an agent on real traffic and keep it there.</description>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>AI Systems</category>
    </item>
    <item>
      <title>RAG that actually answers: retrieval is a product problem</title>
      <link>https://kodexlabs.dev/blog/rag-that-answers</link>
      <guid isPermaLink="true">https://kodexlabs.dev/blog/rag-that-answers</guid>
      <description>Your model isn't the bottleneck. Your retrieval is. Most RAG systems fail because the data layer was designed for search, not for answers. Here's the pipeline that holds up.</description>
      <pubDate>Sun, 28 Jun 2026 00:00:00 GMT</pubDate>
      <category>AI Systems</category>
    </item>
    <item>
      <title>LLM security is not a prompt problem</title>
      <link>https://kodexlabs.dev/blog/llm-security</link>
      <guid isPermaLink="true">https://kodexlabs.dev/blog/llm-security</guid>
      <description>Prompt injection gets the headlines. It's also the least of it. The real risk in an LLM system is agency — the tools you gave the model — and the data it can reach. Here's the threat model we actually use.</description>
      <pubDate>Wed, 10 Jun 2026 00:00:00 GMT</pubDate>
      <category>Security</category>
    </item>
    <item>
      <title>Platform engineering that earns its keep</title>
      <link>https://kodexlabs.dev/blog/platform-engineering</link>
      <guid isPermaLink="true">https://kodexlabs.dev/blog/platform-engineering</guid>
      <description>Internal platforms fail when they're built for the engineering team instead of for the business. The ones that earn their budget solve one problem: how fast a product engineer goes from day one to 'it's in production'.</description>
      <pubDate>Fri, 22 May 2026 00:00:00 GMT</pubDate>
      <category>Platform</category>
    </item>
    <item>
      <title>Shipping software without the compromise</title>
      <link>https://kodexlabs.dev/blog/shipping-without-compromise</link>
      <guid isPermaLink="true">https://kodexlabs.dev/blog/shipping-without-compromise</guid>
      <description>'We had to cut corners to ship' is a story we hear constantly. It's also usually false — the corners got cut long before the deadline, in the scope, in the reviews, in the definition of done. Here's the delivery discipline that avoids it.</description>
      <pubDate>Fri, 08 May 2026 00:00:00 GMT</pubDate>
      <category>Product</category>
    </item>
    <item>
      <title>Observing LLM systems: beyond tokens and cost</title>
      <link>https://kodexlabs.dev/blog/observability-for-ai</link>
      <guid isPermaLink="true">https://kodexlabs.dev/blog/observability-for-ai</guid>
      <description>Your error rate says nothing about whether your LLM product is getting better. Quality in an LLM system is a moving target, and most dashboards can't see it. Here's what to log, trace, and alert on.</description>
      <pubDate>Fri, 24 Apr 2026 00:00:00 GMT</pubDate>
      <category>Reliability</category>
    </item>
  </channel>
</rss>
