Dune/docs/TRUTHTRANCE_REVIVAL_PROMISES.md

Truthtrance native force-revival promises

The grouped follow-up adds whole AND/OR questions across future ordinary force minima and named native leader returns. It retains dynamic alternatives and the shared native purse/allowance rather than changing this scalar question's meaning. Broader families remain due.

The named-leader follow-up adds a separate future personal native leader/KH return question sharing the ordinary force planner's purse and native slots. Leaders still do not count toward the force-counter question below; broader special/card revival remains unfinished.

Earlier-turn follow-up — 26 October 2026

Prototyped / Partial. The same ordinary-return question now works in quiet phases0–4 while this turn's native Revival opportunity remains. The general current-turn authority below still applies. This extends the explicit future interval; it does not promise casualties or resources from unknown future play. Current physical Tanks and typed current-turn elite usage are retained. The future normal/free revival ledgers reset exactly as at real phase4 entry.

The guide and answer search reuse the same owned Charity/opening-income and auction-liability preparation used by shipment. Actual Charity, an owned CHOAM opening's allowed fixed outcome, current winning invoices, paid invoices and unused outgoing pledge refunds stay distinct. A physical held Karama used for an owned ordinary invoice is removed from that witness before any later quote. Incoming allied bidding escrow does not become promised revival funding. The shared witness conservatively requires current cash for an unpaid invoice before adding refundable outgoing aid; a pre-invoice withdrawal that could retain a Karama instead of spending it remains an uncovered preparation route. It is not certified by a different optional-module fixture. No unknown draw, foreign gift or future rival payment/casualty is invented.

Earlier answers remain visible through phase progression. The guide waits in Storm/Spice and for foreign actors; in Charity it can offer actual Charity or Ready, in Bidding an owned ordinary/native pass, Silent zero or actual ordinary payment choice, then in Revival its actual ordinary return/Finish. An existing binding bid Yes retains its separate real bid guide. The payload carries the current phase and original event; stale/foreign or modified guided packets reject. Manual packets keep their native shape. Normal Yes/No progress still records only actual ordinary returns and expires at the original opportunity boundary.

A voluntary pass of needed Charity, unfunded bid, bribe or other spending cannot evade Yes. Completed opposing outcomes finish before impossible answers release. Basic No remains until phase close; Advanced retains the stamped current actor. Optional modules, grouped expressions and special/card revival claims remain required; no start, complete-mode or publication gate opens. Wider preservation, privacy/custody, browser and deployed acceptance remain due after all rules.

The new original-source/runtime and early-control cases live in tests/fixture-truth-revival-early.ts, tests/truth-revival-early-runtime.test.ts and tests/truth-revival-early-controls.test.tsx. Native Richese zero/pass controls have controlled projection evidence; a dedicated original Richese revival journey remains due. Frozen proof passes 17files/165cases, npm run check:quick and npm run build, with six native paths,47 GameTable SSR renders and20 actual hook-free callbacks. Original Basic41/Advanced42 post-Storm prefixes add21/24 steps through actual phases and return3 for1free+4paid. Poor Basic48/Advanced52 sources really bribe4 away, then16 steps earn Charity2 and return2 for2. Four minimal policies per poor source submit a legal Charity action. Progress remains0 through preparation. A66-action genuine turn3 Storm/prior-return1 source adds26 actions through the actual reset and returns2 for2. An original dealt-Karama59-action source adds17: actual bid5/payment guide, one spent Karama, 4 retained and ordinary return3/payment4. All33 original cards remain. Fourteen native/seven early-control cases retain No, native later prevention, stale phase/actor rejection and bid/revival funding in both answer orders.

Report/manifest: /home/quintine/.local/share/dune/checkpoints/20261026-truth-revival-early-proof-v1/; journeys/HTML: adjacent 20261026-truth-revival-early-runtime/. No played hand, force/Tanks, purse, clock or promise is installed in native sources. No saved-room/D1/server/reset/restart/deployment or assurance campaign. SSR/callbacks do not certify DOM/hydration, browser/mobile/deployed or complete rules/combinations.

The following section records the preceding current-phase checkpoint; its phase4-only and earlier-phase absence statements are superseded by this section.

Current-phase prototype — 26 October 2026

Prototyped / Partial. A structured question binds cumulative future ordinary force returns in the current Revival phase, for registered bare native Basic and Advanced tables. Choose total, normal or elite physical counters and a minimum from1 to20. This adds no game-start permission. Optional modules, earlier-phase questions, grouped revival expressions and special/card revival claims remain required work.

Authority and selected interpretation

The November2020 FAQ p8 supplies general current-turn question/compliance/impossibility authority; its previously checked indexed text is recorded in the ordinary-bid contract. A direct fetch during this slice returned403, so it supplies no newly checked dedicated revival ruling. The user-authorized Advanced source, physical39 replacement Truthtrance text, also requires compliance during the current turn and permits later impossibility release. That local passage was read for this slice. Original native revival quotes and Advanced turn order remain authoritative.

Under standing14October choose-recommended authority, select an explicit cumulative future ordinary-return question. Count completed returns after each definite answer. Splitting a return does not avoid No. Each elite is one physical counter; normal means amount minus elites. Already completed returns, leaders, Ghola, Emperor-funded extras and other special returns are excluded because the question specifically names ordinary force revival. Actual native requests, responses, quotes, force transfers and payments remain unchanged.

The phase interval/counting and accepted-order impossibility policy are provisional software compositions, not a dedicated publisher clarification. Waiting or current participants with a remaining opportunity can answer. Basic No persists through phase close because readiness can reopen. An ordered Advanced participant's No finishes when its native opportunity closes. An unmet Yes prevents voluntary Finish Revival and spending or requests that would remove the remaining completion. Completed opposing consequences can release only impossible Yes answers, retaining No and feasible answers in accepted order. A declaration alone never fulfills a promised return.

Connected behavior

game/revival-promises.ts owns bounded canonical claims, typed physical counting, immutable cumulative progress and joint Yes/No checks. The packet is {kind:'revival',target,turn,counter,minimum} inside the original truthAsk. Normal declaration, priority, answer, physical discard and continuation remain. Each accepted answer has a distinct original event and begins at progress0. Only the respondent receives feasible answer choices and its own promises/guide. Public question and answer history remains public.

The original native force-request quote is shared with a bounded guide search. It retains real typed Tanks, remaining normal/free/elite allowances, actual prices and Ixian free-Cyborg allocation. No unknown gift, future draw or foreign choice supplies resources. Earlier shipment/movement obligations constrain the quoted final return. The guide sends the original revive or ready packet with its own event and waits for actual native turn ownership. Manual requests retain their original shape. Stale guided events reject.

The question selector, validated physical-counter fields, public preview, target-only answer buttons and persistent promise panel are connected. The panel shows progress, fulfillment and release; it does not time out. All four existing minimal AI profiles use the same projected answer and native guide. Full AI strategy/calibration remains deferred.

Evidence and remaining gates

Focused pure, original-deal/death runtime and control evidence is recorded in tests/revival-promises.test.ts, tests/fixture-truth-revival.ts, tests/truth-revival-runtime.test.ts and tests/truth-revival-controls.test.tsx. Frozen v2 proof passes22files/288cases, npm run check:quick and npm run build. Five native engine/GameTable SSR paths render20 tables and exercise five actual hook-free guide callbacks. Original H/A/E Basic53/Advanced58-action sources actually ship3 for6, lose3 to the next Storm and reach turn2 Revival with4spice. Another9/8 actions bind/return3 with1free and4paid; Advanced returns one actual Sardaukar counter. All four minimal policies per source submit a legal return. An8-action Advanced No2 path returns1 and finishes below its threshold.

Original native Tleilaxu/Ix47 sources use143 actions;19 allowed or15 stopped actions retain pending progress0, then either real return3/payment4 or actual opposing special-Karama prevention/release with no return/payment. Original33/47 cards remain. Seventeen native,10pure,6control and2funding cases cover actual return/typed/split/prior semantics, two original Truth copies, Ghola exclusions, Basic post-Ready No, waiting ownership, stale callbacks and shipment funding in both answer orders. One observed older Nexus Fremen test now follows real ordered readiness rather than taking a native return out of turn.

Report/manifest: /home/quintine/.local/share/dune/checkpoints/20261026-truth-revival-proof-v2/; journeys/HTML: adjacent 20261026-truth-revival-runtime/. The final documentation overlay corrects one rules-reference related-topic anchor and records this evidence; the exact anchor replacement is asserted.

No complete faction/mode, all combinations, recovery/privacy/custody, browser/mobile or deployed acceptance is certified. No saved game, database, server or deployment is changed by this prototype.