Guard Duke grants using public capture uncertainty
Verify and publish checkpoint container / container (push) Successful in 11m21s

This commit is contained in:
Quintine committed 2026-10-29 19:22:46 +11:00
1 parent 5f4eeee4f1
commit 57e7611468
15 files changed
+500 -19

No files matched your search

+10
View File
@@ -17,6 +17,16 @@ open mode gates.
## Current checkpoint and work
**Duke Ambassador capture uncertainty — 29 October. Prototyped / Partial.**
Fresh games track whether a public Harkonnen capture could have involved Duke,
independent of the secret selection. When capture history is uncertain, direct
acquisition and the automatic alliance loan are uniformly guarded; unstamped
older games remain conservative. A plain Advanced Ecaz–Harkonnen game can use
both grants while its public history rules out capture. Eight related files pass
62 cases, including real setup and capture; broader combinations, resolving
uncertainty later, and deployed verification remain open.
[Scope](ECAZ_DUKE_ACQUISITION.md#public-capture-uncertainty--29-october-2026).
**Concealed Duke and Ghola guidance — 29 October. Prototyped / Partial.**
Ecaz's Ghola choices now use the same projected Duke state as ordinary revival,
so secretly executing another player's Duke captive no longer changes that