<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Reservations on Multivergence.com</title>
    <link>https://multivergence.com/tags/reservations/</link>
    <description>Recent content in Reservations 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/reservations/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How an Agent Books a Venue With Four Holds Open at Once</title>
      <link>https://multivergence.com/how-an-agent-books-a-venue-with-four-holds-open-at-once/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://multivergence.com/how-an-agent-books-a-venue-with-four-holds-open-at-once/</guid>
      <description>&lt;p&gt;Booking a venue for a team offsite is a waiting game. You ask a few places to hold the dates, and each hold runs out at a different time. Quotes come back over the afternoon and someone adds six people to the list; then the team votes. Somewhere in there a hold expires before anyone noticed, and the best option is gone.&lt;/p&gt;&#xA;&lt;p&gt;Each hold is a possible future with a clock on it, which is exactly what a Multivergence branch is. This case study goes through &lt;a href=&#34;https://github.com/multivergence/multivergence/tree/main/examples/holds&#34;&gt;examples/holds&lt;/a&gt;, where an agent keeps four holds open over two days. The figures come from its &lt;a href=&#34;https://github.com/multivergence/multivergence/blob/main/test/results/example-holds.txt&#34;&gt;recorded output&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
