Files
Dune/docs/TRUTHTRANCE_ALLY_FUNDING.md
T
Quintine b3843bf18e
Verify and publish checkpoint container / container (push) Successful in 11m4s
Support Advanced Truthtrance ally funding
2026-11-16 17:36:52 +11:00

64 lines
4.0 KiB
Markdown

# Truthtrance ally-funding questions
## Advanced current-phase prototype — 16 November 2026
**Prototyped / Partial.** The existing structured question is available in
supported quiet Advanced Bidding and Shipment and Movement as well as Basic.
It retains the native funding action, winning-bid lock and Advanced payment
routing. A respondent's pending unpaid shipment or Guild transport reserves its
approved personal cost when testing whether an unfulfilled Yes can still be
kept; that projection does not move or charge spice. A No permits inaction even
when an existing bid locks a higher pledge and rejects a later qualifying update.
The user-authorized revised rulebook physical p. 39 / printed p. 37 supplies
Truthtrance's question and current-turn obligation; physical p. 15 / printed
p. 13 describes allied Bidding and shipment payments. Applying that permission
to this update and its current-phase deadline remains the provisional online
interpretation described below, not an added publisher ruling. Module and
combined-question guards remain; complete Advanced games and deployed
acceptance are not established.
The [Advanced runtime journeys](../tests/truth-pledge-advanced-runtime.test.ts)
use public setup, a real worm, alliance, native actions and legal bots; the
[rendered controls](../tests/truth-pledge-advanced-controls.test.tsx) show
phase-specific private answer availability. [Guild transport journeys](../tests/truth-pledge-advanced-guild-transport.test.ts)
exercise a real cross-shipment and pending permission. Their fixtures select
unopened deals and Spice order, and stage a Karama for the transport response.
Broader faction combinations and save/restore assurance remain due.
## Current-phase prototype — 29 October 2026
**Prototyped / Partial.** In a supported quiet Basic Bidding or Shipment and
Movement phase, a player may ask whether another player will submit an
ally-funding update at or above a chosen amount to their current mutual ally
before that phase ends. The existing publisher FAQ permits game-related yes/no
questions and current-turn promises; applying it to this particular action and
its phase deadline is a provisional online interpretation, not a printed example.
See the [source audit](TRUTHTRANCE_NONBATTLE_READINESS_20260907.md).
A Yes requires an accepted future native `pledgeAid` update while possible.
An earlier pledge alone does not fulfill it, although explicitly submitting the
same total afterward does. A No prohibits a future update reaching the threshold.
The original escrow amount, locked commitments, available spice and repayment at
phase end use the ordinary native funding rules. Setting funds aside does not
pay another player or promise that the ally will spend them. Only the target
receives its private feasible answers and optional exact-action guide.
A voluntary action by the respondent may not make a still-possible Yes
impossible. A different player's action, a natural phase change or loss of the
reciprocal alliance can release an impossible Yes; No expires with the phase or
alliance. Pre-consented immediate deal payments are attributed to the actual
final accepter when determining whether a debit was voluntary. A definite
ally-funding question occupies this phase's single question slot; other future-
action questions remain unavailable for the rest of the phase. A prior definite
future-action question in the turn also excludes a new funding question. These
fences use public question history, avoiding disclosure of private fulfillment
or mixed-question residuals. They avoid inventing joint funding or future unlocked
escrow. At this earlier checkpoint, Advanced remained open; the section above
records the later extension. Other modules, combined questions and
full-game/deployed acceptance remain open.
The [helper](../game/pledge-promises.ts), [native runtime journeys](../tests/truth-pledge-runtime.test.ts)
and [controls](../components/pledge-claim-fields.tsx) record the physical and
interactive scope. Existing saved games gain no retroactive promises.