Dune/docs/TRUTHTRANCE_LEADER_REVIVAL_PROMISES.md

# Truthtrance named leader revival promises

The [grouped follow-up](TRUTHTRANCE_REVIVAL_EXPRESSIONS.md) combines these named
returns and ordinary force minima with whole AND/OR, preserving dynamic choices
and the shared native planner. Scalar questions keep their existing meaning.

## Paid Box selection preserves a Ghola answer — 29 October 2026

**Prototyped / Partial.** Once the owner has paid for a Nullentropy Box search,
a selected recovery must preserve the shared completion of any outstanding
named Ghola Yes. An incompatible choice is rejected before the discard pile is
shuffled; the paid search remains open for a legal selection. A controlled
multi-leader fixture uses the original physical Ghola and Box and checks that
an alternative card is rejected before the actual Ghola replay. Broader
interactions, saved-game assurance and deployed verification remain open.

## Multiple named Ghola answers — 29 October 2026

**Prototyped / Partial.** Multiple
simultaneously outstanding Yes answers may name different leaders when the
shared planner can execute their actual owned Ghola returns with currently
held cards and known, paid Nullentropy Box recovery. Repeated Yes answers for
the same leader can share that one return; different leaders require different
physical plays. Search is bounded by the outstanding names and actual held
Boxes. The owner's guide can offer the next immediately executable Ghola play,
the Box start, and its paid private search choice without revealing a hidden
card to other players.

After a prior return, an owned paid Box search can retain its original decision
and quote the real eligible Ghola choice without charging twice. Forecasting
multiple outstanding returns starting from an already-open paid search remains
unsupported.
A multi-name Yes is not inferred from unknown draws, invented casualties,
foreign consent or hypothetical future preparation. The multi-name planner is
currently limited to already executable owned paths and known recovery; other
future preparation, richer interactions, final saved-game assurance and deployed
acceptance remain open. These are provisional online completion policies, not
a publisher ruling.

The focused multi-name runtime fixture starts from a native Richese/Box game
and retains one physical Ghola. It explicitly stages custody of that card and
the second Truthtrance and stages two dead leaders; it does not claim those
acquisitions or deaths were earned in play. The focused union passes 132 cases; this does not certify complete modes or
deployed behavior.

## Named Ghola leader question — 29 October 2026

**Prototyped / Partial.** A separate provisional
`{kind:'gholaLeader',target,turn,leader}` question asks whether the respondent
will personally return the named leader with an owned Tleilaxu Ghola card after
the answer and before the current turn ends. This is a composition of the
general current-turn Truthtrance authority with the existing Ghola effect,
not a publisher ruling on this exact question. Public leader names may be used
to author the question; the answer, any commitment and its guidance belong to
the respondent's private view.

An actual successful Ghola return of the named leader fulfills Yes. Playing
Ghola to return forces or a different leader, making an ordinary or special
revival, another player's foreign Ghola, a prior play, a pending request or a
prevented return does not. No prohibits the named personal Ghola return during
the relevant remaining turn without prohibiting other legal Ghola choices.
The question grants no card, leader, return allowance or exception to native
card timing, eligibility, custody or physical costs. Existing ordinary
leader-revival questions and Ghola-play questions retain their separate meaning.

A Yes answer must have a real owned completion consistent with existing
obligations; the engine must protect that completion against voluntary actions
and handle actual later prevention without inventing hidden draws, foreign
consent or future casualties. Conflicting promises must not be accepted merely
because each is feasible alone. Exact support for recovery, concurrent promise
families and special interaction profiles remains a matter for the integrated
planner and focused tests. Human guidance and minimal legal bot participation
must use the same authoritative answer and return choices. The prototype uses the shared completion planner, private guidance and minimal bot
actions. The newer multiple-name scope above supersedes the earlier one-target
cutoff. Pending-interaction preflight is conservative. Nine related files pass
128 focused cases, including native Basic and Advanced returns, contradictory
answers and competing ordinary returns. Full interactions, saved-game assurance,
complete modes and deployed behavior remain open.

## Native future-return prototype — 26 October 2026

**Prototyped / Partial.** Registered bare native Basic/Advanced tables support
`{kind:'leaderRevival',target,turn,leader}` in quiet phases0–4 with a remaining
ordinary Revival opportunity. Name an original own leader, Ecaz's shared Duke
where present, or the Advanced Atreides `kwisatz` token. Printed public names
support authoring; private answers and own records/guide stay respondent-only.

Only an actual future personal native leader/KH return after the answer counts.
Direct requests and actually accepted native early negotiations share real
return accounting. A request, quote, unaccepted negotiation, prevented return,
card/special revival or foreign ghola does not fulfill Yes. Prior returns and
the separate force ledger do not count. No prevents that named ordinary return.

## Authority and interpretation

General current-turn Truthtrance authority is recorded in the
[nonbattle audit](TRUTHTRANCE_NONBATTLE_READINESS_20260907.md) and
[force-return contract](TRUTHTRANCE_REVIVAL_PROMISES.md). Supplied Advanced
physical39 was read for this slice. Its Leader Revival passage, physical9/
printed7, retains cohort, one-leader allowance, fighting-strength payment and
faction exceptions. Native rules remain in `game/revival.ts`,
[Ecaz revival](ECAZ_REVIVAL_RULES.md) and
[Advanced opportunity order](ADVANCED_REVIVAL_ORDER.md).

Under standing14October choose-recommended authority, bind the named future
native return until the respondent's actual Revival opportunity closes. Basic
No persists to phase close because readiness may reopen; stamped Advanced No
ends with the native opportunity. Source/interval/owned-completion/release
meaning is provisional software composition, not a dedicated publisher ruling.
Basic keeps its original native protocol.

## Connected behavior

`game/leader-revival-promises.ts` owns canonical claims, required/forbidden
identities, immutable actual-return recording and validation. Same-identity Yes
answers can share one real return; distinct Yes identities need actual native
slots. The question grants no extra allowance. A matching No rejects before a
voluntary native request opens its responses.

The original leader quote and physical/cohort/slot accounting serve actual
returns and private witnesses. One completion planner pays required leaders
and reserves their native slots before aggregate force search. Force and
leader answers share accepted order, with existing unstamped records first.
Voluntary invoices, spending and Finish cannot erase the last completion.
Completed opposing impossibility releases only incompatible Yes in that order.
Original responses and their actual outcomes remain authoritative.

Earlier phases retain current dead/captured/foreign custody and use existing
owned Charity, opening-income and known auction-payment witnesses, with only
the real future normal ledgers reset. No future death, foreign agreement/price,
unknown income or future draw is assumed. Earlier bid/bribe/shipment/movement
funding is retained. Actual accepted personal negotiations count when returned;
an already-priced, not-declined request has an owned acceptance guide. The
planner never invents a future negotiation, foreign agreement or price.
Private witnesses execute no foreign income, skills or continuations. An
actual Tleilaxu self free-return receipt may prepare a needed leader payment;
the real return and its response must complete before the live income exists.

Public-name fields, preview, target-only answers and a persistent own panel
connect to the table. Exact event-bound guides prepare, make a jointly required
force return, return a leader/KH or finish at the actual owned opportunity.
Pending decisions and room controls remain. All four minimal policies use the
same feasible answers/native guide; strategy and calibration stay deferred.

## Evidence and remaining gates

Pure and controlled UI cases plus original battle/death sources are in
`tests/leader-revival-promises.test.ts`,
`tests/truth-leader-revival-controls.test.tsx`,
`tests/fixture-truth-leader-revival.ts` and
`tests/truth-leader-revival-runtime.test.ts`; native shared-purse cases are in
`tests/truth-leader-revival-funding.test.ts`. Ten pure,16 native,six controlled
UI and two native funding cases are part of the frozen **19-file,208/208** union.
`npm run check:quick`, `npm run build` and six native runtime paths pass on the
same unchanged source. The actual GameTable renders23 times and nine real
hook-free guide callbacks submit their original packets.

| Original source | Prefix actions | Further actions | Actual result |
| --- | ---: | ---: | --- |
| Basic H/A/T Ix47 | 102 | 12 | Projectile kills Hidar; future native return costs2, T4→2 |
| Advanced H/A/T Ix47 | 108 | 11 | Same real death/return under actual ordered Revival |
| Basic named No | 102 | 12 | Exact ordinary return rejects; free force/bank1 remains independent, No ends at actual phase close |
| Basic owned income | 102 | 14 | Bribe3 leaves T1; actual free force earns bank1; ordinary leader then costs2, ending T0 |
| Advanced post-Storm | 83 | 33 | Early question remains pending through actual phases and returns the leader at its own opportunity |
| Basic projectile/Tooth | 103 | 15 | Both leaders actually die; A requests, T quotes3, Yes binds, T reprices4, old guide rejects, real acceptance pays4 |

Both original Truths and all47 original cards retain physical inventory.
Only still-unopened original deal/Spice positions and scalar lotteries are
selected. Native sources install no played hand, purse, clock, death, question
or promise. Four minimal profiles submit legal actual returns in both source
modes. Cases also cover prior-return exclusion, Ghola/ordinary separation,
same/conflicting clauses, native ordered waiting, free-income preparation
blocked by Force No, and actual already-priced negotiations for Yes and No.
Controlled projections remain UI evidence, not native acquisition/death/payment.

Feedback repairs voluntary Ghola evasion: its physical return cannot erase the
last ordinary-return Yes by opening a later income response owned elsewhere.
The funding assertion retains a turn-wide bribe No after Revival. Optional
negotiation-record reads are guarded. A transient direct quick-check process
ended143; the final source-bound v4 types/lint and all remaining steps completed
successfully. Earlier failed proof directories remain diagnostic data.

Frozen v4 report/verified manifest:
`/home/quintine/.local/share/dune/checkpoints/20261026-truth-leader-revival-proof-v4/`.
Exact commands/logs are in `report.json`; journeys, SSR HTML and native harness
are in adjacent `20261026-truth-leader-revival-runtime/`. Final evidence prose
is a separately recorded three-document overlay. SSR/callbacks are local
engine/control evidence, not browser clicks.

The native source targets Tleilaxu's own early return, not a five-disc cohort
opening. Dedicated original normal-cohort, Auditor, Duke and KH commitment
journeys, native opposing-prevention/release histories, wider negotiated/card
preparation, optional modules and grouped revival
expressions remain due. No complete faction/mode, all combinations, browser/
mobile/deployed or final assurance is certified. No saved-game/database/server,
reset/restart/deployment operation is performed; no start/publication gate opens.