<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Production-Ai on Jamal Yusuf</title><link>https://jamal.dev/tags/production-ai/</link><description>Recent content in Production-Ai on Jamal Yusuf</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 22 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://jamal.dev/tags/production-ai/index.xml" rel="self" type="application/rss+xml"/><item><title>Reliability Engineering for Generative AI Platforms</title><link>https://jamal.dev/writing/reliability-engineering-generative-ai/</link><pubDate>Mon, 22 Jun 2026 00:00:00 +0000</pubDate><guid>https://jamal.dev/writing/reliability-engineering-generative-ai/</guid><description>&lt;p&gt;The first time an AI agent I helped put into production caused a visible incident, it did not fail dramatically.&lt;/p&gt;
&lt;p&gt;It failed quietly.&lt;/p&gt;
&lt;p&gt;A claims adjustment agent, under load, began making decisions based on slightly stale eligibility data. The downstream payment system accepted the decisions. Finance noticed the variance three days later. By then we had processed thousands of incorrect adjustments.&lt;/p&gt;
&lt;p&gt;There was no stack trace. No obvious error rate spike. Just a slow, silent drift in the quality of context the agent was operating on.&lt;/p&gt;</description></item><item><title>Context Engineering for Production Agentic Systems</title><link>https://jamal.dev/writing/context-engineering-production-agents/</link><pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate><guid>https://jamal.dev/writing/context-engineering-production-agents/</guid><description>&lt;p&gt;There is a moment in every complex AI project when the prompts stop working.&lt;/p&gt;
&lt;p&gt;You have beautiful ReAct loops. You have tool schemas. You have a vector store full of relevant documents. And yet the agent drifts. It forgets constraints three turns in. It hallucinates policy details it was explicitly told. It loses the thread between a membership eligibility check and the downstream claims adjustment it was supposed to trigger.&lt;/p&gt;</description></item></channel></rss>