<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Sentry Blog · Lunar Occultation</title>
    <link>https://lunaroccultation.com/blog</link>
    <description>Field notes from the frontier of regulated AI. Audit checklists, threat patterns, architecture decisions.</description>
    <language>en-us</language>
    <image>
      <url>https://lunaroccultation.com/favicon.svg</url>
      <title>Sentry Blog · Lunar Occultation</title>
      <link>https://lunaroccultation.com/blog</link>
    </image>
    <atom:link href="https://lunaroccultation.com/rss.xml" rel="self" type="application/rss+xml" />

    <item>
      <title>Why we built a DSL, not a drag-and-drop policy builder</title>
      <link>https://lunaroccultation.com/blog/why-a-dsl-not-a-ui-builder</link>
      <guid isPermaLink="true">https://lunaroccultation.com/blog/why-a-dsl-not-a-ui-builder</guid>
      <description>Every AI governance product on the market has a UI builder. Here is the engineering case for why we gave Sentry a regex-first language instead — and why your platform team will actually prefer it.</description>
      <dc:creator>Mikael Eyob</dc:creator>
      <pubDate>Fri, 27 Feb 2026 09:00:00 GMT</pubDate>
      <category>SentryDSL</category>
      <category>Architecture</category>
    </item>

    <item>
      <title>Gateway vs sidecar: the architectural choice that decides your AI audit</title>
      <link>https://lunaroccultation.com/blog/gateway-vs-sidecar-ai-governance</link>
      <guid isPermaLink="true">https://lunaroccultation.com/blog/gateway-vs-sidecar-ai-governance</guid>
      <description>You can enforce AI policies in two places: at the gateway or in a sidecar. The choice sounds academic. It is not. One passes an audit; the other does not.</description>
      <dc:creator>Priya Chandrasekaran</dc:creator>
      <pubDate>Sat, 21 Feb 2026 09:00:00 GMT</pubDate>
      <category>Architecture</category>
    </item>

    <item>
      <title>EU AI Act Article 14, in practice: the working checklist</title>
      <link>https://lunaroccultation.com/blog/eu-ai-act-article-14-checklist</link>
      <guid isPermaLink="true">https://lunaroccultation.com/blog/eu-ai-act-article-14-checklist</guid>
      <description>Article 14 — Human Oversight — is the one AI Act obligation your deploy pipeline interacts with every day. A ten-point checklist that passes a real audit.</description>
      <dc:creator>Harini Varma</dc:creator>
      <pubDate>Fri, 20 Feb 2026 09:00:00 GMT</pubDate>
      <category>Compliance</category>
      <category>EU AI Act</category>
    </item>

    <item>
      <title>The prompt-injection patterns Sentry blocks, with regexes</title>
      <link>https://lunaroccultation.com/blog/prompt-injection-patterns-we-block</link>
      <guid isPermaLink="true">https://lunaroccultation.com/blog/prompt-injection-patterns-we-block</guid>
      <description>Prompt injection isn't one attack — it's seven. Here are the regex families Sentry ships with by default, what each one actually matches, and where to extend them.</description>
      <dc:creator>Mikael Eyob</dc:creator>
      <pubDate>Sat, 14 Feb 2026 09:00:00 GMT</pubDate>
      <category>Security</category>
      <category>SentryDSL</category>
    </item>

    <item>
      <title>Anatomy of a $20M AI incident — reconstructed from public filings</title>
      <link>https://lunaroccultation.com/blog/twenty-million-dollar-ai-incident</link>
      <guid isPermaLink="true">https://lunaroccultation.com/blog/twenty-million-dollar-ai-incident</guid>
      <description>A Fortune 500 retailer, a customer service chatbot, and a single prompt injection that cost twenty million dollars in sixty-three days. Four controls that would have prevented it.</description>
      <dc:creator>Harini Varma</dc:creator>
      <pubDate>Fri, 13 Feb 2026 09:00:00 GMT</pubDate>
      <category>Case Study</category>
      <category>Security</category>
    </item>

    <item>
      <title>Signed evidence 101: what a regulator actually wants</title>
      <link>https://lunaroccultation.com/blog/signed-evidence-101</link>
      <guid isPermaLink="true">https://lunaroccultation.com/blog/signed-evidence-101</guid>
      <description>A regulator will ask one question: prove this decision was consistent with your stated policies on the day it happened. The one artifact that answers it.</description>
      <dc:creator>Priya Chandrasekaran</dc:creator>
      <pubDate>Sat, 07 Feb 2026 09:00:00 GMT</pubDate>
      <category>Architecture</category>
      <category>Audit</category>
    </item>
  </channel>
</rss>
