<?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>Security on Shai Geva</title>
    <link>https://shaigeva.com/tags/security/</link>
    <description>Recent content in Security on Shai Geva</description>
    <generator>Hugo -- 0.151.0</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 30 May 2026 13:01:56 +0300</lastBuildDate>
    <atom:link href="https://shaigeva.com/tags/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AI-first design patterns - managed effects (capabilities)</title>
      <link>https://shaigeva.com/posts/ai_frameworks/04_capabilities_design_pattern/</link>
      <pubDate>Sat, 30 May 2026 13:01:56 +0300</pubDate>
      <guid>https://shaigeva.com/posts/ai_frameworks/04_capabilities_design_pattern/</guid>
      <description>&lt;span class=&#34;aside&#34;&gt;
this post is part of a &lt;a href=&#34;https://shaigeva.com/posts/ai_frameworks/01_ai_frameworks_intro&#34; target=&#34;_blank&#34;&gt;series&lt;/a&gt; about creating
production-grade maintainable AI-first projects, using AI-first design patterns and frameworks.
&lt;/span&gt;

&lt;p&gt;One design pattern that is a particularly great fit for AI-first dev is managed effects (AKA capabilities).&lt;/p&gt;
&lt;p&gt;The basic idea with managed effects is that we mechanically restrict what a piece of code can do by only giving it access to specific capabilities.&lt;br&gt;
This creates a sort-of sandbox around that piece of code, which helps us make some issues that are specific to agentic dev far more manageable.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
