Prototype named Ghola leader Truthtrance promises

docs/CURRENT_STATUS.md

@@ -17,6 +17,16 @@ open mode gates.
 
 ## Current checkpoint and work
 
+**Truthtrance named Ghola leader — 29 October. Prototyped / Partial.** A
+provisional question binds an actual named leader return with Ghola, distinct
+from ordinary revival or returning forces. Private human and bot guidance uses
+the same native action; the shared planner checks earlier commitments and
+protects the remaining card and leader. One distinct outstanding Yes target is
+supported; complex pending interactions are conservatively guarded. Nine
+related files pass 128 cases. Full interactions, saved-game assurance and
+deployed verification remain open.
+[Contract](TRUTHTRANCE_LEADER_REVIVAL_PROMISES.md#named-ghola-leader-question--29-october-2026).
+
 **Distrans/Semuta special-auction continuation — 29 October. Prototyped /
 Partial.** The Semuta claim/pass following a Distrans transfer can now suspend
 and resume a supported Once Around, Silent or normal Black Market lot, retaining

docs/TRUTHTRANCE_LEADER_REVIVAL_PROMISES.md

@@ -4,6 +4,40 @@ 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.
 
+## 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. It supports one distinct outstanding Yes target; more than one remains
+guarded. 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