<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ErrLookup Blog</title>
    <link>https://errors.standardbeagle.com/blog/</link>
    <description>Engineering notes on building and using a machine-consumable error knowledge base.</description>
    <language>en</language>
    <atom:link href="https://errors.standardbeagle.com/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Run ErrLookup on your own internal repositories</title>
      <link>https://errors.standardbeagle.com/blog/analyze-your-internal-repos/</link>
      <guid isPermaLink="true">https://errors.standardbeagle.com/blog/analyze-your-internal-repos/</guid>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
      <description>The pipeline is a local CLI and the dataset is static files — analyze private code on your own hardware and serve the results from any internal host.</description>
    </item>
    <item>
      <title>Why error lookup matters most for compiled languages</title>
      <link>https://errors.standardbeagle.com/blog/compiled-languages-error-lookup/</link>
      <guid isPermaLink="true">https://errors.standardbeagle.com/blog/compiled-languages-error-lookup/</guid>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
      <description>When a Go binary or a JAR throws in production, the error string is often the only artifact you have — the source that raised it never shipped.</description>
    </item>
    <item>
      <title>How the ErrLookup scanner works</title>
      <link>https://errors.standardbeagle.com/blog/how-the-scanner-works/</link>
      <guid isPermaLink="true">https://errors.standardbeagle.com/blog/how-the-scanner-works/</guid>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
      <description>Deterministic candidate extraction, batched LLM analysis, and an adversarial verify pass: the pipeline that turns library source into an error knowledge base.</description>
    </item>
  </channel>
</rss>