<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>LEDAR</title>
    <link>https://ledar.app/</link>
    <description>An AI employee that runs on your machine, reads your PostgreSQL database read-only, and explains what is inside it in plain language.</description>
    <language>en</language>
    <atom:link href="https://ledar.app/rss.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>All 758 foreign keys said they were enforced. None of them were.</title>
      <link>https://ledar.appundefined</link>
      <guid isPermaLink="true">https://ledar.appundefined</guid>
      <pubDate>Fri, 28 Aug 2026 09:00:00 GMT</pubDate>
      <description>We scanned a 344-million-row MusicBrainz copy. Every declared foreign key came back NOT VALID — the constraint exists, and PostgreSQL is not checking it.</description>
    </item>
    <item>
      <title>One reader in five read an empty report as &quot;everything is fine&quot;</title>
      <link>https://ledar.appundefined</link>
      <guid isPermaLink="true">https://ledar.appundefined</guid>
      <pubDate>Mon, 24 Aug 2026 09:00:00 GMT</pubDate>
      <description>We put a database report in front of real readers. The dangerous failure was not a wrong number — it was a report with nothing in it being read as good news.</description>
    </item>
    <item>
      <title>We fired 32 prompt injections at our own product. Eight got through.</title>
      <link>https://ledar.appundefined</link>
      <guid isPermaLink="true">https://ledar.appundefined</guid>
      <pubDate>Sat, 29 Aug 2026 09:00:00 GMT</pubDate>
      <description>What happened when we aimed 32 prompt-injection attempts at our own live question path, and why we are not shipping the filter that would catch them.</description>
    </item>
  </channel>
</rss>
