Dune/docs/STRONGHOLD_CARDS.md

Advanced Stronghold Cards

Historical development module checkpoint, 7 September 2026: the six printed effects, public card custody, mobile declaration, support accounting, AI choices and readable faces are integrated. The later user-authorized classic Advanced preview already permits Stronghold Cards; preserve that access. Complete Advanced/expansion release and arbitrary combinations remain gated.

Expanded E1/E2 faction rules

The same fresh stronghold-factions profile now admits selected Ix/Tleilaxu and CHOAM/Richese native families with classic opponents, Advanced only, two through six seats and Stronghold Cards alone. At least one native expansion faction and its selected distinct ix/choam decks are required. CHOAM-only ordinary deck35; Ix or both47; native Richese cache10 stays separate. Ecaz/Moritani and other overlays remain excluded. The new-family rule paths are Partial / Development Verified, not complete faction/module acceptance.

Native No-Field0/3/5 control/reveal and real cache-acquired Stone outcomes, plus native Face Dancer zero/partial/army replacement and next-turn card control are integrated. Targeted16/16 rule cases, types/lint and11 actual rule-program cases pass. Eighteen unstaged2..6-seat paired/mixed games complete:11,066 accepted actions, zero rejections,290JSON restores. An old Ixian/CHOAM-only report header was corrected to list per-family decks/cache; an actual three-family report smoke completes with the corrected descriptor.

Human390px controls used original CLI setups: G7VDY6KB v12 chose Stone kill mode and completed the Habbanya-winning battle with real Stone retained; 736HJUD3 v8 selected two reserves for Face Dance and replaced the original winner while its Stronghold card remained with Ixians until the turn boundary. No new save/privacy/custody audit lane, full-suite or historical-seat campaign. Mixed No-Field/full-plan and unresolved Stone/Poison Tooth cases stay guarded. Final coherent rule/guide26/26, check:quick, build and actual expanded390px guide pass;205 changed document links are valid. Owned temporary drivers and the test tab/service are removed/closed.

Native Ixian and CHOAM integration — 2 October 2026

Fresh local stronghold-factions integration has Partial / Development Verified rule-path coverage: Advanced only, native Ixians and CHOAM plus unique classic opponents, two through six seats, exactly Ix and CHOAM Treachery decks and Stronghold Cards. The combined deck has 47, not49, physical cards: CHOAM replaces the two shared Ix cards rather than adding duplicate identities. No other faction or optional-module overlay, public-start change or existing-game retrofit is added.

Genuine first end-Mentat custody, all six effects, all five HMS copied advantages, current-control zero/sole/multiple choices, native CHOAM bank support and actual donor funding are connected. Eighteen native source-replay cases and all four projected legal policies pass. Five unstaged Advanced games (2..6 seats) complete with3,129 accepted actions, no rejections and82 JSON restorations. Earlier affected162/162 and full6,513/type/lint/build evidence was recorded before the user's rules-first assurance deferral; it is not a new per-feature gate.

Original local CLI room LAUDR2WN v14 continued its actual undealt setup without redealing. At390px the human Ixian chose Arrakeen from its real HMS copy choices, entered dial6/support3 with bank2/personal1, and sealed the native plan. The original opposed battle completed: personal1→0, three actual cyborg losses and native CHOAM income1. Refresh showed the real Collection opening, not a fictitious completed collection.

Fixture repairs use native CHOAM market done, phase-opening priority, legal Weirding pairing and actual Collection timing. A rare original private deal (initial seed12) used the real Guild-held Thumper for native Nexus alliance, without stealing/redealing it. Prior scoped reviews found no remaining defect. Save/privacy/custody assurance is deferred until all rules under the2 October priority; no new seat/database audit is scheduled. Ecaz rounding, Richese/cache/Stone and other overlays remain outside this profile. Complete factions/cards/modules and deployed acceptance remain open. Final focused guide/tooling25/25, check:quick, build and expanded390px Partial/DevelopmentVerified guide pass. No full-suite or assurance rerun was added after the user's priority amendment.

Authority and inventory

The original CHOAM & Richese module contains six separate Stronghold Cards, one of each. They never enter the Treachery deck, hands, discard, bidding pool or hand limit. The publisher rulebook requires Advanced play; neither CHOAM nor Richese needs to be a participating faction. The mobile card remains set aside when no placed mobile stronghold exists.

The user-authorized root Advanced2.3 PDF governs Advanced differences from 1 October onward; metadata2.3/editorial2.2 and physical-page provenance are in the source amendment. Printed faces and GF9 material supply details omitted there. The historical checkpoint's original sources are:

1. Publisher CHOAM & Richese rulebook, printed pp4, 6, 9–12: inventory, Advanced prerequisite, end-turn custody, CHOAM bank-funded support income and advisor timing. Readable publisher-authored mirror SHA-256 b628cef05b167953c2f192c8acfdefea92aee8f5497eea779edacf7be25e6299.
2. All six publisher-designed English physical faces, visually checked from the product-gallery photograph. Image, SHA-256 b489eaec185f0ecb3413a34276b19c93dfe852b37458dc436d3d976d015f7da4, 1024×768. This is a third-party photograph of the printed components; photographer, date and printing are unverified. It is research evidence, not a bundled asset.
3. Publisher Ecaz & Moritani rulebook, printed p8: Ecaz controls a stronghold occupied only by itself and its ally.
4. Classic base rules, pp10–11 and13; November2020 FAQ, pp2 and8: battle outcomes, support, dial meaning, Tooth and defenses. Later direct rulings take precedence over general older text. No tournament-rewritten Stronghold effects were adopted.

Printed identity	Canonical board ID	Complete effect in original language
Arrakeen	arrakeen	The bank contributes two spice toward actual force-support payment in battles there.
Carthag	carthag	Without a poison weapon in your plan, your played non-poison defense also functions as a Snooper.
Habbanya Sietch	habbanya_ridge_sietch	Win battle ties there regardless of storm order or Juice of Sapho.
Sietch Tabr	sietch_tabr	A win earns bank spice equal to the opposing dial rounded down.
Tuek’s Sietch	tueks_sietch	Each Worthless card played in the battle earns two bank spice; the face imposes no win condition.
Ixian Hidden Mobile Stronghold	hidden_mobile_stronghold	Copy an advantage of another controlled stronghold and declare it before Battle Plans.

No card has a printed once-per-turn limit. Benefits apply to their holder in that location, not globally. The copied benefit applies to the battle inside the mobile stronghold.

Custody and decisions

game/stronghold-cards.ts owns the canonical definitions, control query, costs and income arithmetic. Setup leaves every owner null. At final end-Mentat settlement, after eligible board changes and advisor normalization, each card transfers to its controller or is set aside. Cards remain with their recorded holder throughout the next turn, even after leaving, losing a battle or becoming advisors. claimedTurn prevents duplicate settlement. Normal turn completion and terminal victory both use the same ownership checkpoint.

Fighter presence across a territory counts; advisors do not. A concealed No-Field contributes one public presence without reading its private denomination. Ordinary allied armies do not pool control. Exactly Ecaz plus its reciprocal ally selects Ecaz, as the explicit faction exception. A mobile interior is distinct from its pointing territory.

Before mobile battle powers and plans, the card holder receives a public choice if multiple other strongholds are currently controlled. One eligible advantage is announced automatically; zero proceeds without a copied advantage. The persisted choice is bound to the battle event, owner, phase and exact eligible pool. An accepted copy remains fixed for this battle. Public views expose ownership, declared copy and each combatant’s effective advantage; sealed plans and foreign hands retain their existing privacy.

Composed-rule interpretations

These are recorded textual interpretations, not claims of dedicated publisher FAQ answers:

• Mobile control versus card custody: the face says controlled stronghold, whereas the general module separately permits retaining a departed location’s card. Therefore use current physical control, without requiring custody of that other card. A newly occupied location can qualify; an abandoned card alone cannot. No tournament end-of-Bidding timing or replacement copy pool is used.
• Arrakeen low costs: bank support is min(2, actual support). Unspent allowance never becomes personal cash, and free Fremen support cannot mint income. Normal and allied personal charges use the remaining cost. CHOAM’s published income includes the bank portion, excludes CHOAM’s own donor share, and follows the existing no-income-on-traitor rule.
• Carthag roles: defensive Weirding Way is projectile defense and can gain Snooper; defensive Chemistry already is poison defense. Worthless and empty slots cannot gain protection. A poison-role weapon, including Chemistry or Tooth in the weapon role, prevents this advantage. The added property does not replace physical identity: Shields still cause Lasgun explosions and Snooper protection does not stop Tooth. The defense actually used after any permitted late replacement supplies the property.
• Habbanya and Stone Burner: the general battle-tie advantage also decides a tied undialed-token comparison. It does not override a traitor victory or create a winner after mutual destruction. Sapho remains an unfinished card effect; this implementation does not certify its future ordering.
• Tabr: use the opposing declared dial, not leader strength, support cost or token count. A single traitor caller wins and qualifies. Explosion and double traitor have no winner and do not qualify.
• Tuek: ordinary defeat and single-traitor outcomes do not erase played Worthless cards. An explosion can still qualify. For double traitor, the base rule that neither player receives spice takes precedence, so neither receives this payout. CHOAM’s out-of-plan Worthless discard powers and BG Karama conversions are different uses and do not qualify.
• Ecaz ally battle: card custody belongs to Ecaz. No general transfer or automatic sharing of a held card’s benefit was inferred. Complete combined-force Ecaz combat and its dial representation remain outside this checkpoint.

Player experience and AI

The table has public ownership labels, a six-card gallery, an enlarged inspector, and a decision panel for mobile copies. Support controls include Arrakeen’s two bank spice and separate the actual bank contribution from player/ally payment. Successful automatic support, copy, ownership and income events use the existing house-colored notices without an acknowledgement.

The internal reference has searchable complete original effect prose, related phase/faction links, an example and five-part implementation checklist. It contains no external source links. Each illustration is original built-in image generation, saved locally under public/art/strongholds/*-v1.png; exact prompts, original paths, hashes and visual inspection notes are in STRONGHOLD_ART_GENERATION.json. Normal and enlarged faces retain crisp interface text independent of the artwork.

All four policies consume their entitled public copy/effect and private hand/support data. Arrakeen adds affordable supported half-step dial candidates so a large army does not overlook free support when its ideal dial is unaffordable. Carthag and Habbanya enter combat evaluation. Mobile choice heuristics consider funding, defense, defender priority and Worthless holdings. This is policy support, not proof of calibrated relative strength.

Verification

• 12 pure inventory/control/cost/income cases.
• 9 actual engine lifecycle and six-effect cases, including CHOAM donations, defender Stone tie, losing Worthless cards and stale mobile answers.
• 4 all-profile AI cases, including 4/6/10/20-force Arrakeen armies and hidden-state noninterference.
• 3 additional combat-role and mutual-effect matrix cases.
• 4 production-room SQLite tests: fresh module instances, real private-seat recovery, sealed-plan views, duplicate/crossed copy CAS, exactly-once subsidies/income, and eight corrupted saved-choice bindings. The room scheduler does not answer a pending human choice; direct engine normalization and actions reject invalid bindings without writing.
• Independent actual-action matrix: 17 Arrakeen/CHOAM support-share combinations, all paid once with the expected balances.
• 40 complete sampled base-faction Advanced games with the optional module: all player counts 2–6 × all four homogeneous profiles × two roster/seed replicates, nine distinct rosters. 19,665 accepted actions, zero rejected candidates/stalls/invariant failures, 224 setup actions and 912 continued JSON round trips. Observed 330 custody, 21 support and 7 income notices. Source hashes were stable during the 105.603-second run.

The game study uses the unchanged strict base audit initializer, then adds only empty Stronghold module configuration immediately before the first setup action. It does not change cards, resources, starting forces or the public start gate. Runner /tmp/dune-stronghold-fullgames.ts, full results /tmp/dune-stronghold-fullgames.json (SHA-256 d6f924aca8ed714df0a92008b4d6eda5b54d1e0192f4eda1a937dd98adbcf3e8), summary /tmp/dune-stronghold-fullgames-summary.json. This base-roster study does not exercise an Ixian interior or CHOAM full game; focused tests cover their bounded interactions.

The registered suites pass 1,528 rules/client/component tests and 133 persistence/API tests. Logs: /tmp/dune-stronghold-full.log and /tmp/dune-stronghold-multiplayer.log. Desktop normal and enlarged faces, plus all six enlarged phone-width faces at 390×844, were visually inspected with complete readable text and working close controls. Final live-control and build verification are recorded in the implementation status checkpoint.