<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SidantiX Blog</title>
    <link>https://www.sidantix.ai/blog/</link>
    <atom:link href="https://www.sidantix.ai/blog/feed.xml" rel="self" type="application/rss+xml" />
    <description>Notes from the founder on making autonomous IGA real. Design decisions, tradeoffs, and open specs. No fluff.</description>
    <language>en-us</language>
    <copyright>© 2026 SidantiX</copyright>
    <managingEditor>hello@sidantix.com (Phani Kolli)</managingEditor>
    <webMaster>hello@sidantix.com (Phani Kolli)</webMaster>
    <lastBuildDate>Fri, 01 Aug 2026 12:00:00 -0700</lastBuildDate>
    <generator>Hand-authored — SidantiX 2026</generator>

    <item>
      <title>Why your AI agents need an expiration date — and 4 other controls nobody ships</title>
      <link>https://www.sidantix.ai/blog/ai-safety-hardening</link>
      <guid isPermaLink="true">https://www.sidantix.ai/blog/ai-safety-hardening</guid>
      <pubDate>Fri, 01 Aug 2026 12:00:00 -0700</pubDate>
      <author>hello@sidantix.com (Phani Kolli)</author>
      <category>AI-agent security</category>
      <category>AI hardening</category>
      <description>Five AI-agent safety controls that separate real governance from checkbox theater: egress allowlists, constitution attestation, time-bounded delegations, adversarial CI, and kill-switch SLOs.</description>
    </item>

    <item>
      <title>5 questions to ask any AI-agent governance vendor before you sign</title>
      <link>https://www.sidantix.ai/blog/five-questions</link>
      <guid isPermaLink="true">https://www.sidantix.ai/blog/five-questions</guid>
      <pubDate>Sat, 02 Aug 2026 00:00:00 -0700</pubDate>
      <author>hello@sidantix.com (Phani Kolli)</author>
      <category>AI-agent security</category>
      <category>Buyer guide</category>
      <description>A buyer-side checklist for evaluating AI-agent governance vendors. Every question is designed to separate real cryptographic controls from configuration theater.</description>
    </item>

    <item>
      <title>When your AI model tries to escape — what actually stops it</title>
      <link>https://www.sidantix.ai/blog/ai-model-breakout</link>
      <guid isPermaLink="true">https://www.sidantix.ai/blog/ai-model-breakout</guid>
      <pubDate>Fri, 01 Aug 2026 00:00:00 -0700</pubDate>
      <author>hello@sidantix.com (Phani Kolli)</author>
      <category>AI-agent security</category>
      <category>Incident response</category>
      <description>The recent Anthropic and OpenAI announcements about their own models bypassing safety controls are not one-off incidents. They're a category of failure that runtime-configurable safety systems can't stop. Here's what actually can.</description>
    </item>

    <item>
      <title>The Machine Constitution — invariants for AI agents that no runtime config can override</title>
      <link>https://www.sidantix.ai/blog/machine-constitution</link>
      <guid isPermaLink="true">https://www.sidantix.ai/blog/machine-constitution</guid>
      <pubDate>Fri, 01 Aug 2026 00:00:00 -0700</pubDate>
      <author>hello@sidantix.com (Phani Kolli)</author>
      <category>AI-agent security</category>
      <category>Open source</category>
      <description>An open format for the safety invariants every AI-agent policy engine needs — and why runtime-mutable rules are a category error.</description>
    </item>

  </channel>
</rss>
