<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Durgesh Rathod — Agent reliability notes</title><description>I help teams turn AI agent prototypes into systems they can bill customers for — evals, cost control, and observability. 9 years of distributed systems, now applied to agent reliability.</description><link>https://durgeshrathod.com/</link><language>en-us</language><copyright>© 2026 Durgesh Rathod</copyright><item><title>What to look for in an agent design review</title><link>https://durgeshrathod.com/notes/agent-design-review/</link><guid isPermaLink="true">https://durgeshrathod.com/notes/agent-design-review/</guid><description>Reviewing an agent feature before it ships is the cheapest reliability work available, and most teams review the prompt rather than the architecture. Nine questions that catch the expensive problems while they are still free.</description><pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate><category>Notes</category><category>agent design review</category><category>AI code review checklist</category><category>LLM architecture review</category><category>agent feature review</category></item><item><title>Where your context window actually goes</title><link>https://durgeshrathod.com/notes/context-window-budget/</link><guid isPermaLink="true">https://durgeshrathod.com/notes/context-window-budget/</guid><description>A million-token window does not mean you should use it. Decompose one real conversation and the proportions are usually a surprise — history dominates, tool definitions are larger than expected, and the useful content is a minority of what you pay for.</description><pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate><category>Notes</category><category>LLM context window</category><category>context window budget</category><category>conversation history cost</category><category>LLM token usage</category></item><item><title>Event-driven agents: what Kafka taught me about agent architecture</title><link>https://durgeshrathod.com/notes/event-driven-agents/</link><guid isPermaLink="true">https://durgeshrathod.com/notes/event-driven-agents/</guid><description>A 20% input spike once turned a healthy pipeline into an outage because it had no backpressure — it had optimism. Every concept that prevents that has a direct agent equivalent, and almost no agent codebase implements any of them.</description><pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate><category>Notes</category><category>event-driven agents</category><category>Kafka LLM architecture</category><category>async agent design</category><category>agent backpressure</category><category>LLM streaming data</category></item><item><title>LLM-as-judge is overused</title><link>https://durgeshrathod.com/notes/llm-as-judge-overused/</link><guid isPermaLink="true">https://durgeshrathod.com/notes/llm-as-judge-overused/</guid><description>It is slow, it costs money on every CI run, and it is non-deterministic — which means your test suite has flaky tests by construction. About 70% of the checks teams reach for a judge to make can be written as assertions instead.</description><pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate><category>Notes</category><category>LLM as judge</category><category>LLM evaluation methods</category><category>AI eval assertions</category><category>LLM testing CI</category></item><item><title>MCP in production: what the protocol gives you and what it does not</title><link>https://durgeshrathod.com/notes/mcp-in-production/</link><guid isPermaLink="true">https://durgeshrathod.com/notes/mcp-in-production/</guid><description>Model Context Protocol moves your tool boundary into a place where validation and authorisation naturally live. That is the real benefit, and it is not the one usually advertised. What it does not give you: security, cheaper tokens, or a reason to trust tool arguments.</description><pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate><category>Notes</category><category>Model Context Protocol production</category><category>MCP best practices</category><category>MCP security</category><category>MCP tool design</category><category>MCP vs function calling</category></item><item><title>Model routing is the biggest cost lever, and it needs evals first</title><link>https://durgeshrathod.com/notes/model-routing/</link><guid isPermaLink="true">https://durgeshrathod.com/notes/model-routing/</guid><description>Routing tasks by difficulty typically recovers 40–70% of spend. It is also the only cost lever that can silently degrade quality — which is why the teams that most need it are usually the ones least equipped to do it safely.</description><pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate><category>Notes</category><category>LLM model routing</category><category>reduce LLM costs</category><category>model selection by task</category><category>LLM cost optimisation</category></item><item><title>Prompt caching and semantic caching are not the same thing</title><link>https://durgeshrathod.com/notes/prompt-caching-vs-semantic-caching/</link><guid isPermaLink="true">https://durgeshrathod.com/notes/prompt-caching-vs-semantic-caching/</guid><description>They get discussed interchangeably and they solve different problems with different risks. One is a billing mechanism with a write premium that can lose you money; the other returns a previous answer to a different question and can leak across tenants.</description><pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate><category>Notes</category><category>prompt caching</category><category>semantic caching LLM</category><category>LLM cache hit rate</category><category>LLM cost caching</category></item><item><title>Prompt versioning: your prompts are deployable artefacts</title><link>https://durgeshrathod.com/notes/prompt-versioning/</link><guid isPermaLink="true">https://durgeshrathod.com/notes/prompt-versioning/</guid><description>If a customer reports a bad answer from last Tuesday, can you reconstruct the exact prompt that produced it? Most teams cannot, and it makes every subsequent investigation archaeology.</description><pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate><category>Notes</category><category>prompt versioning</category><category>LLM prompt management</category><category>prompt rollback</category><category>LLM reproducibility</category></item><item><title>The tool-definition tax: what your agent pays before it does anything</title><link>https://durgeshrathod.com/notes/tool-definition-token-cost/</link><guid isPermaLink="true">https://durgeshrathod.com/notes/tool-definition-token-cost/</guid><description>Every tool schema you attach is billed on every single call, whether the agent uses it or not — plus a per-model tool-use system prompt of 286 to 804 tokens. Here is how to measure that fixed cost and what it does to your bill at scale.</description><pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate><category>Notes</category><category>LLM cost optimisation</category><category>tool definitions tokens</category><category>agent cost</category><category>prompt caching</category><category>MCP</category></item><item><title>Your agent doesn&apos;t have a model problem</title><link>https://durgeshrathod.com/notes/why-ai-agents-fail-in-production/</link><guid isPermaLink="true">https://durgeshrathod.com/notes/why-ai-agents-fail-in-production/</guid><description>Almost every failing agent I have looked at is failing on engineering discipline, not model capability. The evidence is that upgrading the model rarely fixes it — and the four things that do are unglamorous.</description><pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate><category>Notes</category><category>why AI agents fail in production</category><category>AI agent reliability</category><category>LLM engineering discipline</category><category>production AI systems</category></item><item><title>A text-to-SQL agent 2,000 people could actually trust with HR data</title><link>https://durgeshrathod.com/work/hr-analytics-agent/</link><guid isPermaLink="true">https://durgeshrathod.com/work/hr-analytics-agent/</guid><description>A natural-language analytics agent over sensitive workforce data, serving 2,000 concurrent users across isolated tenants. Reporting went from 2–3 days to under 30 seconds — but only after we stopped trusting the model with the boundary.</description><pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate><category>Case study</category><category>text-to-SQL</category><category>multi-tenant LLM</category><category>conversational analytics</category><category>HR analytics AI</category><category>tenant isolation</category></item><item><title>Multi-agent systems without the spiral</title><link>https://durgeshrathod.com/work/multi-agent-orchestration/</link><guid isPermaLink="true">https://durgeshrathod.com/work/multi-agent-orchestration/</guid><description>Two production agent systems on MCP and CrewAI — a project-management assistant and an autonomous lead-generation pipeline. What multi-agent buys you, what it costs, and the specific cases where a single agent with good tools wins.</description><pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate><category>Case study</category><category>multi-agent systems</category><category>Model Context Protocol</category><category>MCP</category><category>CrewAI</category><category>agent orchestration</category></item><item><title>520 million parameters every 15 minutes</title><link>https://durgeshrathod.com/work/telecom-throughput/</link><guid isPermaLink="true">https://durgeshrathod.com/work/telecom-throughput/</guid><description>A configuration-driven telecom data platform processing 200M configuration and 320M performance parameters per 15-minute cycle on Golang, Kafka, Kubernetes and PostgreSQL. The project that shaped how I think about bounded resources — and why I trust it more than any AI credential I have.</description><pubDate>Sun, 02 Aug 2026 00:00:00 GMT</pubDate><category>Case study</category><category>high throughput data pipeline</category><category>Golang Kafka Kubernetes</category><category>configuration-driven architecture</category><category>telecom performance management</category><category>distributed systems</category></item></channel></rss>