admin/Dune
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
3e0fa2a8a2a67a10b04791c29ea935c0de084b33
Dune/docs/HOMEWORLD_BENEFITS_RULES.md
T

393 lines
33 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Homeworld charity and revival benefits: source contract
Source audit, 9 September 2026. This separates publisher wording, rule composition, and remaining decisions. It does not enable Homeworld games or replace the outstanding Ambassador/Duke revival rulings.
## Salusa Low and free Sardaukar revival — 27 October 2026
The [GF9 Ecaz and Moritani rulebook, pp. 9–10](https://www.gf9games.com/dune/wp-content/uploads/EcazMoritani-Rulebook-LOWRES.pdf#page=10)
gives Salusa's Low penalty as no free Sardaukar revival and says Karama cannot
affect Homeworld advantages or penalties. The supplied Advanced rulebook,
physical p. 31 / printed p. 29, exempts Emperor special revival from turn limits,
but does not exempt it from this separate Homeworld prohibition. Physical p. 39 /
printed p. 37 makes Ghola's force return free. Applying the Low penalty across
these sources is a source-composition interpretation, not a specific FAQ.
For fresh Advanced Homeworld actions, the shared rule excludes Sardaukar from
free normal revival, Ghola, special Emperor Karama and Tleilaxu Ambassador
returns while the Low penalty applies. Paid normal Sardaukar revival remains
legal subject to the usual costs, discounts and limits; free ordinary forces and
eligible leaders remain available. An unused ordinary free allowance is retained
after a paid star, so a later eligible ordinary return may consume it. Ambassador
returns use the native reserve destinations: normal forces to Kaitain and
Sardaukar to Salusa.
Provisionally, an established Low occupation retains its penalty after native
repopulation until the original qualifying occupation ends. Foreign presence
without a usable original qualification history is guarded rather than assumed
to be occupied or unoccupied. Previously accepted unstamped revival receipts and
special intents retain their original terms; the change does not rewrite saved
counters. Rule behavior, controls and minimal bots are connected in the current
prototype; focused integration verification and wider combinations remain due.
This section supersedes the Low-to-High free Ghola claims in the historical
sections below; it does not certify complete Homeworlds or release readiness.
## Salusa Ghola and live Truthtrance promises — 27 October 2026
Historical: free Sardaukar cannot now be returned while the Low penalty applies;
see the later [Salusa Low decision](#salusa-low-and-free-sardaukar-revival--27-october-2026).
Before either full plan seals, a current battle promise no longer forbids every
population-crossing Ghola. Preserve a feasible Yes, whole-No or grouped claim.
Reject the actor's return if the resulting High support regime makes that
actor's own promise impossible, including an odd dial with only free double
stars or a positive support promise with no payable ordinary counter. A rejected
action consumes no card, force, revival allowance or binding.
The actual physical return and any obsolete inspection renewal occur before
Truthtrance feasibility. Carry the real Ghola actor/action through that check
and its printed card disposal. An uncontextual release must not retire the
actor's promise first. Feasible answers remain fixed; an opposing promise that
actually becomes impossible follows the existing release policy. No new promise
parser or battle solver is introduced.
The server quotes each real force group using a detached copy, the native Ghola
effect/disposal and the existing reachable-plan solver. Current force maxima,
elite allowance and exact `homeworldRevivalBlocks` use those results. Human
controls and minimal AI consume the existing shared block adapter; they do not
reconstruct claim legality or inspect opponents' plans.
The supplied PDF physical39 / printed37 requires Truthtrance compliance while
possible. [Official November2020 FAQp8](https://www.gf9games.com/dune/wp-content/uploads/2020/11/Dune-FAQ-Nov-2020.pdf#page=8)
permits current-turn and AND/OR questions. Neither separately defines deliberate
self-impossibility; rejecting the actor's voluntary destruction is the existing
[product interpretation](TRUTHTRANCE_NONBATTLE_READINESS_20260907.md#where-promises-currently-bind-actions),
not a new printed Ghola restriction. Full sealed-plan repricing remains an
unfinished preview boundary. Earlier inspection/promise guards below are dated
history where superseded by this follow-up.
### Live-promise evidence
Sixteen selected files pass145/145 with types/lint. Native tests use actual
initial Atreides Truthtrance, priority passes, current battle questions and
definite answers. They cover feasible Yes2, whole-No1, grouped OR1/2, own
impossible Yes1 and positive support, later use after completing the original
promise, and Prescience1 plus TruthYes2 renewal. Exact control-block reasons
match authoritative rejections and maxima. All four minimal profiles submit
legal required plans and omit blocked/spent Ghola.
The separate runtime has three original public Advanced E/A/G base33/Homeworld
prefixes totaling169 actions. A real paid first-battle star loss creates the
Tanks source; no played resource, phase, inspection, promise or receipt is
installed. Only unopened initial card/Spice positions and native scalar
lotteries are selected. Sixteen accepted continuation actions compare feasible
return, one immutable rejection followed by actual original-plan completion/
later Ghola, and original inspection renewal while preserving TruthYes2.
Eleven GameTable/two BattlePreparation SSR renders, three existing group-block
adapter checks and one shared answer-adapter packet connect current controls.
Stateful Ghola/answer/plan inputs are not operated in a browser. Full seals,
new played Cunning/Ghola pairs, native-Salusa battle, complete modes, mobile,
deployed and final recovery/privacy/custody acceptance remain separate.
No build was repeated for this focused rule change.
Private proof: `/home/quintine/.local/share/dune/checkpoints/20261027-salusa-ghola-truth-proof-v1/`;
runtime: `20261027-salusa-ghola-truth-runtime/run-v1/` beside it. Frozen tree
`d713902330ddca9084ab9a2d9e02b239ee7344b2d33d97eb9f040131a5f1c65c`
contains3354 files. Final prose overlays are limited to this contract, the
dashboard and implementation log.
## Salusa Ghola and renewed inspection answers — 27 October 2026
Historical: free Sardaukar cannot now be returned while the Low penalty applies;
see the later [Salusa Low decision](#salusa-low-and-free-sardaukar-revival--27-october-2026).
The earlier commitment-free window below now includes completed inspection
answers before either full plan is sealed. Commit the actual Ghola return and
current Salusa High benefit first. Preserve a still-feasible native answer;
if it becomes impossible, its owner must answer the same field again before
plans can be submitted. An odd dial using only now-free double-strength stars
is such a case. The old value is not made into a sealed plan, refunded or used
as permission to weaken a star. Normal modal interactions still finish first.
Authority for the update is the supplied PDF physical41 / printed39: its
outlined impossible-Prescience Q&A requires an updated valid answer before
reveal. Physical3 / printed1 identifies outlined rulings as unofficial; their
authority here is the user's adoption of this PDF, not a newly found GF9 FAQ.
Immediate Ghola remains physical39 / printed37, with no separate exception.
Reuse the existing [native-first inspection renewal](NEXUS_ATREIDES_RULES.md#residual-poison-and-two-inspected-commitments).
For Cunning, keep a feasible native answer first, then test the extra answer
jointly. If the native answer is impossible, renew its original field before
the extra original field. Retain observation history and the spent Nexus
record; do not charge again, offer another cancellation or choose new fields.
This multi-answer priority remains a provisional online composition. Full
sealed plans and active Truthtrance battle promises retain their explicit
preview guard; this slice does not define their repricing or release.
### Inspection-renewal evidence
Fourteen selected files pass115/115 with types/lint. The actual original public
Advanced E/A/G base33/Homeworld source can select Basin from the real chooser's
first-battle alternatives, earn a paid Sardaukar casualty and reach the later
Arrakeen battle. Actual Atreides declarations, counter-response passes and
Emperor answers create the initial dial1/2 commitments. No played hand, force,
purse, clock, inspection answer or battle receipt is installed. Only unopened
initial card/Spice positions and native scalar lotteries are selected.
The separate runtime uses two prefixes totaling104 actions and11 continuation
actions. Actual Ghola returns once in each: odd1 requires the owned same-field
answer2 before actual plans/calls; feasible2 stays fixed without another
question. Nine GameTable and two BattlePreparation SSR renders plus one actual
shared UI answer-adapter packet connect the current controls. Stateful input
operation/browser hydration is not claimed. All four minimal profiles provide
legal pending answers. Existing Cunning/Residual tests cover the inherited
protocol; no new played Cunning/Ghola pair is certified. The older explicitly
controlled resource fixture clears its stale Charity frame when staging Battle.
Private proof: `/home/quintine/.local/share/dune/checkpoints/20261027-salusa-ghola-inspection-proof-v2/`;
runtime: `20261027-salusa-ghola-inspection-runtime/run-v1/` beside it. Frozen
tree `1321c432fa0a204e5e8db3406be76b4608dac129409c9395fa77eac2bde1290a`
contains3351 files. Final evidence overlays are limited to this document, the
dashboard and implementation log. No build was repeated for this focused rule
change; complete modes, native-Salusa battle, browser/mobile, deployed and final
recovery/privacy/custody acceptance remain separate.
## Salusa Ghola before battle commitments — 27 October 2026
Historical: free Sardaukar cannot now be returned while the Low penalty applies;
see the later [Salusa Low decision](#salusa-low-and-free-sardaukar-revival--27-october-2026).
Historical first window: inspection restrictions described in this subsection
are superseded by the renewed-answer follow-up above. Its proof remains dated.
An otherwise legal Ghola may return a dead Sardaukar to Salusa during the
Emperor's battle while no plan is sealed and no inspection answer or active
Truthtrance battle promise is committed. Returning the actual counter from
Tanks raises Salusa from one to two; the current High benefit then supplies
free Sardaukar support in that same battle. It does not add that counter to an
Arrakis army, spend ordinary revival allowance, waive the once-per-turn elite
revival limit or bypass a pending response/decision. Existing force controls and
minimal AI use the same projected elite allowance and combat descriptor.
The user-authorized revised PDF establishes immediate Ghola at any time
(physical39 / printed37), current population and the native return destination
(physical22 / printed20), and strength/spice commitments plus matching casualty
allocation (physical11–12 / printed9–10). Salusa's printed High face supplies
the free support. No new timing priority is introduced around native modal
decisions. A native-Salusa return joins that World's actual pool; its connected
population rules remain current rather than freezing a face for the battle.
**Remaining preview boundary:** once either plan, an inspection answer or an
active battle promise exists, the population-crossing return remains guarded.
This is an unfinished continuation, not an official prohibition. The source's
identified unofficial impossible-Prescience-answer update (physical41 /
printed39) supports a future explicit update, but does not settle every sealed
dial/support composition. Do not refund support, reopen sealed plans, allow
wasted support or weaken free Sardaukar merely to make an old dial legal. Normal
force and eligible leader targets remain usable under their ordinary gates.
### Focused evidence
Nine selected files pass78/78 with types/lint. The public original Advanced
E/A/G base33/Homeworld programme takes51 source actions: paid E4-star shipment,
actual two-star movement and Guild entry create two real battles; a paid first
win puts one actual star in Tanks. In the later uncommitted battle, five native
actions play the originally dealt Ghola, submit plans with free star support
and complete traitor calls. Salusa ends at two, Arrakis receives no revived
counter and the same physical card is discarded once. All four profiles provide
legal plans after that return. The previous paid-support and answered-Prescience
guard cases remain; a new opponent-only sealed case also remains guarded.
The separate native runtime renders eight GameTables before/after return,
after an actual sealed-plan branch and after completion. This is server
rendering with native action packets, not stateful Ghola/plan input operation
or browser hydration. It does not certify native-Salusa battle chronology,
module combinations, full modes, deployed acceptance or final recovery/privacy/
custody assurance. No build was repeated for the focused rule-helper change.
Private proof: `/home/quintine/.local/share/dune/checkpoints/20261027-salusa-ghola-proof-v1/`;
runtime: `20261027-salusa-ghola-runtime/run-v1/` beside it. Frozen source tree
`7d6408588870da018b93bc5a7208d19eb24a4050e023ce9eff3ac3c3227efbba`
contains3350 files. Only this evidence text, the dashboard and implementation
log are final documentation overlays after those checks.
## Provisional Low Homeworld revival prevention — 25 October 2026
**Prototyped / Partial.** The earlier target guard against Tleilaxu special
Karama is removed. Native Advanced Tleilaxu may choose a Low Homeworld faction
at the existing quiet window or original pending revival decision. Eligibility,
physical Karama disposal, once-per-game use and ordinary enclosing priorities
remain in the [native special-power contract](TLEILAXU_SPECIAL_KARAMA.md).
The user-authorized revised PDF's physical page 38 H prevents force/leader
revival for a chosen player, with no Homeworld exception. Publisher E3 printed
page 10 protects Homeworld advantages and penalties from Karama. Under the
14 October choose-recommended instruction, the explicit provisional composition
is **event prevention**: Low keeps its printed extra free-revival rate, but the
ordinary return is prevented as a whole, including its conditional extra
counter. No separate bonus-only return is created. This is not a located
combined publisher FAQ or a change to the printed High/Low face.
No physical force, leader, payment or quota changes because of the stopped
return. No actual free return exists to award Tleilaxu/Axlotl income, and no
paid Cyborg or newly returned group exists to trigger Ix/Southern/Tleilax High
follow-ups. Prior completed returns and their effects remain completed. There
is no new response aimed only at the Homeworld bonus, and no retroactive
interruption of a committed deployment.
The 24 October prevention cutover is retained: Ghola is prevented during the
remaining affected Revival, then becomes available outside that phase under
its own ordinary card rules. The Emperor's native special Karama keeps its
printed immunity. This does not restore the old provisional Ghola bypass or
conflate La La La with a Karama effect. Targets retain readable persistent
guidance; existing minimal policies consume the shared actual native offer,
without strategic tuning.
Bounded evidence: [native source](../tests/fixture-homeworld-revival-prevention.ts),
[native transitions](../tests/homeworld-revival-prevention-runtime.test.ts) and
[controlled regression](../tests/homeworld-revival-benefits-engine.test.ts).
Frozen 10-file 87/87, types/lint/build and four actual-control/engine/GameTable SSR
journeys pass. Genuine 75-action original setup, typed free shipment and Storm
losses earn Low 0/Tanks 5 before the real second Revival. Quiet/pending prevention
retains rate 4 and all physical/usage state; decline returns 4 and awards original
income 1. Held Ghola rejects during affected phase 4, then returns 5 after actual phase
progression. Four existing policies act legally without tuning. One existing
in-memory Ghola lifecycle file is included in the selected union; this is not
final assurance. Private proof:
`/home/quintine/.local/share/dune/checkpoints/20261025-homeworld-revival-prevention/`.
The earlier unresolved-overlap paragraph below remains the historical source
audit; this dated policy supersedes its execution guard. Full module/High-
effect combinations and final assurance remain open.
## Provisional Ix High paid revival bonus — 25 October 2026
**Prototyped / Partial.** The printed Ix High card now connects an ordinary
paid Cyborg revival to its automatic physical Suboid return. The original
`revive` controls still choose the base group and which Cyborgs use the ordinary
free quota. A free Cyborg, paid Suboid, Ghola return, or another faction paying
Emperor extra revival does not trigger this native paid-Cyborg grant.
The card establishes two free Suboids per paid Cyborg. The authorized revised
PDF's physical page 22 gives the current-population Homeworld rule, but does
not supply an Ix-specific quota/shortage ruling. Physical page 9 retains the
ordinary revival cap. The following are explicit **provisional composition
policies**, selected under the user's 14 October instruction to proceed with
recommended interpretations; they are not publisher errata:
- Observe native Ix High before accepting the group. A return that first raises
Ix from Low to High earns no retroactive bonus; a later independent paid
Cyborg request observes its own current population.
- Reserve the selected base group's normal Suboids first. Return up to two
remaining physical Suboids from Tanks per paid Cyborg. A shortage reduces the
grant; it never manufactures a counter, substitutes a Cyborg, blocks the
original legal purchase or leaves a debt for a later return.
- The bonus is additional to normal revival allowance and ordinary free quota.
Recruits does not multiply it. A discounted positive Cyborg payment qualifies;
canceling the price discount retains the grant only if the original request
can still be funded. The original selected quantities and invoice stay intact.
- Prior La La La prevents the free bonus on new requests while leaving paid
revival available. The existing reactive opportunity also recognizes a
bonus-only free event: successful La La La stops the whole atomic request
without payment or returns; preventing La La La resumes the original frozen
request and grant. No new Homeworld-only Karama response is generated.
- A delivered bonus counts as one free-return event for existing Tleilaxu and
Axlotl income. Combine it with any base free return rather than awarding
twice. The paid invoice, once-per-turn receipts and Tleilax's phase-start Low
suppression remain. This composes the revised PDF's general free-revival
income at physical pages 21 and 38; neither passage specifically names Ix.
The accepted request stores only its positive `ixSuboidBonus` count. Settlement
checks its paid Cyborg allocation and actual remaining Suboids, then deposits
the entire physical return once. Ordinary `revived` and `freeForcesRevived`
increase only for the selected base group. Old pending requests without that
field retain their accepted behavior. The player view exposes current High
eligibility; persistent selection text explains the automatic grant or La La La
suppression. Existing minimal AI uses the same ordinary legal actions, with no
strategic refinement.
Implementation and focused evidence: [physical quote](../game/ix-homeworld-revival.ts),
[native chronology](../tests/fixture-ix-homeworld-revival-bonus.ts),
[native tests](../tests/ix-homeworld-revival-bonus-runtime.test.ts),
[quote tests](../tests/ix-homeworld-revival.test.ts),
[continuation tests](../tests/ix-homeworld-revival-continuation.test.ts),
[controls](../components/ix-homeworld-revival.tsx) and
[control tests](../tests/ix-homeworld-revival-controls.test.ts).
Frozen proof covers 12 related files, 210 cases: 209 originally passed, and the
sole Recruits fixture failure was corrected to a quote-only composition test;
its full 6/6 file, final types/lint/build pass with the other 2,793 source files
unchanged. Four actual native runtime/SSR journeys pass (Basic 111, Advanced 118,
prior-free 112 and original-Ghola 111 source actions). These earn original 47 cards,
a real paid 5 mixed invasion and five actual Tanks casualties; no played state
is installed. Separate controlled continuation/income/La La La/Recruits contexts
are labelled. Proof is retained privately in
`/home/quintine/.local/share/dune/checkpoints/20261025-ix-homeworld-revival-bonus/`.
Full Homeworld/module combinations, comprehensive assurance and final deployed
acceptance remain open. This dated section supersedes the earlier audit's
decision-pending implementation boundary below; it does not turn those gaps in
printed authority into located rulings.
## Provisional high-threshold revival deployment — 9 October 2026
The previously blocked case "a supported revival whose own return first reaches
the Homeworld's high threshold" now has a visibly provisional policy: the
population **resulting** from that return decides the deployment ability, so the
crossing return may itself place its revived starred (Fremen Southern
Hemisphere) or ordinary free (Tleilaxu High) group instead of only returning it
to reserves. The printed card grants the ability while the faction is at High,
and the returned forces are what make it High, so evaluating after the deposit
is the natural composition of the two texts.
This is a first-version implementation choice, **not a located publisher timing
ruling**. The Tleilaxu low-income condition still snapshots native status on
entry to Revival, so crossing high later does not erase that printed
start-condition. Partial groups, split destinations, Southern storm placement,
allied-Homeworld limits and entry effects requiring a shipment classification
remain guarded.
Evidence: the `homeworld-revival` union (65 cases) passes with the crossing
return staging its own placement choice, and the four preserved Advanced
captures that previously stopped at `phase 4` on this question now complete
(78/68/932/133 further actions) with zero rejections. See
[the resumption record](IMPLEMENTATION_STATUS.md#9-october-2026--gated-captures-resumed-under-the-basic-occupation-and-odd-force-occupy-prototypes).
## Publisher facts and provenance
| Source | Verified material |
| -------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [GF9 E3, pp.9–10,16](https://www.gf9games.com/dune/wp-content/uploads/EcazMoritani-Rulebook-LOWRES.pdf) | Thresholds follow current native reserves. Low adds one free revival and one bank spice **when collecting** charity; Salusa supplies neither. Karama cannot affect Homeworld advantages or penalties. The FAQ explicitly gives low Fremen four free revivals; Recruits doubles the current rate, capped at seven. Local publisher extract: `/tmp/dune-rules/ecaz-audit.txt`, lines375–445 and745–750. |
| [GF9 base, pp.8–9,16–17](https://www.gf9games.com/dunegame/wp-content/uploads/Dune-Rulebook.pdf) | Ordinary charity raises zero/one spice to two. Normal force revival has a three-counter limit. Fremen normally get three free, cannot buy additional normal revivals, and may grant their ally three free. Advanced BG always gets two charity. Local `base.txt`, lines472–504,929 and1068. |
| [GF9 E1, pp.6–9,12](https://www.gf9games.com/dunegame/wp-content/uploads/2020/09/IxianAndTleilaxuRulebook.pdf) | Tleilaxu may raise another faction's limit to five; its own normal limit is unrestricted. Revival payments and bank income for other factions' free revival/Ghola are separate. Cyborgs cost three to revive; ordinary free revival may select either type. Special Tleilaxu Karama prevents revival. The Karama table denies BG charity entirely. Local `ix-official-mirror.txt`, lines197–198,250–255,335 and535–537. |
| [GF9 November FAQ, p.3](https://www.gf9games.com/dune/wp-content/uploads/2020/11/Dune-FAQ-Nov-2020.pdf) | The explicit Advanced Karama timing table restricts Tleilaxu's special effect to Revival. This is not inferred from Guild timing. |
| [GF9 E2, pp.7–8,14](https://www.gf9games.com/dune/wp-content/uploads/2021/11/CHOAM-Rulebook-low-res.pdf) | La La La prevents Free Revival during Revival. Inflation doubles or cancels charity, expressly including BG and CHOAM's income. Cancellation of CHOAM's income changes ordinary charity's payer to the bank. Local `choam-lelekan-mirror.txt`, lines279–318 and545 onward. |
Actual Ix HIGH and Tleilax LOW cards were visually rechecked in the [four-sheet component photographs](https://www.reddit.com/r/DuneBoardGame/comments/16w27x0/every_homeworld_cards/), locally `homeworld-reddit-face2.png` and `homeworld-reddit-face3.png`. These are photographs of publisher components, not authority derived from commenters. Ix grants two free Suboids when paying to revive a Cyborg. Tleilax specifically tests whether it **starts** Revival low and then denies income from other factions' Free Revival. The card catalog and broader source inventory are in [Homeworld component audit](HOMEWORLD_COMPONENT_AUDIT.md).
## Supported composition for implementation
- **Current eligibility:** use the native population before the claimed event. Do not globally freeze low benefits at phase start. Tleilax's specifically worded income penalty is the exception and requires a durable phase-start observation.
- **A grouped revival:** quote the current rate before moving that group, preserve the accepted quote through interruptions, then derive the new population for the next independent request. Neither a mid-group per-counter repricing loop nor a whole-phase entitlement lock appears in the sources. This transaction boundary is an implementation inference consistent with the current-rate language, not a separately printed timing rule.
- **Free rate versus capacity:** adding one free revival does not generally add one paid revival. A useful formula is `max(ordinaryLimit, currentFreeRate)` for total normal capacity, followed by physical Tanks and already-used allowance checks. This makes the FAQ's four-free Fremen entitlement usable without granting everyone a fourth paid revival. The exact formula is an inference; the FAQ does not separately state the no-Recruits total-limit calculation. Do not describe it as a quoted erratum.
- **Fremen alliance:** apply the granted rate of three, then the recipient's own low bonus. The donor's low population does not turn its printed alliance grant into four. Canceling the alliance benefit removes that source, not the recipient's independent Homeworld increment. This follows the distinct grant and native modifier; it does not add an ordinary Karama cancellation of every faction's printed free rate.
- **Charity:** establish a valid collection first. Multiply ordinary charity and the conditional low bonus by Inflation, while keeping the bonus bank-paid. At zero spice, ordinary low charity is two from its ordinary payer plus one bank; Double makes four plus two. At one spice it is one plus one, or two plus two. Cancel produces no collection and no bonus. Advanced BG's ordinary amount is two regardless of wealth; a canceled BG charity claim similarly has no qualifying collection. These are cross-source compositions, not located worked examples.
**CHOAM's own income — resolved 7 October 2026 by user ruling.** Its initial two-per-faction payment is named the Charity advantage, and E2 expressly includes it in Inflation. The user ruled that it **counts as a qualifying collection** for Tupile's low bank increment, so the low-population bonus is added under the same Inflation multiplier as ordinary charity. The engine no longer blocks low-population CHOAM opening income.
## Keep cancellation sources distinct
`revivalRules.freeBlocked` currently represents **La La La**, not Karama. Its prohibition covers taking the current Free Revival, including the Homeworld increment. Homeworld Karama immunity does not provide immunity to this independent Worthless power. Likewise, Inflation is a charity modifier, not a direct Karama against a Homeworld. There should be no response aimed solely at turning off the low increment.
The Tleilaxu special Karama has a different unresolved overlap: it prevents revival itself, while E3 protects Homeworld advantages. The natural event-based reading prevents the ordinary request without erasing its rate, just as denying a qualifying charity event prevents its conditional bonus. However, no retrieved primary text specifically settles whether the low extra counter survives that special prohibition as an independently executable return. Do not silently turn this into La La La's known non-Karama rule, or claim that only the bonus survives without an explicit interpretation.
## Tleilax and Ix finite effect boundaries
**Tleilax:** snapshot native low status on entry to Revival; crossing high later does not erase the printed start-condition. Suppress only the bank income for another faction's Free Revival. Do not suppress paid receipts, its own revival, or Ghola income merely because they share a helper. E1 names Ghola separately; the low card does not name it. Preserve existing once-per-faction ordinary-free-income accounting independently of this condition. High Tleilax's optional shipment of the returned group is a separate destination continuation, not an automatic consequence of this low-income work.
**Ix:** the trigger requires an actually paid Cyborg return while the relevant high advantage applies. A free Cyborg, Ghola, or a paid Suboid supplies no such trigger. The grant remains two physical Suboids per qualifying Cyborg, never two newly created pieces or a Cyborg substitution. A discounted but positive Cyborg payment is still payment. Keep paid/free typed allocations in the quote so total transaction cost is not mistaken for proof that every selected Cyborg was paid.
The retrieved card and publisher FAQ do **not** settle whether those Suboids consume normal revival allowance or are additional to it; this changes legal quantities after one or more earlier revivals. Nor do they explicitly choose between partial fulfillment from an insufficient Suboid Tanks pool and requiring both. Both issues materially affect a complete automatic purchase/bonus implementation. Do not add an arbitrary optional decline to hide that uncertainty. Recruits explicitly doubles free **rates**, so it does not by itself establish four bonus Suboids per paid Cyborg. Its interaction with any exceptional total must follow the resolved quota policy.
## Release boundary
Implementable together: current low benefit projection, source-separated ordinary charity payments, current normal revival quotation, retained accepted-request pricing, and the explicit Tleilax phase-start income condition. Add tests at the exact threshold, during a suspended request, after crossing it, with a Fremen ally, and with Inflation/La La La/BG cancellation. Keep CHOAM's own-income classification, special-Karama overlap and Ix bonus quota/shortage behavior visible until interpreted. These are the remaining material combinations from this audit, not reasons to postpone the independently established mechanics.
Fresh searches of publisher rulebooks/November FAQ and targeted designer clarification queries found no additional primary ruling for the unresolved cases. Tournament compilations, wishlists, and movie-game rules were not used as authority. In particular, a third-party compilation's added “breaking current revival limits” language is not a GF9 quotation. No runtime, tests, saved rooms, or automation were changed.
Reference in new issue View Git Blame Copy Permalink