Resolve Duke uncertainty on public events
Verify and publish checkpoint container / container (push) Canceled after 0s

This commit is contained in:
Quintine committed 2026-10-29 19:30:00 +11:00
1 parent 57e7611468
commit 59cb336c80
14 files changed
+360 -25

No files matched your search

+10
View File
@@ -17,6 +17,16 @@ open mode gates.
## Current checkpoint and work
**Resolving public Duke capture uncertainty — 29 October. Prototyped /
Partial.** Publicly established ordinary Duke battle, revival, acquisition or named
death outcomes clear the conservative capture marker, including in older games
without a marker. A later possible Harkonnen capture makes it uncertain again.
Same-recipient tenure conversion is available when history is clear. Twelve
related files pass 87 cases; some death and revival conditions are staged in
the focused fixtures. Other uncertainty resolution paths, full combinations
and deployed verification remain open.
[Scope](ECAZ_DUKE_ACQUISITION.md#public-resolution-of-capture-uncertainty--29-october-2026).
**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