Restore safe Duke grants in early legacy games
Verify and publish checkpoint container / container (push) Successful in 10m31s
Verify and publish checkpoint container / container (push) Successful in 10m31s
This commit is contained in:
1 parent
59cb336c80
commit
22b463a395
10 files changed
+263
-11
No files matched your search
@@ -17,6 +17,15 @@ open mode gates.
|
||||
|
||||
## Current checkpoint and work
|
||||
|
||||
**Early legacy Duke proof and occupied Ecaz displacement — 29 October.
|
||||
Prototyped / Partial.** An unstamped game can establish a clear capture history
|
||||
from public first-turn, pre-battle phase and continuation state; an explicit
|
||||
uncertain marker and later or ambiguous states remain guarded. An actual public
|
||||
occupied-Ecaz displacement of an ordinary living Duke grant also clears the
|
||||
marker. Eleven related files pass 73 cases, including native setup and occupation
|
||||
with controlled staging. Wider interactions, capture assurance and deployed verification remain
|
||||
open. [Scope](ECAZ_DUKE_ACQUISITION.md#public-first-turn-proof-and-occupied-ecaz-displacement--29-october-2026).
|
||||
|
||||
**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
|
||||
|
||||
Reference in new issue
Block a user