Files
Dune/docs/ADVANCED_REVIVAL_ORDER.md
T

5.1 KiB

Advanced Revival player order

26 October 2026. Prototyped / Partial. This is one core source cutover, not complete Advanced or optional-module certification.

Source and interpretation

The user-authorized UNOFFICIAL_Revised_Dune_Rulebook_v.2.3_web.pdf, physical9/printed7, expressly starts Force Revival with the First Player and proceeds counterclockwise. It is the supplied unofficial Advanced authority bound by the source amendment, not a newly located publisher ruling. Reproduce the bounded read with:

pdftotext -f 9 -l 9 -layout UNOFFICIAL_Revised_Dune_Rulebook_v.2.3_web.pdf -

The adjacent Leader Revival paragraph says leader returns are in addition to force revival. This preview explicitly composes native force and leader/KH/ foreign-Ghola choices into one participant opportunity. The source does not independently print a separate leader queue. Basic's publisher text supplies no matching Force Revival sequence, so Basic keeps concurrent readiness.

Connected behavior

  • A new Advanced Revival opens a version1 public order using the actual First Player order already determined by Storm. Only its first remaining participant can make ordinary self returns, negotiate/request/accept a native leader return, or explicitly finish. Accepted native requests mark that opportunity started; subsequent requests retain it.
  • Tleilaxu may quote or decline the current request and offer native limit/ discount grants outside its own opportunity. Fremen grants remain separate. Emperor can pay for extra allied forces during the beneficiary's current opportunity. The response remains owned by its original authorized actor.
  • A committed return and all required payment, income, card, placement and arrival decisions finish before ordinary Finish. Answering a response does not advance or consume the responder's own opportunity.
  • Finish withdraws any outstanding unaccepted own leader negotiation, adds exactly that participant to the completed prefix and advances once. Completed native turns cannot reopen through another return, Finish or an early Truthtrance shipment/movement commitment.
  • Card effects, Nexus and special Karama retain their separate existing timing. The guard targets native self actions rather than all actions in the phase. Private future-shipment witnesses may still consider a later owned Revival preparation; their policy waits for the real opportunity before proposing it.
  • Closing decisions retain the completed frame until the phase actually ends. The next phase removes it. A phase already opened without the frame retains its legacy readiness semantics; projection never manufactures a queue midway.

game/revival-order.ts owns the immutable order calculation and validation; the engine owns phase lifecycle, transactions and projection. Controls use components/revival-turn.tsx, the existing native return buttons and commerce controls. Minimal AI follows the same projected availability. No action kind, database migration or saved-game conversion is added.

Evidence and remaining scope

Focused cases are tests/revival-order.test.ts, tests/advanced-revival-order-engine.test.ts and tests/advanced-revival-order-controls.test.tsx. Their native source is tests/fixture-advanced-revival-order.ts: public E/A/T plus the original Ix deck, actual setup and first Revival; the return variant additionally earns Tanks through paid shipment and a later actual Storm. Controlled old-envelope and prior leader-death supplements are labelled separately.

Frozen proof passes 12 files,105/105, types/lint/build and nine runtime/ control paths with13 GameTable SSR renders. Seven paths are native: first ordered Revival (41 source actions), played normal1 shipment for2 and actual later card-Storm casualty/free revival (99), Basic readiness (38), and four minimal policies with5 further actions each. Native47 Treachery identities, the returned ordinary counter and separate Tleilaxu bank1 remain. The other two paths are explicitly controlled old-envelope and leader-death supplements.

Source-driver readiness and a stale Hajr test now use actual current Revival and immediate post-movement controls. Feedback also removes false later-Storm dials and mandatory uncontested-income acknowledgements, uses semantic status markup and narrows an optional test ledger. Application source is unchanged between successful proof-v5 tests/types/lint/build and proof-v6 runtime; only the private SSR loader needed its existing Vinext aliases/CSS mapping. Combined report and source manifest are in /home/quintine/.local/share/dune/checkpoints/20261026-advanced-revival-order-proof-v6/; journeys/HTML are adjacent 20261026-advanced-revival-order-runtime/. This is SSR/selected-props callback evidence. No saved-room/D1/server, reset, restart, deployment or recovery operation occurs.

Sapho's new Revival adapter, broader combinations, full rules review, save/recovery/privacy/custody assurance, browser/mobile and exact-revision deployed acceptance remain due. Existing games, the local PDF and hosting configuration are preserved. No mode/publication gate opens.