<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Engineering on Multivergence.com</title>
    <link>https://multivergence.com/tags/engineering/</link>
    <description>Recent content in Engineering on Multivergence.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://multivergence.com/tags/engineering/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How Multivergence Was Tested With a Thousand Crashes and 86 Million Reads</title>
      <link>https://multivergence.com/how-multivergence-was-tested-with-a-thousand-crashes-and-86-million-reads/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://multivergence.com/how-multivergence-was-tested-with-a-thousand-crashes-and-86-million-reads/</guid>
      <description>&lt;p&gt;A state engine for branching futures makes a handful of promises. A write to one branch never shows up in another. A promote happens completely or not at all, even if the process dies halfway. The same calls always give the same weights. Deadlines and constraints fire exactly when they should. And several processes can share one store without losing anything. Each of those got its own test, aimed at breaking it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
