<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Agentic Architect — Daily Senior Rule</title>
    <link>https://agenticstandardcontact-byte.github.io/agentic-architect/blog/</link>
    <description>One practical Cursor + C#/.NET pattern per day. Field notes from building a stateful AI partner for production .NET codebases.</description>
    <language>en-gb</language>
    <atom:link href="https://agenticstandardcontact-byte.github.io/agentic-architect/feed.xml" rel="self" type="application/rss+xml" />

    <item>
      <title>The Scoped→Singleton DI bug your AI just suggested (and how to catch it)</title>
      <link>https://agenticstandardcontact-byte.github.io/agentic-architect/blog/02-scoped-singleton-di-bug.html</link>
      <guid isPermaLink="true">https://agenticstandardcontact-byte.github.io/agentic-architect/blog/02-scoped-singleton-di-bug.html</guid>
      <pubDate>Wed, 20 May 2026 08:00:00 +0000</pubDate>
      <description>The .NET lifetime bug that ships silently — and the Cursor rule that catches it before merge.</description>
    </item>

    <item>
      <title>The Context Tax: Why every Cursor session costs you 15 minutes</title>
      <link>https://agenticstandardcontact-byte.github.io/agentic-architect/blog/01-the-context-tax.html</link>
      <guid isPermaLink="true">https://agenticstandardcontact-byte.github.io/agentic-architect/blog/01-the-context-tax.html</guid>
      <pubDate>Tue, 19 May 2026 22:00:00 +0000</pubDate>
      <description>The hidden cost senior engineers pay every morning — and a four-rule architecture for eliminating it.</description>
    </item>

      <item>
      <title>Rule 2: Persistence Boundaries</title>
      <link>https://agenticstandardcontact-byte.github.io/agentic-architect/blog/daily-rules.html#2026-05-20</link>
      <guid isPermaLink="false">daily-rule-2026-05-20</guid>
      <pubDate>Wed, 20 May 2026 09:00:00 +0000</pubDate>
      <description>Never let the AI write database logic in your Controllers. Enforce a strict boundary where all IQueryable access stays in the Infrastructure layer. This keeps your business logic "pure" and readable for the LLM.</description>
    </item>

  </channel>
</rss>
