<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Context-Engineering on Girish Shekhar</title><link>https://blog.girishshekhar.com/tags/context-engineering/</link><description>Recent content in Context-Engineering on Girish Shekhar</description><generator>Hugo -- 0.163.3</generator><language>en-us</language><lastBuildDate>Sun, 10 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.girishshekhar.com/tags/context-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>Context Is the Real Engineering Problem</title><link>https://blog.girishshekhar.com/posts/agent-coordination-patterns/3-context-engineering-is-the-real-problem/</link><pubDate>Sun, 10 May 2026 00:00:00 +0000</pubDate><guid>https://blog.girishshekhar.com/posts/agent-coordination-patterns/3-context-engineering-is-the-real-problem/</guid><description>The coordination patterns are well understood. The protocol layer is converging. The unsolved problem is context: how do you decide what to pass between agents, when to summarize versus delegate in full, and how to do this without the routing decision itself becoming the expensive part. This post lands the thesis — and examines what happens when agents coordinate asynchronously across disconnected environments.</description></item></channel></rss>