Support multiple named Ghola commitments
Verify and publish checkpoint container / container (push) Canceled after 0s
Verify and publish checkpoint container / container (push) Canceled after 0s
This commit is contained in:
1 parent
6c1530382d
commit
bdd5aaf18c
8 files changed
+286
-26
No files matched your search
@@ -4,6 +4,35 @@ 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.
|
||||
|
||||
## 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
|
||||
@@ -32,8 +61,8 @@ 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
|
||||
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.
|
||||
|
||||
Reference in new issue
Block a user