Prototype Truthtrance ally funding commitments

docs/CURRENT_STATUS.md

@@ -17,6 +17,16 @@ open mode gates.
 
 ## Current checkpoint and work
 
+**Truthtrance ally funding — 29 October. Prototyped / Partial.**
+Supported quiet Basic Bidding and Shipment/Movement questions can bind a future
+funding update to the respondent's current mutual ally. Existing escrow alone
+does not count; a repeated total can. Native funding and private wallet rules
+remain, with public-history fences around other future questions. Forty-nine
+related cases, quick type/lint checks and the production build pass, including
+actual escrow, forced deal payment, both phases, legal bots and observer
+comparison. Other modules, joint commitments and deployed acceptance remain open.
+[Scope](TRUTHTRANCE_ALLY_FUNDING.md#current-phase-prototype--29-october-2026).
+
 **Gitea marker-transfer failure — 29 October. Partial.** Run #82 failed
 because its marker-transfer fixture attempted a second all-reserve Caladan
 evacuation after the marker had arrived: eight forces cost more than the

docs/RULE_DECISIONS.md

@@ -1,5 +1,15 @@
 # Rule decision index
 
+## Truthtrance ally-funding updates — 29 October 2026
+
+The first Basic current-phase ally-funding question counts a future accepted
+funding update, not earlier escrow or the ally's eventual expenditure. The
+publisher FAQ permits game-related questions and current-turn promises but does
+not prescribe this online question or deadline. The phase-bound procedure and
+public-history question boundary are provisional.
+[Scope](TRUTHTRANCE_ALLY_FUNDING.md#current-phase-prototype--29-october-2026).
+
+
 ## Sapho at a shared arrival — 29 October 2026
 
 The provisional Basic overlap procedure offers Ecaz and Moritani a public

docs/TRUTHTRANCE_ALLY_FUNDING.md

@@ -0,0 +1,36 @@
+# Truthtrance ally-funding questions
+
+## 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. Other modules,
+Advanced, 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.