<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on Theorem</title><link>https://theorem-blockprint.pages.dev/blog/</link><description>Recent content in Blog on Theorem</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 05 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://theorem-blockprint.pages.dev/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>`lf-lean`: The frontier of verified software engineering</title><link>https://theorem-blockprint.pages.dev/blog/lf-lean/</link><pubDate>Thu, 05 Feb 2026 00:00:00 +0000</pubDate><guid>https://theorem-blockprint.pages.dev/blog/lf-lean/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;&#10;&lt;p&gt;As AIs automate increasingly complex software tasks, one question gets harder to answer: how do we know the code they produce is correct? The standard approach of reviewing AI-generated code and its tests doesn&amp;rsquo;t scale.&#10;Human review effort grows proportionally with code volume, while AI code generation capacity grows exponentially.&lt;label for="sn-bug-growth" class="sidenote-number"&gt;1&lt;/label&gt;&#10;&lt;input type="checkbox" id="sn-bug-growth" class="sidenote-toggle-input" /&gt;&#10;&lt;span class="sidenote"&gt;&lt;span class="sidenote-num"&gt;1&lt;/span&gt; Frontier software engineering typically results in multiplicative bug growth; many bugs are subtle and interaction-driven, and their count grows super-linearly with code length and complexity. See &lt;a href="#appendix-c"&gt;Appendix C&lt;/a&gt;.&lt;/span&gt;&#10;&#10;If this trend continues, we&amp;rsquo;re headed toward a world where code deployment is bottlenecked on human review capacity, or just deployed without review.&lt;/p&gt;</description></item><item><title>Catching bugs with fractional proofs</title><link>https://theorem-blockprint.pages.dev/blog/catching-bugs-with-fractional-proofs/</link><pubDate>Tue, 07 Oct 2025 00:00:00 +0000</pubDate><guid>https://theorem-blockprint.pages.dev/blog/catching-bugs-with-fractional-proofs/</guid><description>&lt;p class="post-description"&gt;Fractional proof decomposition fuses partial evaluation and property-based testing to scale testing compute logarithmically with bug rarity, instead of linearly.&lt;/p&gt;&#10;&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;&#10;&lt;p&gt;Most large projects have a limited compute budget for testing, lest it slow down the CI pipeline.&#10;This means missing rare edge cases until customers find them in production.&#10;I love formal verification! And I want to bring the power of reasoning about program structure to testing.&#10;In this blog post, I will briefly introduce fractional proof decomposition, our new technique that makes testing compute scale logarithmically with bug rarity instead of linearly.&lt;/p&gt;&#10;&lt;p&gt;As a demo, I&amp;rsquo;ll walk through how this approach would have caught Anthropic&amp;rsquo;s recent &lt;a href="https://www.anthropic.com/engineering/a-postmortem-of-three-recent-issues"&gt;approximate top-K bug&lt;/a&gt;. Note that we generate these unit tests without relying on the bug reproducer code, using just the high-level specification of top-K sampling.&lt;/p&gt;</description></item></channel></rss>