Support multiple travel terms in public deals
Verify and publish checkpoint container / container (push) Canceled after 0s

This commit is contained in:
Quintine committed 2026-11-16 15:19:10 +11:00
1 parent 13c337a24a
commit d7d0f89625
13 files changed
+790 -51

No files matched your search

+24
View File
@@ -1,5 +1,29 @@
# Public deal records
## Multiple travel terms — 16 November 2026
**Prototyped / Partial.** A supported Basic classic deal may include up to
twelve additional shipment or ground-movement terms, each with its own named
participant, action and current or future turn. In a group offer, invited
participants without travel terms consent first; invited travelers can then
consent in any order. The proposer consents by making the offer. All parties
must agree before any term binds or immediate payment settles. Single-travel
deals keep their existing consent order and saved representation.
Current-turn terms use native travel checks and share the traveler's real
forces and spice with their due payments. Conflicting future terms are rejected;
future travel reserves no current resources. Each additional term has its own
status and commitment, and mutual release cancels every unfinished term.
The term limit and online consent order are provisional implementation choices.
[Model](../tests/public-deals-additional-travel-model.test.ts),
[gameplay](../tests/public-deals-multiple-travel.test.ts),
[receipt and status](../tests/public-deals-multiple-travel-integrity.test.ts),
[controls](../tests/public-deals-multiple-travel-controls.test.tsx) and an
[authenticated room case](../tests/public-deals-multiple-travel-http.test.ts)
cover the connected prototype. Wider rules combinations, complete games and
deployed acceptance remain open.
## Proposer travel — 16 November 2026
**Prototyped / Partial.** A proposer can include their own shipment or ground