<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Model-Checking on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/model-checking/</link>
    <description>Recent content in Model-Checking on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 13 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/model-checking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>TLA&#43; vs Apalache vs CBMC in 2026: Which Model Checker Should You Actually Use?</title>
      <link>https://www.pistack.xyz/posts/2026-10-13-model-checkers-tlaplus-apalache-cbmc-guide/</link>
      <pubDate>Tue, 13 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-13-model-checkers-tlaplus-apalache-cbmc-guide/</guid>
      <description>&lt;p&gt;Some bugs are invisible to every test you will ever write. A distributed lock that passes code review can still lose a message under one interleaving in ten million, and no amount of unit testing explores the schedules your production cluster will invent at 3 a.m. Model checkers exist to attack exactly that class of bug — by enumerating the behaviours your design allows instead of sampling a handful of them.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
