<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Agent Engineering Lab</title><description>Field Notes, Signal, Recipes, and Lab Reports from the agentic AI publication by Sunil Prakash.</description><link>https://agenticlab.sunilprakash.com/</link><language>en-us</language><item><title>FN-004: Loop engineering is a 30-year-old loop with a new hashtag</title><link>https://agenticlab.sunilprakash.com/field-notes/004-loop-engineering-30-year-old-loop/</link><guid isPermaLink="true">https://agenticlab.sunilprakash.com/field-notes/004-loop-engineering-30-year-old-loop/</guid><description>Loop engineering renamed a three-decade-old idea. The stop condition it treats as a detail was named unsolved in 1995, the self-verification it assumes is contradicted by the evidence, and nobody connects loops that run while you sleep to the credential gap that deletes production databases.</description><pubDate>Thu, 25 Jun 2026 00:00:00 GMT</pubDate><category>Field Notes</category></item><item><title>SG-003: Multi-agent is not an architecture decision. It is a workload decision.</title><link>https://agenticlab.sunilprakash.com/signal/003-multi-agent-decision-variable/</link><guid isPermaLink="true">https://agenticlab.sunilprakash.com/signal/003-multi-agent-decision-variable/</guid><description>Anthropic and Cognition published seemingly opposite conclusions on multi-agent systems within a day of each other in June 2025. Both are right, because they measured different workload shapes. The decision is not multi-agent yes or no. It is whether the work requires decomposition a router cannot encode. This Signal gives the decision rule, the primary sources on both sides, and a first-party 100-query experiment measuring the cost of getting it wrong.</description><pubDate>Sun, 07 Jun 2026 00:00:00 GMT</pubDate><category>Signal</category></item><item><title>FN-003: Anthropic just told you the harness is the product</title><link>https://agenticlab.sunilprakash.com/field-notes/003-anthropic-told-you-harness-is-product/</link><guid isPermaLink="true">https://agenticlab.sunilprakash.com/field-notes/003-anthropic-told-you-harness-is-product/</guid><description>Anthropic&apos;s recent moves, an earlier independent essay, and a late-2025 preprint say the same thing. The unit of evaluation is harness plus model plus task.</description><pubDate>Tue, 26 May 2026 00:00:00 GMT</pubDate><category>Field Notes</category></item><item><title>SG-002: Long context did not kill RAG. It changed what retrieval is for.</title><link>https://agenticlab.sunilprakash.com/signal/002-when-long-context-replaces-rag/</link><guid isPermaLink="true">https://agenticlab.sunilprakash.com/signal/002-when-long-context-replaces-rag/</guid><description>Long context replaced lookup, not retrieval. Production architecture turns on whether the system needs to select, cite, govern, or update evidence. This Signal gives the routing rule, the academic literature behind it, and the control-plane reframe that follows.</description><pubDate>Sat, 23 May 2026 00:00:00 GMT</pubDate><category>Signal</category></item><item><title>LAB-001: Multi-agent vs router on 100 customer-support queries</title><link>https://agenticlab.sunilprakash.com/labs/multi-agent-vs-router-100-queries/</link><guid isPermaLink="true">https://agenticlab.sunilprakash.com/labs/multi-agent-vs-router-100-queries/</guid><description>100 real support queries from a public dataset, run twice — once through a single-agent workflow router, once through a 3-agent hierarchical multi-agent system. Measured against the same eval rubric.</description><pubDate>Wed, 20 May 2026 00:00:00 GMT</pubDate><category>Labs</category></item><item><title>FN-002: Your eval rubric needs failure buckets, not just scores</title><link>https://agenticlab.sunilprakash.com/field-notes/002-eval-rubric-failure-buckets/</link><guid isPermaLink="true">https://agenticlab.sunilprakash.com/field-notes/002-eval-rubric-failure-buckets/</guid><description>Two agents can score identically on a benchmark and fail differently in production. Failure buckets are the rubric. The aggregate is what falls out of it.</description><pubDate>Sun, 17 May 2026 00:00:00 GMT</pubDate><category>Field Notes</category></item><item><title>FN-001: The multi-agent papers nobody is citing</title><link>https://agenticlab.sunilprakash.com/field-notes/001-multi-agent-papers-nobody-cites/</link><guid isPermaLink="true">https://agenticlab.sunilprakash.com/field-notes/001-multi-agent-papers-nobody-cites/</guid><description>Three papers and one practitioner survey put multi-agent failure rates between 41 and 86.7 percent and error amplification up to 17.2x. The version that survived production looks more like a CI pipeline than a faculty meeting.</description><pubDate>Thu, 14 May 2026 00:00:00 GMT</pubDate><category>Field Notes</category></item><item><title>SG-001: The skills.md discourse is sharpening the wrong knife</title><link>https://agenticlab.sunilprakash.com/signal/001-skills-md-wrong-knife/</link><guid isPermaLink="true">https://agenticlab.sunilprakash.com/signal/001-skills-md-wrong-knife/</guid><description>Most skills.md advice in circulation is optimizing the wrong surface. Anthropic&apos;s docs name the real constraint: a 1% context-window budget for descriptions that quietly trims the labels of skills you invoke least. The marketplace economy is a retrieval anti-pattern.</description><pubDate>Thu, 14 May 2026 00:00:00 GMT</pubDate><category>Signal</category></item><item><title>R-001: Build and deploy your first Strands agent on AgentCore Runtime</title><link>https://agenticlab.sunilprakash.com/recipes/001-strands-on-agentcore-runtime/</link><guid isPermaLink="true">https://agenticlab.sunilprakash.com/recipes/001-strands-on-agentcore-runtime/</guid><description>Build and deploy a working Strands agent on AWS Bedrock AgentCore Runtime in an afternoon. Uses the modern @aws/agentcore CLI (npm) on a current AWS account, not the deprecated Python starter toolkit. Verified on a live deploy.</description><pubDate>Wed, 13 May 2026 00:00:00 GMT</pubDate><category>Recipes</category></item></channel></rss>