Support deferred payments with travel deals
Verify and publish checkpoint container / container (push) Successful in 11m29s
Verify and publish checkpoint container / container (push) Successful in 11m29s
This commit is contained in:
1 parent
9536c77062
commit
5e294215be
16 files changed
+603
-100
No files matched your search
@@ -17,6 +17,16 @@ open mode gates.
|
||||
|
||||
## Current checkpoint and work
|
||||
|
||||
**Public travel with deferred payment — 16 November. Prototyped / Partial.**
|
||||
Two-party and group offers can pair a travel term with one deferred payment;
|
||||
due-now acceptance checks a shared funded route, and participants can complete
|
||||
the payment and travel in either order. Controls, release and scheduled terms
|
||||
are connected. Bid/Revival bot guidance also retains its required bid. Thirty-one
|
||||
related files pass 191 cases, the new authenticated HTTP case passes, and type
|
||||
checking, lint and production build pass. Multiple payments in one offer, wider
|
||||
rules/modules and deployed acceptance remain open.
|
||||
[Scope](PUBLIC_DEALS.md#travel-with-a-deferred-payment--16-november-2026).
|
||||
|
||||
**Basic phase-bid, Revival and Shipment commitments — 16 November. Prototyped /
|
||||
Partial.** The owned-cash witness now composes supported leader and grouped
|
||||
Revival with Shipment; planned returns use the same actual purse and physical
|
||||
|
||||
@@ -1,5 +1,35 @@
|
||||
# Public deal records
|
||||
|
||||
## Travel with a deferred payment — 16 November 2026
|
||||
|
||||
**Prototyped / Partial.** In supported Basic classic tables, a two-party or
|
||||
group agreement can pair one structured travel term with one exact deferred
|
||||
payment between participants. The traveler accepts last. The payment and
|
||||
travel can have different actors or deadlines, and neither transfers spice
|
||||
at acceptance. When due now, a detached native completion checks all the
|
||||
payer's due payments together with their live travel, including a travel term
|
||||
accepted immediately before a separate payment or vice versa. A failed final
|
||||
acceptance leaves the offer and resources intact. Future obligations retain
|
||||
the existing no-reservation policy and become enforceable in their due turn.
|
||||
|
||||
Payments still use the native bribe action and separate Mentat collection;
|
||||
payment and travel can be completed in either order if both remain possible.
|
||||
Unanimous release removes an unpaid payment and its unfinished travel; it does
|
||||
not refund an already settled payment. The terms are a provisional structured
|
||||
online representation of the public agreement rule, not a restriction imposed
|
||||
by the publisher. This supersedes earlier statements below that the two terms
|
||||
could not be combined. Multiple payments in one offer, Advanced, expansion
|
||||
factions, arbitrary prose, wider interactions and deployed acceptance remain
|
||||
open.
|
||||
|
||||
Evidence: [public gameplay](../tests/public-deals-deferred-travel.test.ts),
|
||||
[separate future terms](../tests/public-deals-future-deferred-runtime.test.ts),
|
||||
[deal controls](../tests/public-deals-travel-controls.test.tsx) and the
|
||||
[authenticated boundary](../tests/public-deals-deferred-travel-http.test.ts).
|
||||
Thirty-one related offline files pass 191 cases, and the new HTTP case passes
|
||||
against a local server with a fresh test room. Type checking, lint and the
|
||||
production build pass; build chunk-size warnings remain.
|
||||
|
||||
## Group travel with an immediate payment — 29 October 2026
|
||||
|
||||
**Prototyped / Partial.** A Basic classic group offer of three to six human
|
||||
|
||||
Reference in new issue
Block a user