Dune/docs/ECAZ_OCCUPY_RULES.md

Ecaz Occupy: Advanced source and historical conflict

Historical primary-source audit, 2026-09-07, corrected after independent verification. The old publisher/designer casualty-rounding conflict remains unresolved as a publisher correction and for Basic. Its earlier false attribution to Jack Reda is still withdrawn. The later user-authorized Advanced source below selects explicit Advanced arithmetic; it does not retroactively certify that attribution.

Authorized Advanced cutover — 2 October 2026

The user authorized the root UNOFFICIAL_Revised_Dune_Rulebook_v.2.3_web.pdf as Advanced source of truth on1 October, including its identified unofficial rulings. Exact revision/SHA and metadata2.3/editorial2.2 are bound by the source amendment. Its physical p32 / logical p30 Occupy B explicitly supplies:

Advanced mandatory Ecaz dial contribution = ceil(E / 2), fully supported
Advanced ordinary-win Ecaz survivors = floor(E / 2)
Advanced ordinary-win Ecaz losses = ceil(E / 2), separately from ally dial losses

Ecaz chooses the lead faction; that faction supplies its actual leader/cards/ plan and spice, while the active variable dial always uses Ecaz's ally's force pool plus the fixed Ecaz contribution, regardless of lead. Physical p19 / logical p17 Ecaz Karama row explicitly changes a prevented Occupy to the SELECTED LEAD'S OWN force pool, with its other ally contributing zero. Keep the selected lead and recompute legality before plans; do not silently inherit the ally's pool when Ecaz leads.

Storm Obstruction (physical p6) and Battle Determination (physical p11) forbid battle if any participating forces are in storm or separated by it. Advanced eligibility therefore checks the whole participating territory armies, including both coexisting allies; it does not invent component-only battle plans or casualties. The canonical board quote retains actual co-side membership when one seat represents the coalition, so an unlocked BG advisor may still voluntarily become a fighter through its native pre-movement opportunity.

This is an authorized Advanced software/source cutover, not a new GF9/ designer erratum or a Basic ruling. Basic's earlier conflict stays separate. The specific user Ecaz-only Duke revival/Ghola decision remains higher-priority than the contrary revival exception printed on that sheet.

Advanced combined-army implementation is Partial / Development Verified: native selection, owner-labelled force/support/loss settlement, printed/BG prevention, human controls and all four minimal legal policies. Ordinary canceled-win non-dialed ally retention and canceled-defeat whole-side destruction compose the base same-side outcome, not a newly located special casualty FAQ. Exotic/optional combinations remain explicit. Source/controls/rule runtime are developed now; comprehensive save/privacy/custody assurance follows all rules under the2 October priority.

Bounded native rule and control proof

The fresh local ecaz-occupy profile admits Ecaz/classic/optional Moritani, 2..6-seat Advanced, ordinary33 Treachery Cards and the E3 faction setup alone. It does not select the independent three-card variant, other overlays, public expansion starts or an existing-game retrofit.

Seven actual native-program cases exercise E1/E5 free fixed contribution, both plan/payer leads, native Fremen/Fedaykin and Emperor/Sardaukar, and both canceled lead-own branches through original Collection continuation. Exact odd/even, storm-relative order, traitor, mutual-traitor, explosion, printed/ BG Karama and next-turn cases have meaningful rule regressions. A reproduced storm-isolated joint battle now has no offer; clear whole armies retain one offer and their actual co-side membership. The existing voluntary BG advisor offer is preserved, not re-pinned to absence. Final scoped reviews find no defect.

Original CLI/human390px Q5Z2WH8X v22 chose Ecaz lead and total9: mandatory Ecaz3 plus free Fremen/Fedaykin6. Native resolution left Ecaz2, Fremen0, Ecaz spice unchanged5 and original Collection. LZHMY454 v14 used real printed Karama after Ecaz lead, recomputed minimum0/own pool3, sealed dial1/support1, and resolved with Ecaz2/Guild4, one actual Ecaz support debit and original Collection. All four policies actually seal native legal plans for either lead, active or canceled.

The coherent affected rule/guide batch passes 173/173. Current-source five unstaged2..6 games complete with2,123 accepted actions, no rejections and54JSON continuations, sourceUnchanged:true. No game sample triggers a combined lead choice: profile continuation is observed there, while the native cases and human rooms establish the actual combined rule path.

Provenance and attribution correction

Source	Observed wording or correction	Authority and conclusion
GF9 E3 rulebook, p.8	Contribution rounds upward; survivors after a win round downward.	General printed rule, supporting ceil contribution/loss and floor survivors.
Same publisher PDF, indexed p.15	Five contribute two; two die and three remain.	Contradicts the general paragraph. A current publisher URL does not prove every page includes later revisions.
Publisher-authored English mirror, p.15, extracted in /tmp/dune-rules/ecaz-audit.txt:686	Five contribute three, but two still die and three remain.	Contribution agrees with p.8; casualty sentence still conflicts.
Rulebook file submitted by Jack Reda / The Warp	File description mentions numerical corrections.	Supports the existence of a revised file, but the description alone does not identify the casualty correction or establish corrected contents.
Jack Reda, 26 August 2023, on that file page	Explains face-up Ambassador placement and face-down Terror placement.	Does not correct Occupy casualties.
Jeff C / @brigade, 28 November 2023, on that file page	Reports remaining number errors and proposes three of five Ecaz forces die, with two surviving.	Community interpretation, not publisher or designer erratum. It cannot resolve this task's source conflict.

The exact fresh query site:boardgamegeek.com/filepage/263742 "First Q&A" returned the full comment boundaries. An earlier broader result had omitted the intervening Jeff C author/date block, causing the false attribution. Direct BGG opening returned 403. The complete indexed result takes precedence over that incomplete excerpt. Do not cite Jeff C's sentence as a Reda ruling or infer author approval from his hosting the file.

For participating Ecaz force count E, the p.8 reading, not an adjudicated correction, is:

Ecaz contribution = ceil(E / 2), fully supported without spice
Ecaz losses on ordinary allied win = ceil(E / 2)
Ecaz survivors on ordinary allied win = floor(E / 2)

The historical publisher/mirror example still conflicts for E=5, and the earlier audits correctly record that publisher gap. Basic still needs a supported interpretation. Advanced now uses the separately user-authorized source cutover above: its explicit ceil contribution and floor survivors select the arithmetic without claiming a designer correction. Fixed Ecaz losses stay independent of the ally's variable dial losses.

Occupation, controller and battle order

Ecaz and its current ally form one occupation side and may share a territory. Their actual counters retain separate ownership. This allows Ecaz to enter a stronghold already holding its ally and an enemy; it does not allow a third unrelated occupation side. Storm restrictions still apply. Homeworlds are expressly excluded because they are not territories. Existing discovery locations and the mobile stronghold require their own admission rules; Occupy does not itself create permission to ship directly into the mobile stronghold. E3 pp.8,10

Jack Reda independently confirms the stronghold exception and explains the two meanings of aggressor in Understanding Ecaz Occupy, 16 October 2023: ordinary storm order still determines who selects battles; the faction ultimately fighting matters for tie priority. His answer also confirms that selecting Ecaz does not exchange the roles of the two force pools. BG advisors need not flip and do not participate in Occupy combat while they remain advisors.

Implementation must therefore distinguish:

• Battle-order actor: determined by the normal battle sequence before Ecaz's selection.
• Selected battling faction: Ecaz chooses this after battle order is determined. It supplies its own permitted leader, hand and Battle Plan; it is not permission to browse or play the ally's hand.
• Dialed force owner: always Ecaz's ally while Occupy operates.
• Fixed-contribution owner: always Ecaz, with the printed half-force contribution and separately attributed casualties.

Do not represent these as one interchangeable attacker identifier. In a storm order ally → opponent → Ecaz, selecting Ecaz must not silently inherit the ally's tie priority merely because the ally selected this battle. The precise API should retain the battle-order actor and derive the selected combatant's ordinary tie relation separately. This follows the designer's distinction; no Sapho or Stronghold-card exception is inferred from it.

Battle calculation, support and losses

The ally's chosen dial uses its normal force rules; the Ecaz increment costs no support spice in Advanced play. The E3 p.15 Fremen FAQ confirms Fedaykin can be dialed and Fremen forces retain free full strength in this co-occupied battle. Its answer to the first of two questions is not a numerical one-Fedaykin limit. Preserve physical force types and actual force ownership when computing support and casualty alternatives. E3 pp.8,15

For a normal win, settle the dialed ally's legal losses under Basic or Advanced rules, then the independent Ecaz loss under the explicitly selected rounding rule. For a normal loss, both participating allied force pools lose their forces: retaining Ecaz's fixed survivors is conditional on winning, not a guaranteed retreat. BG advisors remain outside these pools. A lasgun/shield explosion destroys all affected territory forces under its general rule; neither half-rounding nor the unchosen-faction label makes a safe army. Base pp.10–11,13,22

The chosen faction owns the plan and is the ordinary plan-payment actor under base p.13. Apply only established funding permissions, such as CHOAM's battle aid; shared occupation does not merge spice balances or grant arbitrary allied funding. The fixed Ecaz increment is not an amount of spice secretly paid by Ecaz and must not create CHOAM payment income. Preserve normal force-owner properties, including the explicitly confirmed Fremen support exemption. This payment composition is inferred from the ordinary plan rule and Ecaz's explicit selection, rather than a retrieved worked payer example.

General battle effects still need their own scoped application. A traitor's ordinary winner-loss exception, defeated-side destruction, leader deaths, and card ownership must be considered across the actual allied side instead of processing Ecaz as an unrelated third army. Neither the conflicting example nor the community correction is an explicit ruling on every traitor, Face Dancer, Stone Burner, Suboid exchange, Auditor, capture or Stronghold-card combination. These integration checks are separate from the still-open rounding conflict.

E3 p.16 specifically says that Harass & Withdraw returns the card player's undialed forces, while the ally's forces follow their normal treatment. Therefore a side-wide indiscriminate retreat is incorrect. Preserve owner-labelled force pools before adding this card. E3 p.16

Collection, control and victory

Desert collection is a shared allocation: the allies may agree on the split; absent agreement it is as equal as possible with the odd spice going to Ecaz's ally. Determine the actual collectible amount once, respecting force availability and collection rate, then allocate it. Do not pay the entire spice deposit separately to both factions. The p.15 FAQ also confirms that co-occupation in Arrakeen gives both factions ornithopters and collection rate three. E3 pp.8,15

The Advanced Collection advantage is separate: in co-occupied Arrakeen and Carthag each ally receives two bank spice; in co-occupied Tuek's Sietch each receives one. It applies at Spice Collection, and does not multiply desert spice or grant Basic stronghold income. E3 p.8, base p.13

At turn end a co-occupied stronghold counts once for the alliance and Ecaz controls it. Three strongholds suffice for their allied victory only when both factions co-occupy all three; otherwise ordinary allied victory conditions still matter. A two-and-one distribution is not three co-occupied strongholds. Advisors cannot manufacture a second fighting occupier. The p.15 FAQ forbids combining split ownership of the three Tech Tokens into an extra stronghold and confirms Ecaz/Fremen co-occupation in Sietch Tabr does not spoil Fremen's special victory. E3 pp.8,15, base p.12

A single holder of all Tech Tokens can still gain their ordinary stronghold equivalent. That does not itself establish a third territory occupied by both allies; the special three-co-occupied test must retain its physical co-occupation requirement. This is the direct composition of the threshold wording with the token FAQ, not a new permission to combine token custody.

Karama: native and converted

The Occupy cancellation is explicitly before Battle Plans are formed. Once canceled, the chosen battling faction dials its own forces and the other ally contributes zero. It does not revoke their three-stronghold victory permission or evict legally co-occupied forces. Preserve the selected combatant; do not quietly select whichever faction now has more forces. A separate Collection cancellation denies Ecaz's co-occupation bank income while the ally collects normally. It is not a cancellation of desert collection, territory access or the whole alliance. E3 p.16

An Advanced BG Worthless conversion uses the same substantive timing and result as a printed Karama. Conversion is not permission to cancel after a plan has become committed, to see the selected opponent's private plan, or to add a second Occupy choice after cancellation. The existing BG conversion response can decide whether the Worthless operates as Karama; after that decision the original source-bound Occupy request resumes. An allowed cancellation must recompute force ownership, support and dial options before any plan becomes valid. Base p.18

The p.16 row explicitly states zero combat contribution for the non-battling ally but does not itself give a full casualty sentence for that canceled case. Ordinary-winning-side retention and losing-side destruction are a plausible composition; do not advertise an independently retrieved designer ruling on that consequence. This is a separate source check from native rounding.

Historical bounded recommendation

Implement a pure, owner-labelled Occupy battle profile shared by validation, AI, public preview and actual scoring: current Ecaz/ally side; selected combatant; battle-order actor; dialed force owner; exact Ecaz contribution; ordinary winner casualty split; and canceled profile. Keep the rounding policy explicit until resolved; retain storm-separated and advisor exclusions, and never read the non-selected ally's hand. Integrate a durable public combatant-selection stage and the pre-plan Karama opportunity before admitting plans. The p.8 arithmetic can be represented as a labelled candidate in an isolated pure helper, but an execution path must not silently treat it as a designer-corrected rule. The independently supported allied-entry and battle-side identity work is the safer immediate production slice.

Acceptance examples should include Ecaz counts 1–5, either selected faction, all three relative storm positions, both win/loss outcomes, Basic/Advanced supported dials, Fremen free strength, advisor-only BG exclusion, printed and BG-converted cancellation, and JSON recovery after selection. Separate targeted follow-ups should cover the source-scoped special battle effects above, agreed/default desert allocation, Advanced Collection, and actual three-co-occupied victory. Keep the optional Homeworld/Nexus/Discovery modifiers explicitly outside the initial profile until their own faces and outcomes are wired; no ordinary Occupy rule may be used to bypass them.

The September audit changed no runtime and corrected the false designer attribution. The October Advanced cutover above is separate; Basic, optional/exotic interactions and independently unanswered cancellation details retain their historical boundaries.