Dune/docs/HOMEWORLD_REVIVAL_DEPLOYMENT_RULES.md

# Southern Hemisphere and Tleilax revival deployment

Primary-source audit, 10 September 2026. This is a source and implementation-boundary contract, not a runtime completion claim. The coordinator has already asked about threshold restoration and splitting several revived Fedaykin; those answers remain pending.

## Individual Southern allocation — 27 October 2026

**Prototyped / Partial.** Under the 14 October recommended-option instruction,
new Basic returns of two or three eligible Fedaykin use a visibly provisional
per-star interpretation. The photographed publisher Southern high face uses
plural forces; neither that face nor the supplied revised rules explicitly
settles splitting or a strict partial placement. This policy is not a publisher
clarification or an answer to the earlier user question. The supplied revision,
physical22, delegates Homeworld abilities to their cards; physical32 retains
the Advanced one-Fedaykin revival limit. The original component provenance is
recorded [below](#printed-effects-and-provenance).

Complete the original revival into reserves once, then fix its eligible new
stars and resulting-population entitlement. Choose one through all remaining
stars and a currently legal territory already containing Fremen forces. Finish
that portion's native arrival before offering a fresh portion, which may use
another destination. Leaving the remainder in reserves ends the allocation.
Destinations are quoted against the current board; old reserves, ordinary
forces and a new free allowance cannot join the original batch. No second
revival, payment or shipment/movement allowance is introduced. Restore the
original deferred income once, after every portion and child finishes.

The version2 return retains its immutable original root and grant. Each portion
has its own event, exact starred subset, destination and ordinary arrival
history. Ambassador and Terror consumers bind the current child rather than
the aggregate root. The next choice cannot precede an unfinished arrival.
Public controls show the original total, remaining, placed and kept counts;
all four profiles have the same legal fallback without strategic tuning.
Single-star/Advanced returns, Tleilax's whole free group and existing
unversioned/version1 returns keep their prior procedure. The selected storm/HMS
routes and existing source-specific arrival policies below remain applicable.

Focused evidence paths: [return](../game/homeworld-revival-return.ts),
[destinations](../game/homeworld-revival-destinations.ts),
[controls](../components/homeworld-revival-deployment.tsx),
[native source](../tests/fixture-southern-allocation.ts),
[native cases](../tests/southern-allocation-runtime.test.ts).
Frozen **24 affected files, 256/256**, types/lint/build and seven genuine
native programmes pass. Actual Basic Homeworld setup, a paid Emperor invasion,
real battle/starred casualties and the next Storm earn the original revival.
Runtime includes 21 GameTable SSR renders, 12 button-group SSR renders and
12 actual quantity/destination/reserves callbacks. Source/further counts
(414/20, aggregate across programmes) derive from recorded action arrays.
No played state, Tank, phase or upcoming revival receipt is installed.

Twelve new native cases cover split, partial/whole/declined placement, actual
two-star entitlement, stale/overdraw/other-owner rejection, pending ownership,
one deferred Tleilax payment, Ecaz interruption and four legal profiles.
Seven helper and four control cases cover exact subsets, fixed grants, current
children and callback boundaries. Early feedback repairs new fixture shipment/
leader selection and the one-spice normalized income oracle. Related feedback
updates whole-only expectations and native Advanced source-order drivers.

The existing local server returned HTTP200; no restart was needed. No HTTP/storage boundary,
saved-game/database or deployed operation changes. This is local native/SSR/
callback evidence, not browser hydration, complete modes or final acceptance.
Wider combinations and final rules/recovery/privacy/deployed proof remain open.
Private proof: `/home/quintine/.local/share/dune/checkpoints/20261027-southern-allocation-proof-v2/`;
journeys/HTML: adjacent `20261027-southern-allocation-runtime/run/`.

The dated audit's whole-group boundary below records the earlier common
subset; this explicit provisional policy supersedes it only for fresh Basic
multi-Fedaykin allocation. It does not resolve unrelated pending questions.

## Selected storm and HMS route policy — 25 October 2026

Use the existing out-of-storm destinations and native HMS entry route, under
the 14 October recommended-option authority. The supplied authorized revision,
physical10/logical8 movement rule and physical32/logical30 Fremen B, separates
ordinary storm restrictions from the named **shipment** exception. Southern
**placement** does not inherit that exceptional shipment permission. This is
selected provisional composition for Southern, not a new Southern FAQ.

Physical34/logical32 Ix B restricts non-Ix entry to reaching the pointing
territory and then using Force Movement; HMS itself remains storm- and
worm-protected. Southern placement grants no such route override. Tleilax's
off-planet SEND likewise retains the Ixian direct-shipment restriction. Existing
BG/Terror/Ambassador entry reactions do not grant a shipment or movement route.
An occupied interior does not create a revival destination merely because it is
sheltered. Display the route restriction first, even when the pointing sector
is in storm; do not describe the HMS interior as exposed to that storm.

These choices replace the old waiting-for-ruling labels without opening an
unsupported route, spending another allowance or changing the eligible group.
They do not borrow the source-specific Moritani Cunning HMS exclusion as a
universal user ban. Fresh source review used the supplied44-page PDF visually;
E1/November publisher PDF retrieval returned403, so no fresh publisher
confirmation is claimed. The earlier audit and checkpoints below remain dated
evidence; their unresolved storm/HMS labels are superseded by this policy.

## Revival Terror continuation — 25 October 2026

**Prototyped / Partial.** The adopted physical SEND-entry interpretation now
connects eligible Terror territories to the original revived group. The native
Moritani owner keeps its Reveal/Decline and Enemy of My Enemy choices, all six
printed effects and original card, force, leader and deferred-payment mechanics.
The original revival income waits for the complete entry; no shipment fee,
ordinary shipment allowance or Revival-phase Heighliner income is introduced.
This is the provisional composition selected under the 14 October instruction,
not a publisher FAQ.

A new public source binds the exact original return, destination and physical
group. Terror receipts and ordered overlaps retain it through native discard
continuations. Historical source-absent receipt bytes remain unchanged. When
Terror and Ambassador tokens both qualify, their owners keep the existing
storm-order opportunities; resolving one never overwrites the other's prompt.

A positive Sneak Attack is its own committed reserve entry. It captures the
actual Moritani group and original Terror receipt, then waits for the original
overlap before opening its BG and Ambassador reactions. The original revival
continues after these children. Zero forces produces no new arrival. The new
phase-four Intrusion counter binds that actual Sneak source and retains the
independent Spiritual followup. Other phases retain their existing Spiritual
packet format. New source metadata is historical evidence after a committed
effect, not a fresh shipment permission or a requirement that victims survive.

Evidence paths: [source helper](../game/revival-terror-entry.ts),
[Terror receipt](../game/terror-entry-receipt.ts),
[ordered overlap](../game/arrival-overlap.ts),
[arrival history](../game/homeworld-arrival.ts),
[native source](../tests/fixture-revival-terror.ts),
[printed effects](../tests/revival-terror-runtime.test.ts).
The following BG checkpoint is retained as prior evidence; its Terror fence is
superseded by this continuation. Southern storm, HMS classification, broader
combinations, complete modes and comprehensive assurance remain open.

Frozen **23 files, 310/310**, types/lint/build and six native engine/GameTable
SSR journeys pass on unchanged source. Default Basic71/Advanced73 original
actions earn actual High19/Tanks1 through paid Hagga13 shipment, next-Storm13
loss and real first-Mentat Terror placement, then ordinary free revive1. All
six effects, decline, original Karama versus Enemy of My Enemy and four minimal
policies use native controls. Both storm orders and Sabotage discard ownership
are exercised. Optional native Advanced BG/Ecaz programme146 uses actual independent
three-card/Nexus selection and original50; defaults retain47. Ecaz's legal
Basin9 setup really loses six in the first sweep. Basic Ecaz's actual token
uses Arrakeen10 while Storm11 excludes Carthag11. No source played hand/wallet/
force/phase/Tank/response is installed.

Eight source and ten controlled arrival cases include exact packet/clock/actor,
legacy bytes, Southern support and captured Polar origin. Nine additional
native integration cases check both overlaps, fresh Sabotage discard, Sneak's
original second owner before its own BG/entrant Ambassador and an independent
original Karama versus the Sneak-derived Spiritual packet. The direct cancelled-
alliance preflight now admits its exact revived parent before card cost. A
bounded source review also removes a redundant original-territory fence from
captured Sneak history. Other-phase Spiritual formats remain unchanged.

The first frozen quick check passes; runtime then catches an unsupported fixture
roster. The source now uses actual admitted options instead of bypassing that
start guard. Further fixture feedback corrects Ecaz setup territory/owner and
Basic's in-storm Ambassador target. A private runtime assertion also follows
the native hidden-supply rekey after accepted alliance, rather than requiring
the old token ID. Initial related proof was 224/228; final 310/310 adds the original
alliance files and the actual preflight repair. No rules are relaxed to obtain
a green fixture. Logs/HTML and matching code fingerprint remain private under
`/home/quintine/.local/share/dune/checkpoints/20261025-revival-terror/`.
These are engine/SSR journeys, not DOM callbacks, hydration, browser/mobile or
deployed acceptance. Wider nested combinations, complete modes and final
assurance remain open. No saved-room/D1/server/reset/restart/deployment operation
occurred.

## Revival arrival responses — 25 October 2026

**Prototyped / Partial.** The original positive revived group now opens native
Advanced BG Intrusion at a destination containing BG fighters. The authorized
supplied revision's physical page28 F uses entry, so this real physical arrival
meets its condition. On Tleilax's off-planet Free Revival deployment to Arrakis,
BG additionally receives its ordinary Spiritual Advisor choice. The face says
**send**, not **ship**: classifying that transfer as qualifying off-planet
shipping for this independent BG advantage is an explicit provisional
composition under the 14 October recommended-choice instruction, consistent
with the earlier Moritani Sneak Attack SEND composition. It is not a new
publisher FAQ. Southern's on-planet group earns no Spiritual accompaniment;
a Homeworld destination earns no board-entry response.

The original group is already physically placed. Resolve Intrusion and its
ordinary Karama response, then the eligible Spiritual choice and its independent
whole-packet response, matching and mandatory-alone conversion. Preventing a BG
advantage never reverses the revival, its committed placement or ordinary quota.
The remaining original entry waits for those children and reaches its actual
Ambassador once, without replaying forces. Tleilax's original free-revival bank
income remains held until arrival finishes and settles once; it is not an extra
shipping fee or a second free-revival event. Add no Guild special-stop window,
ordinary shipment/movement use, purchased-rate consumption or Revival-phase
Heighliner income.

Phase-four Spiritual sources name the exact original revival event and current
board destination, or an actual owned Guild Ambassador child of that return.
No unrelated phase-four packet is admitted. Existing source formats and signature
bytes remain unchanged outside the new provenance. The original return waits
for pending Spiritual, queued entry and Ambassador work. An independent BG
Ambassador root carries its actual committed public packet; old Guild suffixes
retain their original parent links. This is continuation support, not a new
power or a second placement. Persistent guides describe the existing group and
independent counter consequences; minimal policies use the same native choices.

The old blanket Spiritual and fighter-Intrusion destination fences are removed.
**Revival entry into an eligible Terror token remains gated** while its original
entry/overlap continuation is connected: existing overlap/discard code assumes
Shipment and Movement. Its classification policy is selected, but that native
consumer is unfinished, not silently certified by this BG checkpoint. Group/
quantity, Southern storm, Hidden Mobile Stronghold and other existing destination
restrictions remain. Comprehensive assurance and complete modes remain open.

Evidence paths: [destination quote](../game/homeworld-revival-destinations.ts),
[Spiritual source](../game/spiritual-advisor.ts),
[automatic conversion](../game/advisor-automatic-flip.ts),
[original arrival](../game/homeworld-arrival.ts),
[native source](../tests/fixture-revival-arrival-reactions.ts),
[native cases](../tests/revival-arrival-reactions-runtime.test.ts),
[source cases](../tests/spiritual-advisor-revival.test.ts) and
[controlled arrival-root cases](../tests/homeworld-revival-spiritual-arrival.test.ts).
This dated section supersedes the older BG classification fences below;
quantity/splitting and other pending source boundaries are not resolved here.

Frozen **19 files, 246/246**, types/lint/build and eight native engine/GameTable
SSR journeys pass. Public Basic68/Advanced71 source actions earn original E1
setup/47 cards, a paid one-counter sand shipment, its real next-Storm13 loss and
High19/Tanks1 before ordinary Free Revival. Resident72 first earns BG's actual
paid Carthag fighter. Native choices cover decline, High Wallach two to Polar,
Advanced accompaniment, Intrusion and independent original Karama against each
BG advantage. Original Tleilax free-revival bank income1 settles once after the
children; expecting unchanged final spice was an incorrect first fixture
assertion, not a new charge. All four minimal policies propose legal actions.

Eight source and eight controlled arrival-root cases supplement those native
programmes. Separate conserved-board cases cover Southern Intrusion cancellation
without Spiritual and Tleilax entry into an actual Fremen Ambassador relocation.
An older scenario expected forbidden accompaniment into retained BG fighters;
it now asserts rejection, legal Polar fallback and mandatory alone conversion.
No illegal BG suffix is retained merely to keep a historical test green.
The original Fremen relocation remains separately exercised. Native combined
Ecaz, visual/browser/deployed and parent hydration are not claimed.

Runtime exposes and repairs the phase5-only Intrusion cancellation preflight;
its new branch validates the original revived arrival before card cost. A
no-followup Southern case also repairs completion immediately after deferred
entry drains, rather than requiring another human action. Bounded review adds
the revival tag to a fresh Basic Guild advisor child. After the cancellation repair, runtime
passes before the related stale assertion fails; final frozen proof includes
all repairs on identical source. Private source-bound logs/HTML:
`/home/quintine/.local/share/dune/checkpoints/20261025-revival-bg-arrival/`.
No saved-room/D1/server/reset/restart/deployment operation occurred. Terror and
other named boundaries, complete modes and final assurance remain open.

## Printed effects and provenance

The high faces were visually reread in the original 3024×4032 component photograph, locally `/tmp/dune-card-economy-homeworlds.jpg`, associated with [BGG image 7767034](https://boardgamegeek.com/image/7767034/dune-ecaz-and-moritani). See the [component audit](HOMEWORLD_COMPONENT_AUDIT.md) for provenance. The photographed publisher components are evidence; community explanations are not substituted for rules.

| Homeworld | Native high threshold | Printed scope, paraphrased |
| --- | --- | --- |
| Southern Hemisphere | 3 | Newly revived starred Fedaykin may immediately join a territory already containing Fremen forces. |
| Tleilax | 9 | On taking Free Revival, its returned forces may go from reserves, without cost, to one territory or Homeworld, observing storm and occupancy restrictions. |

Southern uses plural forces and does not name Free Revival or a phase. Tleilax uses the verb **send**, not **ship**. Earlier local documents calling the latter a shipment use a classification inference; the face alone does not establish that inference.

## Exact returning group

Southern applies to actual starred counters revived by an otherwise supported producer: ordinary revival, Ghola, or an eligible Ambassador effect. It excludes ordinary counters, leaders, preexisting reserves, Face Dancer replacement and returning surviving forces. Preserve the physical starred identity in Basic too. Advanced permits only one Fedaykin revival per turn across producers; Basic does not acquire that Advanced limit. [GF9 E3, p.16](https://www.gf9games.com/dune/wp-content/uploads/EcazMoritani-Rulebook-LOWRES.pdf#page=16), [November FAQ, p.2](https://www.gf9games.com/dune/wp-content/uploads/2020/11/Dune-FAQ-Nov-2020.pdf#page=2).

Tleilax names the ordinary Free Revival source. A paid counter in the same request is excluded. Modifiers to that ordinary free allowance retain its source. E1 distinguishes free revival from Ghola; zero spice alone therefore cannot classify a Ghola or Ambassador return as Free Revival for deployment. This distinction composes the printed sources; no retrieved FAQ directly answers this Homeworld/Ghola interaction. [GF9 E1, p.7](https://www.gf9games.com/dunegame/wp-content/uploads/2020/09/IxianAndTleilaxuRulebook.pdf#page=7). Keep any unresolved Ambassador quota restrictions from its [existing audit](TLEILAXU_AMBASSADOR_RULES.md).

## Population and immediate timing

The base return goes into reserves. E3 maintains high benefits while the minimum native population is present and inactivates them below it. Its nearby immediate-qualification language concerns occupation, not an explicit revival-trigger ordering. [Base, p.9](https://www.gf9games.com/dunegame/wp-content/uploads/Dune-Rulebook.pdf#page=9), [E3, p.9](https://www.gf9games.com/dune/wp-content/uploads/EcazMoritani-Rulebook-LOWRES.pdf#page=9).

Ordinary free-rate pricing remains the pre-return quotation described in [benefit rules](HOMEWORLD_BENEFITS_RULES.md). Eligibility for a newly triggered deployment is a separate question. Depositing the complete revived group and then testing high is a plausible composition, but no inspected source settles the low-to-high boundary. Do not present it as a verified timing rule. Preserve both populations and block the divergent case pending the existing question.

If the player starts high and only the newly returned subset leaves, its native population cannot fall below its pre-return count unless another intervening action changes custody. This supplies an independently usable timing subset. Do not substitute old reserves for the returned group. A pending decision must reserve its exact eligible counters and revalidate intervening custody changes.

Tleilax specifies one destination. Southern does not explicitly settle whether a Basic group containing several stars can split among territories, nor whether repeated placements re-evaluate an entitlement earned by the group. The already-pending question covers that case. Do not resolve it through array iteration order or silently assert that plural wording mandates either one destination or several.

Sending the complete eligible group to one legal destination works under both candidate destination interpretations, so the splitting question does not require declining that common case. Neither face expressly permits an arbitrary strict subset through an up-to quantity. A complete eligible group or decline is the strongest directly supported quantity subset; do not present arbitrary partial deployment as separately verified. For Southern the eligible group means only its newly revived stars; for Tleilax it means only the ordinary free counters, excluding any paid counters returned alongside them. Finish that disposition once instead of repeatedly offering the remainder and thereby silently allowing splitting.

## Destinations and arrival effects

Homeworlds are not territories, and allied Homeworld destinations are forbidden. Southern's territory permission therefore excludes Homeworlds; Tleilax expressly includes them. Neither effect authorizes ignoring other occupancy restrictions. [E3, p.10](https://www.gf9games.com/dune/wp-content/uploads/EcazMoritani-Rulebook-LOWRES.pdf#page=10).

Southern's existing-force requirement is territorial, not a Great Flat distance limit. Its face supplies no express storm permission. The Fremen half-loss permission in the November FAQ is explicitly about Shipment; applying it to revival placement would be an additional interpretation. Fremen reserves are on-planet. Strongholds containing two other factions cannot be entered for any reason. [November FAQ, pp.2,5](https://www.gf9games.com/dune/wp-content/uploads/2020/11/Dune-FAQ-Nov-2020.pdf#page=5).

Use legal out-of-storm sectors for the independently supported Southern subset. Do not label storm placement definitely forbidden or definitely half-loss solely from that subset. Preserve ordinary alliance and protected-location rules; the word territory is not authority to bypass the Hidden Mobile Stronghold's source-specific restrictions.

| Interaction | Source-grounded treatment or remaining boundary |
| --- | --- |
| Guild payment income | The deployment costs zero, so it generates no paid-spice receipt regardless of shipment classification. |
| Ordinary turn usage | This immediate revival consequence does not use or reset the later ordinary shipment/movement allowance. This is timing composition, not a separate FAQ example. |
| Heighliner | The Tech Token operates in Shipment & Movement. Ordinary Revival-phase deployment therefore does not pay it. Do not generalize this conclusion to a future out-of-phase producer without inspecting its source. [E1, p.5](https://www.gf9games.com/dunegame/wp-content/uploads/2020/09/IxianAndTleilaxuRulebook.pdf#page=5). |
| BG accompaniment | Requires an off-planet shipment onto Dune. Southern's on-planet origin does not satisfy it. A Tleilax destination on another Homeworld also does not satisfy onto-Dune. Tleilax deployment onto Arrakis still needs its send/shipment classification settled. [Base, pp.17–18](https://www.gf9games.com/dunegame/wp-content/uploads/Dune-Rulebook.pdf#page=17). |
| BG Intrusion | Its condition names shipping or moving into a territory with fighters. Neither face explicitly classifies its arrival using those terms. Do not automatically force or suppress an Intrusion response at an affected destination. [Base, p.18](https://www.gf9games.com/dunegame/wp-content/uploads/Dune-Rulebook.pdf#page=18). |
| Moritani Terror | The general trigger names movement or shipment. These deployment classifications are not settled by the retrieved sources. No-Field placement's explicit FAQ treatment does not prove all placements trigger Terror. [E3, pp.5,14](https://www.gf9games.com/dune/wp-content/uploads/EcazMoritani-Rulebook-LOWRES.pdf#page=5). |
| Ecaz Ambassador | The printed trigger more broadly names entry into a stronghold. Actual deployment can compose with this entry condition and its ordinary faction, ally and advisor exclusions; this is not a specific revival FAQ answer. [E3, p.7](https://www.gf9games.com/dune/wp-content/uploads/EcazMoritani-Rulebook-LOWRES.pdf#page=7). |
| Karama | The Homeworld effect itself is immune. Independent ordinary advantages retain their own cancellation rules. Do not duplicate the existing unresolved special-Tleilaxu-Karama versus underlying revival question. [E3, p.10](https://www.gf9games.com/dune/wp-content/uploads/EcazMoritani-Rulebook-LOWRES.pdf#page=10). |

Until arrival classification is settled, a legal destination with no relevant unresolved reaction permits useful independent work. At a destination where classification changes a reaction, preserve an explicit gate instead of choosing a reaction policy silently. An off-planet BG accompaniment opportunity can make classification relevant even when BG is absent from the selected territory.

## Implementation handoff and existing questions

Retain a server-owned event receipt containing source kind, player, turn/phase, revived physical normal/starred counts, the actual ordinary free subset, pre/post native counts, remaining eligible counters and the suspended phase continuation. Bind its immutable event fields. A deployment must consume those reserved counters exactly once, and decline must leave them in reserves. Restore cannot recreate an offer from current reserves, current Tanks or a recalculated free rate. Keep projected choices, bots and server validation on the same quote; expose no private card identity merely to identify a Ghola source.

Meaningful regressions include paid/free mixed revival, old reserves excluded, Basic stars versus Advanced shared revival cap, low-to-high refusal pending its ruling, no Homeworld option for Southern, one Tleilax destination, legal storm sectors, current alliance occupancy, reaction-specific gates, unchanged phase usage, decline, JSON continuation and rejected-action immutability. Additional complete-module verification remains required.

Ix's paid-Cyborg bonus still lacks authoritative quota and insufficient-Suboid rulings. Those questions were already asked; see [benefits](HOMEWORLD_BENEFITS_RULES.md) and [invasion audit](HOMEWORLD_INVASION_RULES.md). No new authority found here resolves them. Occupation lifecycle, low-Junction contributor rounding and unrevealed Grumman token removal are separate pending questions and were not repeated.

Only this source document was edited. Fresh publisher-indexed extracts and the physical high faces were inspected; direct E3 PDF opening remained unavailable. No runtime behavior, saved game, reference or implementation checkpoint is certified by this audit.