Prototype conditional future battle Truthtrance
Verify and publish checkpoint container / container (push) Failing after 11m11s

This commit is contained in:
Quintine committed 2026-10-28 21:17:44 +11:00
1 parent 71009d73e3
commit 02695aea7c
15 files changed
+721 -8

No files matched your search

+21
View File
@@ -1,5 +1,26 @@
# Truthtrance combined current-turn actions
## Conditional next-battle leader question — 28 October 2026
**Prototyped / Partial.** In a quiet Basic Shipment and Movement window with
classic factions and no optional modules, a player can ask whether another
player will use a named native leader in that player's first later battle this
turn, if one occurs. A definite answer creates a waiting receipt; it does not
require a shipment, movement or battle. At the first actual battle involving
that player the receipt binds its real battle event and uses the native plan
validator and guidance. If no battle occurs, the receipt expires when Battle
ends. An independently impossible answer is released by the existing battle
promise reconciliation. Another structured action answer for that respondent
is guarded while the conditional answer is active; broader promise composition,
expansion factions, optional modules and Advanced are not supported here.
The publisher's [November 2020 FAQ](https://www.gf9games.com/dune/wp-content/uploads/2020/11/Dune-FAQ-Nov-2020.pdf)
permits game-related current-turn action questions and requires honoring an
answer while possible. The first-battle binding and no-opportunity expiry are
provisional online interpretations, not specific publisher rulings. The
[native runtime tests](../tests/truth-future-battle-leader-runtime.test.ts)
exercise both answers and expiry without inventing a battle.
## Printed flight and pre-leader cards — 27 October 2026
**Prototyped / Partial.** `cardPlay/ornithopter` counts the first accepted