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
@@ -17,6 +17,17 @@ open mode gates.
|
||||
|
||||
## Current checkpoint and work
|
||||
|
||||
**Basic Fremen ally revival scheduling — 29 October. Prototyped / Partial.**
|
||||
An automated mutual ally now waits for a useful human Fremen free-revival grant
|
||||
in concurrent Basic Revival, until the grant resolves or the Fremen selects the
|
||||
existing Ready action. Karama responses remain active; other bot actions do not
|
||||
wait. The Fremen panel explains the choice. Genuine setup, battle casualties,
|
||||
Nexus alliance, grant/prevention and all four automated profiles are covered;
|
||||
the four-file related batch passes 40 cases, and type checking, lint and the
|
||||
production build pass. Ordered Revival, larger alliances,
|
||||
other opportunity races and deployed acceptance remain open.
|
||||
[Scope](FREMEN_REVIVAL_GRANT.md#human-fremen-and-an-automated-ally--29-october-2026).
|
||||
|
||||
**Opt-in CHOAM market continuation — 29 October. Prototyped / Partial.**
|
||||
In supported Basic CHOAM/classic games, a human can finish a market and choose
|
||||
to skip later markets for that turn; an owner-only persistent control revokes
|
||||
|
||||
@@ -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