Freeze escalation attrition at universe fork time

docs/explanation/escalation-game.html

@@ -22,7 +22,7 @@ <h1>Escalation Game</h1>
 
 			<section id="escalation">
 				<h2>Escalation</h2>
-				<p>The first deposit after the question ends opens the game. Each deposit adds to its outcome's cumulative balance; it does not have to exceed the leader. Meanwhile the <a href="../reference/glossary.html#required-support">required support</a> rises along a fixed curve over time. The game's deadline is the moment required support overtakes binding capital, so the deadline moves later only when a deposit raises the median balance. A challenger that stops adding REP lets the rising requirement pass its stake, and the leader wins.</p>
+				<p>The first deposit after the question ends opens the game. Each deposit adds to its outcome's cumulative balance; it does not have to exceed the leader. Meanwhile the <a href="../reference/glossary.html#required-support">required support</a> rises along a fixed curve over time. The scheduled deadline estimates when required support will overtake binding capital, so it moves later only when a deposit raises the median balance. Rounding can delay the actual crossing beyond that deadline. A challenger that stops adding REP lets the rising requirement pass its stake, and the leader wins.</p>
 
 				<figure class="diagram" id="fig-statoblast-escalation-cost-curve">
 					<div class="plot-chart" data-plot-chart="fig-statoblast-escalation-cost-curve" data-plot-width="860" data-plot-height="300" role="img" aria-label="Required support from day 0 through day 52"><span class="plot-chart-fallback">Required support is zero through day 3, starts at the start bond just after day 3, and reaches the non-decision threshold on day 52.</span></div>
@@ -105,9 +105,9 @@ <h2>How the game ends</h2>
 
 				<p>The game ends in one of three ways:</p>
 				<ol>
-					<li><strong>Strict local winner.</strong> After the scheduled deadline, exactly one outcome has the greatest balance. Statoblast finalizes on that outcome.</li>
+					<li><strong>Strict local winner.</strong> Statoblast finalizes on the unique strict leader only after the scheduled deadline has passed and required support has overtaken binding capital.</li>
 					<li><strong>Local non-decision.</strong> Two outcomes reach the non-decision threshold. Statoblast uses its fork path instead of choosing one locally.</li>
-					<li><strong>Interruption by another fork.</strong> The pool's universe forks on a different question at or before the deadline. The game has no local result and continues in the child pools instead; see <a href="./statoblast.html#forks-migration">forks and migration</a>.</li>
+					<li><strong>Interruption by another fork.</strong> The pool's universe forks on a different question while the game is unresolved, even if its scheduled deadline has passed. Required support freezes at the fork, and the game continues in the child pools instead; see <a href="./statoblast.html#forks-migration">forks and migration</a>. A result already final before the fork stays settled.</li>
 				</ol>
 
 				<p>Settlement rewards the side that held its ground. Winning deposits get their principal back plus a bonus. The runner-up's stake, the binding capital, pays for it: three fifths becomes the bonus pool and two fifths, the <a href="../reference/glossary.html#escalation-haircut">escalation haircut</a>, is burned, unless the fork this game triggered already burned it as the <a href="../reference/glossary.html#fork-haircut">fork haircut</a>. REP staked on a third outcome is forfeited: a local game sweeps it to the SecurityPool, while a game carried across a fork burns it. The bonus is only available on the portion of winning deposits up to the <a href="../reference/glossary.html#reward-eligible-cap">reward-eligible cap</a>, one and a half times binding capital; deposits beyond that cap simply get their principal back. Settlement also compares the universe's current fork threshold, in full, with the non-decision threshold the game fixed when it opened. If the current fork threshold is the lower of the two, every winning withdrawal is multiplied by the current fork threshold divided by that non-decision threshold, which can push the final transfer below principal. The comparison is skipped when the universe forked after the game ended. The <a href="../reference/contracts/escalationgame.html#winning-deposit-payout">EscalationGame reference</a> works one payout through with exact numbers.</p>

docs/explanation/statoblast.html

@@ -38,7 +38,7 @@ <h2>2. Normal market lifecycle</h2>
 					<li>Vault owners deposit REP; traders deposit ETH to mint complete sets.</li>
 					<li>Traders may exchange shares through an exchange such as <a href="./trading.html">Trading</a>.</li>
 					<li>After the question ends, the first REP deposit on an outcome opens the <a href="../reference/glossary.html#escalation-game">Escalation Game</a>.</li>
-					<li>An unchallenged report wins three days later; a contested game runs until one outcome is the strict leader at its deadline. Holders then redeem winning shares from the pool's settlement collateral.</li>
+					<li>If the game finalizes locally, holders redeem winning shares from the pool's settlement collateral.</li>
 				</ol>
 				<figure class="diagram" id="fig-statoblast-share-lifecycle">
 					<div class="plot-chart" data-plot-chart="fig-statoblast-share-lifecycle" data-plot-width="860" data-plot-height="606" role="img" aria-label="Complete set lifecycle"><span class="plot-chart-fallback">ETH mints Invalid, Yes, and No shares. Operational pools redeem full sets, and finalized winning shares redeem through outcome settlement.</span></div>
@@ -111,7 +111,7 @@ <h2>3. Participants and assets</h2>
 					<h2>4. Local resolution</h2>
 					<a class="anchor-link" href="#local-resolution" aria-label="Link to Local resolution">#</a>
 				</div>
-				<p>The game opens with the first REP deposit after the question ends. REP-backed balances then accumulate behind Invalid, Yes, and No. Their median is <a href="../reference/glossary.html#binding-capital">binding capital</a> and determines the moving deadline. After that deadline, exactly one strict balance leader produces the local winner. Winning shares redeem from that pool.</p>
+				<p>The game opens with the first REP deposit after the question ends. REP-backed balances then accumulate behind Invalid, Yes, and No. Their median is <a href="../reference/glossary.html#binding-capital">binding capital</a> and determines the scheduled deadline. When the game finalizes locally, winning shares redeem from that pool.</p>
 				<p>If two outcomes reach the <a href="../reference/glossary.html#non-decision-threshold">non-decision threshold</a>, the game does not choose between them. Anyone can then fork the universe on the market question through Statoblast, which pays the <a href="../reference/glossary.html#fork-threshold">fork threshold</a> from the REP held by the pool and the game. See <a href="./escalation-game.html">the Escalation Game explanation</a> for the required-support curve, deadlines, payouts, and how games continue across forks.</p>
 			</section>
 

docs/explanation/system-overview.html

@@ -64,7 +64,7 @@ <h2>One market, start to finish</h2>
 					</ol>
 					<figcaption id="market-lifecycle-caption"><span class="figure-label">Market lifecycle.</span> The ordinary path resolves locally and skips the migration and repair steps. The fork path creates one child pool per answer and repairs each child's collateral separately.</figcaption>
 				</figure>
-				<p>Reporters stake REP behind an answer in the pool's <a href="./escalation-game.html">Escalation Game</a>, a dispute round whose deadline moves later as the contested amount grows. When the deadline finally passes, the market resolves if exactly one answer holds more REP than every other, and winning shares redeem the pool's ETH. Usually that is the end of the story.</p>
+				<p>Reporters stake REP behind an answer in the pool's <a href="./escalation-game.html">Escalation Game</a>, a dispute round whose deadline depends on the competing stakes. Once the game finalizes locally on one answer, winning shares redeem the pool's ETH.</p>
 				<p>If two answers each attract so much REP that neither can be called the winner, the pool <em>forks</em>: its universe splits into an Invalid, a Yes, and a No child. Vault owners choose a child for their vault. Shareholders can materialize their share claims in multiple children. ETH is not duplicated: each child receives only what migrates to it, and a child that comes up short holds a Truth Auction, selling its own REP for ETH to close the gap. <a href="./statoblast.html#forks-migration">Forks and migration</a> follows both paths in detail, and <a href="./zoltar.html#non-guarantees">what a fork does and does not promise</a> is the single most important thing to understand about these protocols.</p>
 			</section>
 			<nav aria-label="Continue reading"><a href="./statoblast.html">Follow a market through Statoblast</a> · <a href="./zoltar.html">Understand branching universes</a> · <a href="../reference/glossary.html">Look up a term</a></nav>