<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>The Software Lens</title>
<link>https://thesoftwarelens.com/</link>
<description>The Software Lens. Frameworks and essays on agentic systems, SaaC, AIM and the architecture of the AI era, plus video episodes.</description>
<language>en-US</language>
<lastBuildDate>Fri, 09 Oct 2026 21:10:22 +0000</lastBuildDate>
<atom:link href="https://thesoftwarelens.com/feed.xml" rel="self" type="application/rss+xml" />
<item><title>The Knowledge Store Pattern: How to Build AI Agent Memory on AWS, Azure or Google Cloud</title><link>https://thesoftwarelens.com/the-knowledge-store-pattern/</link><guid isPermaLink="true">https://thesoftwarelens.com/the-knowledge-store-pattern/</guid><description>How to design AI agent memory: vector search, a graph and a record store, with the services to use on AWS (S3 Vectors, Neptune), Azure and Google Cloud.</description><category>Foundations</category><dc:creator><![CDATA[Imtiaz Hassan]]></dc:creator></item>
<item><title>The Anatomy of a Capability — and the Protocol Shift</title><link>https://thesoftwarelens.com/the-anatomy-of-a-capability-and-the-protocol-shift/</link><guid isPermaLink="true">https://thesoftwarelens.com/the-anatomy-of-a-capability-and-the-protocol-shift/</guid><description>What is a capability, formally? Four orthogonal parts: Manifest, Surface, Kernel, Guardrails. And the protocol underneath is shifting from REST to MCP. Here is why.</description><category>SaaC</category><dc:creator><![CDATA[Imtiaz Hassan]]></dc:creator></item>
<item><title>From SaaS to SaaC: Why the Delivery Model Has to Change</title><link>https://thesoftwarelens.com/from-saas-to-saac/</link><guid isPermaLink="true">https://thesoftwarelens.com/from-saas-to-saac/</guid><description>Per-seat pricing, UI-first product, integrate-once contracts — every SaaS assumption breaks when the primary caller is an agent. The delivery model that replaces it is SaaC.</description><category>SaaC</category><dc:creator><![CDATA[Imtiaz Hassan]]></dc:creator></item>
<item><title>The Four Moats: Defensibility in an Agentic Economy</title><link>https://thesoftwarelens.com/the-four-moats-defensibility-in-an-agentic-economy/</link><guid isPermaLink="true">https://thesoftwarelens.com/the-four-moats-defensibility-in-an-agentic-economy/</guid><description>If every company can buy the same AI models, where is the moat? Four places it lives in an agentic economy, and why each one compounds.</description><category>Agentic Economy</category><dc:creator><![CDATA[Imtiaz Hassan]]></dc:creator></item>
<item><title>Enterprise Integration Patterns in the Agentic Era, Part 2: Six Mistakes, Two Industries, One Architecture</title><link>https://thesoftwarelens.com/integration-patterns-agentic-era-part-2-agent-native-architecture/</link><guid isPermaLink="true">https://thesoftwarelens.com/integration-patterns-agentic-era-part-2-agent-native-architecture/</guid><description>Part 2: the six integration pitfalls of the first ninety days, higher education and fintech, and the five-layer agent-native integration architecture to build to.</description><category>Integration</category><dc:creator><![CDATA[Imtiaz Hassan]]></dc:creator></item>
<item><title>Enterprise Integration Patterns in the Agentic Era, Part 1: Why EAI, SOA and API Integration Break When the Caller Is an Agent</title><link>https://thesoftwarelens.com/integration-patterns-agentic-era-part-1-why-eai-soa-and-apis-break/</link><guid isPermaLink="true">https://thesoftwarelens.com/integration-patterns-agentic-era-part-1-why-eai-soa-and-apis-break/</guid><description>EAI, SOA and API integration assumed a human caller. Part 1: five problems AI agents expose, and which integration patterns survive, change jobs or die.</description><category>Integration</category><dc:creator><![CDATA[Imtiaz Hassan]]></dc:creator></item>
<item><title>OKL and the Organizational AI Brain</title><link>https://thesoftwarelens.com/okl-and-the-organizational-ai-brain/</link><guid isPermaLink="true">https://thesoftwarelens.com/okl-and-the-organizational-ai-brain/</guid><description>OKL — Objectives, Knowledge, Learning — is the framework that makes an organization&#x27;s learning rate measurable. Combined with the Organizational AI Brain, it becomes a runtime, not a slide.</description><category>Foundations</category><dc:creator><![CDATA[Imtiaz Hassan]]></dc:creator></item>
<item><title>Microservices Break Under Agents — And Why AIM Fits</title><link>https://thesoftwarelens.com/microservices-break-and-aim-fits/</link><guid isPermaLink="true">https://thesoftwarelens.com/microservices-break-and-aim-fits/</guid><description>Microservices were shaped for human-developer callers. Under autonomous agents, the contract breaks at four specific seams. AIM — Agents, Intelligence, MCP — is the three-layer pattern that fits.</description><category>AIM</category><dc:creator><![CDATA[Imtiaz Hassan]]></dc:creator></item>
</channel>
</rss>
