Preserve Fremen revival grant opportunity for bot allies
Verify and publish checkpoint container / container (push) Successful in 10m54s
Verify and publish checkpoint container / container (push) Successful in 10m54s
This commit is contained in:
1 parent
825f903cce
commit
ac7db3cb35
7 files changed
+201
-2
No files matched your search
@@ -1,5 +1,18 @@
|
||||
# Fremen allied free revival
|
||||
|
||||
## Human Fremen and an automated ally — 29 October 2026
|
||||
|
||||
**Prototyped / Partial.** During concurrent Basic Revival, an automated mutual
|
||||
ally waits to make its ordinary force return or finish Revival while a human
|
||||
Fremen has an eligible grant that would increase that ally's remaining free
|
||||
allowance and the ally has forces in the Tanks. The Fremen may use the existing
|
||||
grant action; its ordinary Karama response still resolves before the ally acts.
|
||||
The Fremen's existing Ready for next phase also releases the wait, as do an
|
||||
accepted or prevented grant. Other bot actions and responses remain available.
|
||||
The Fremen panel explains this scheduling choice. This is a provisional online
|
||||
priority policy, not a printed rule or a new mandatory confirmation. Ordered
|
||||
Revival, larger alliances and other races are not covered by this policy.
|
||||
|
||||
## Staged three-member alliance — 28 October 2026
|
||||
|
||||
In the unexposed Basic classic group prototype, Fremen may select each of its
|
||||
|
||||
Reference in new issue
Block a user