<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Orchestration on Eugeniusz Zabłocki Blog</title>
    <link>https://ezablocki.com/tags/orchestration/</link>
    <description>Recent content in Orchestration on Eugeniusz Zabłocki Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>© Eugeniusz Zabłocki</copyright>
    <lastBuildDate>Thu, 14 May 2026 13:18:08 +0200</lastBuildDate><atom:link href="https://ezablocki.com/tags/orchestration/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Beyond &#34;Dumb&#34; Chatbots: Building a Stateful Security Gatekeeper with LangGraph</title>
      <link>https://ezablocki.com/posts/building-stateful-security-gatekeeper-langgraph/</link>
      <pubDate>Thu, 14 May 2026 13:18:08 +0200</pubDate>
      
      <guid>https://ezablocki.com/posts/building-stateful-security-gatekeeper-langgraph/</guid>
      <description>The industry is currently obsessed with &amp;ldquo;prompt engineering.&amp;rdquo; But if you’re building a security gatekeeper for your project dependencies, a better prompt won&amp;rsquo;t save you. The problem isn&amp;rsquo;t that LLMs are &amp;ldquo;dumb&amp;rdquo;; it’s that they are stateless. Asking a standard LLM to audit a package.json is like asking a genius lawyer to review a contract while they are suffering from short-term memory loss.
If you want AI to actually gatekeep your dependencies, you don&amp;rsquo;t need another chat window.</description>
    </item>
    
  </channel>
</rss>
