Support sector-specific Truthtrance shipments
This commit is contained in:
1 parent
8006e53580
commit
536d334543
27 files changed
+1121
-71
No files matched your search
@@ -20,6 +20,14 @@ open mode gates.
|
||||
Keep identified Basic-function gaps ahead of Advanced and wider interactions.
|
||||
Prototype labels and final acceptance gates remain.
|
||||
|
||||
**Truthtrance shipment sectors — 27 October. Prototyped / Partial.**
|
||||
A future reserve-shipment condition may name an exact printed sector or the
|
||||
whole territory. Sector and territory clauses share the original physical
|
||||
shipment and payment, including combined answers and private native guidance.
|
||||
Older sectorless receipts keep their existing meaning. Broader combinations,
|
||||
complete rules and deployed acceptance remain open.
|
||||
[Scope](TRUTHTRANCE_TURN_ACTIONS.md#reserve-shipment-sector--27-october-2026).
|
||||
|
||||
**Truthtrance upcoming Basic storm dial — 27 October. Prototyped / Partial.**
|
||||
An exact-value condition binds an eligible player's original unsubmitted native
|
||||
dial, with the normal first-turn or later range. The same sealed submission
|
||||
|
||||
@@ -1,5 +1,14 @@
|
||||
# Dune implementation status
|
||||
|
||||
## 27 October 2026 — Truthtrance reserve shipment sector
|
||||
|
||||
An optional exact printed sector is part of the existing future reserve
|
||||
shipment condition. Combined answers use one native shipment, its physical
|
||||
forces and actual payment; private guidance and minimal bot actions use the
|
||||
real sector. Sectorless legacy receipts retain their old shape. Broader
|
||||
interactions, complete rules and deployed acceptance remain open.
|
||||
[Contract](TRUTHTRANCE_TURN_ACTIONS.md#reserve-shipment-sector--27-october-2026).
|
||||
|
||||
## 27 October 2026 — Truthtrance upcoming Basic storm dial
|
||||
|
||||
A source-bound current-turn question can bind an eligible Basic player's
|
||||
|
||||
@@ -1,5 +1,13 @@
|
||||
# Rule decision index
|
||||
|
||||
## Truthtrance and reserve shipment sector — 27 October 2026
|
||||
|
||||
An optional exact sector names the same original reserve-shipment event as
|
||||
territory-wide conditions. The actual physical group, destination and payment
|
||||
determine the answer. This is a provisional online application of the FAQ's
|
||||
current-turn question permission, not a separate publisher timing ruling.
|
||||
[Contract](TRUTHTRANCE_TURN_ACTIONS.md#reserve-shipment-sector--27-october-2026).
|
||||
|
||||
## Truthtrance and the upcoming Basic storm dial — 27 October 2026
|
||||
|
||||
A question about an eligible player's future native dial binds their exact
|
||||
|
||||
@@ -1057,3 +1057,26 @@ information about the named value but do not publish a sealed dial receipt.
|
||||
Current facts and other supported whole-action alternatives keep their existing
|
||||
limitations. Advanced later Storm uses its native deck and remains outside this
|
||||
Basic question prototype; full rule, browser and deployed acceptance are open.
|
||||
|
||||
## Reserve shipment sector — 27 October 2026
|
||||
|
||||
**Prototyped / Partial.** The publisher FAQ (November 2020, p. 8) permits
|
||||
current-turn Yes/No questions; this structured exact-sector condition applies
|
||||
the project's provisional online binding convention. A question may specify a
|
||||
printed sector of its destination territory and a physical force minimum, or
|
||||
omit the sector to match the whole territory. Multiple sector and territory
|
||||
clauses refer to one original future reserve shipment. The native dispatcher
|
||||
still decides actual availability, storm, strength, cost and funding.
|
||||
|
||||
The planner considers the actual sectors when quoting a legal route and shares
|
||||
funding and the shipment interval with other accepted answers. Actual delivery
|
||||
records its real destination and sector for sector-aware questions. An older
|
||||
sectorless receipt is never assigned an inferred sector, and a legacy
|
||||
territory-only question keeps its old receipt shape. A No forbids the whole
|
||||
matching condition; Yes and OR retain actual alternative completions. Human
|
||||
controls and minimal legal AI use the native projected action. A genuinely
|
||||
opposing stop may release an impossible answer under existing rules.
|
||||
|
||||
Controlled regressions use genuine Basic setup, physical cards and actual
|
||||
storm-safe printed sectors; broader combinations, Advanced, full rules and
|
||||
deployed acceptance remain open.
|
||||
Reference in new issue
Block a user