Dune/docs/NEXUS_GUILD_RULES.md

Spacing Guild Nexus: shipment source contract

Later runtime checkpoints: Guild Cunning implements the extra-shipment continuation. Guild Secret Ally implements supported paid routes using the focused source resolution. The bounded Betrayal checkpoint below records direct local full-payment verification, separately from wider and deployed acceptance. The original audit remains historical source evidence; revisit its Secret Ally Homeworld-return question against the newly authorized Advanced reference before reopening research.

Source audit, 10 September 2026. This documents the three printed panels and their integration boundaries. It does not implement them or certify complete Guild, Homeworld, Nexus or expansion compliance. Common Nexus lifecycle and existing release gates continue to apply. No user question was sent during this audit.

Classic original phase-module funding — 18 October 2026

The classic core entry now retains original Tech3+ and Advanced Strongholds2+, base33 or selected36 and optional14. Guild fee parents bind only genuinely enabled module state; original bare-parent grammar remains. Real token/card owners are earned at their original boundaries. Actual combined paid5/ Guild-card receipt/Bureaucrat2 leaves payer7/recipient13/Guild6 while one Heighliners spice waits; actual phase5 close pays its owner Guild7, independent of the diverted shipping receiver. No phase income finances earlier fees. Source and complete bounded evidence.

Classic core funded card shipments — 18 October 2026

Fresh classic2–6 Basic/Advanced Nexus uses original base33 or selected independent36, optionally all14 Skills, with actual native Guild payment replacement initialized through the shared public core capability. No card variant or separate public reaction selector is required. Original standalone Homeworld and other native envelopes remain separate; played games are not reflagged or supplied fabricated history.

Within this core entry, the earlier Cunning/Richese producer exclusions below are superseded. Original signed reserve/cross/return Cunning and one-counter Richese shipments retain their actual funded invoice, native counters and physical continuation through the existing fee acknowledgement. The actual Guild singleton spent for Cunning cannot also be held for rival Betrayal Use. Existing neutral wrong-face Pass and provisional timing remain unchanged. Actual5/price1 and third-party5→recipient3/Bank2 retain their original rules. Current source, 304/304, controls and legal policies.

Primary evidence

The Guild face was freshly inspected in the original photograph of GF9's twelve Nexus cards, local inspection copy /tmp/dune-nexus-cards.jpg:

• Cunning, Guild only: an immediate second shipment after the owner's Shipment and Movement. The second shipment's forces cannot move unless Hajr permits it.
• Secret Ally, Guild absent: Guild shipping prices, with cross-planet shipment or return to reserves permitted as the holder's shipment action.
• Betrayal, opposing Guild seated: take one entire shipping payment otherwise going to Guild or the bank, including one's own payment. The face expressly overrides a faction collecting for occupying Junction.

The base GF9 rulebook, p19 identifies three native shipment forms: reserves to Arrakis, one Arrakis territory to another, or one territory to reserves. Guild uses half ordinary prices; returning costs one spice per two forces. Its flexible placement in the combined-turn order is Advanced. Page 23 rounds fractional shipment costs upward, confirms the return tariff, and preserves payment by allies. These publisher passages were freshly retrieved from the official search index; direct PDF opening returned 403.

The November 2020 FAQ was freshly checked through indexed publisher text. Page 2 allows Hajr after entering Arrakeen/Carthag and grants the resulting ornithopter access. Page 8 requires Hajr during one's own turn under ordinary movement rules. Page 7 separates canceling one Guild income receipt, one discounted shipment, cross/return permission, and Advanced timing; cancellation stops one ability use. Page 2 routes each contributor's shipment funding directly to Guild or bank, with Guild's own contribution going to the bank. Page 7 routes independent Karama shipment payments to the bank.

The Ecaz & Moritani rulebook, pp10–11, inspected in the publisher-authored mirror /tmp/dune-e3-nexus-rules.pdf, calls Cunning an enhancement of a native advantage. It requires used Nexus cards to be discarded. Its Homeworld rules distinguish native Guild transport from other factions' routes, prohibit shipment to an ally's world, and exclude Homeworlds from territories. Homeworld advantages and penalties are immune to Karama.

Search results concerning tournament house rules and the separate 2021 movie game were excluded. No retrieved publisher clarification specifically addresses Guild Nexus with Hajr, skipped movement, an independent Karama shipment, or Secret Ally Homeworld returns.

Cunning: supported sequence and composition

Keep one combined turn open. Finish or decline the original shipment and ordinary movement opportunity, then resolve the Nexus second shipment before handing the turn to another faction. Declining ordinary movement is not a new prohibition on the card: the named Shipment and Movement turn has still reached its end. No inspected text requires moving a positive number of forces merely to reach that boundary. Likewise, do not implement the second shipment by reopening the original unused shipment slot after a pass; it is a distinct card-granted opportunity. These are phase-sequence compositions, not a dedicated FAQ answer about passing.

Allow native shipment forms. The new shipment inherits native Guild reserve, cross-planet and return choices, actual tariff, legal source group, storm/stronghold rules and custody. Nothing restricts it to the first shipment's type or destination, or makes it free. A group moved during ordinary movement can be selected for the later cross-shipment; shipping is a separate action. Payment, physical arrival, technology triggers and entry reactions must settle before the second-shipment opportunity can finish.

Movement remains bounded. The second shipment does not grant an ordinary movement. Ending the first ordinary movement by declining it cannot leave an ordinary move available for newly shipped forces. The express exception is Hajr. If Hajr is played after the second shipment, retain the same active player until its optional legal extra move finishes or is declined. A previously played but unspent Hajr move can remain available under ordinary allowance composition; a Hajr move already consumed before the second shipment cannot grant a third move. Track the actual remaining allowance, not merely whether Hajr appears in a played-card list. A later move checks current ornithopter access normally.

The card does not expressly establish how the separate physical Richese Ornithopter combines with this exception. The 18 October provisional composition permits it to replace one earned unused Hajr allowance, retaining actual completed-group counts and no abandoned-group credit. This supersedes the earlier software exclusion; it is not a dedicated publisher ruling. Native city range remains a different ability.

Separate native cancellations. Cunning creates an enhanced native shipment allowance. Treating its declaration as a cancelable native enhancement is the common Cunning/general Karama composition. Cancellation consumes the attempted Nexus use but grants no second shipment and cannot undo the first shipment or completed movement. This is distinct from permitting a second shipment while canceling its discounted rate or its cross/return form. The base FAQ explicitly treats those native advantages separately; one generic cancellation must not silently choose all three outcomes. Existing rate/route cancellation limitations remain implementation work. Independent Karama shipment permission also has its own payment route; it must not silently authorize a second shipment after Cunning itself was canceled.

Homeworld Cunning routes are native routes. Guild remains the native Guild faction, so an additional legal Guild shipment can use an already supported native Homeworld transport adapter. Preserve the route's typed forces and pricing, Homeworld alliance prohibition, BG limitations and actual arrival rules. The card does not turn a Homeworld into a territory or grant another faction the high-Junction sponsor ability.

Secret Ally: one modified shipping action

The absence test is the seated native Guild faction, not whether a Guild player currently has board forces. Consume the held Nexus when declaring its use for the owner's shipping action. The grant supplies the printed rates and route choices; it does not add a second shipment, create a real alliance, provide flexible Advanced Guild timing, collect other players' payments, or convey every Guild/Homeworld benefit.

For ordinary Arrakis routes, use the same rounded Guild tariff and one-territory source selection as native transport. The shipment still consumes the holder's normal shipping action. The ordinary movement afterward remains available and uses the holder's own movement rules. Keep physical elite/advisor/No-Field classification, source custody, storm restrictions and entry continuations with the actual player. A Fremen holder's ordinary free reserve reinforcement remains a distinct native option; do not overwrite its existing zero-price action merely because a Guild Nexus is held.

The Guild is absent, so no native Guild income recipient or native Guild advantage owner exists. Do not manufacture a Guild-rate Karama response targeting a nonexistent player. The Nexus rule does not establish universal immunity for borrowed effects; this is a distinction between the printed card grant and the native cancellation targets. Ordinary actual arrival reactions can still apply.

Secret Ally with Homeworlds needs separate resolution. E3 expressly limits Arrakis-to-Homeworld shipment to native Guild, except its named Homeworld transport advantage; Secret Ally expressly allows return to the holder's reserves. With reserves represented on a Homeworld, those provisions meet directly. Neither the face nor the inspected FAQ explains whether this grant overrides that faction-specific route restriction. Native Guild Cunning does not have that ambiguity. Do not silently extend the Secret Ally return to arbitrary foreign Homeworlds, or treat the entire Secret Ally panel as implemented while that material combination is unresolved. Richese No-Field discount combinations retain their existing separate pricing boundary.

Betrayal: payment replacement

Bind one actual shipment payment and redirect that payment in full to the Nexus holder. This is payment replacement, not bank income added alongside the existing receiver. The express own-payment case allows paying the shipment's cost and receiving that payment; it does not permit financing the cost with the expected later receipt. A free shipment supplies no positive payment to take.

The face expressly supersedes occupied Junction collection for that payment. Preserve the original charged amount before any native low-Junction division; do not hand the card holder only the Guild's reduced half while paying the remainder to an occupier. This follows the component's full-payment override, not the unoccupied low-Junction runtime quote. The existing contributor-rounding and occupation-lifecycle questions are not resolved generally by this one card.

An implementation needs an original payment identity, exact charged contributions and a committed replacement recipient before ordinary Guild/bank/occupier settlement. Preserve hidden held Nexus identities until an actual play. The bounded protocol below is an application privacy choice, not a resolution of the publisher timing gap. A zero-cost Guild Ambassador shipment cannot manufacture a Betrayal award.

Existing integration points and required state

engine.ts currently uses p.shipped, numeric p.moved, movesAllowed, finishMovementTurn and the endMovement action to manage the combined turn. movesAllowed currently treats a played Hajr as a two-move ceiling, which alone cannot distinguish an intentionally ended ordinary move from an unspent extra move after a new second shipment. A Cunning continuation needs that distinction before the queue advances. Advanced movementTurn/chooseGuildTiming and Sapho ordering must see one uninterrupted owner turn, not insert Guild into the queue twice.

Preserve distinct settlement adapters: ordinary reserve shipment, guildShip, native Homeworld shipment, concealed No-Field and Junction-sponsored transport. shipment-price.ts already separates reserve prices, Guild transport tariffs, contribution bounds and Guild income. guild-homeworld-shipment.ts explicitly requires native Guild and should not be broadened indiscriminately for Secret Ally. shipment-promises.ts also requires review: a second shipping action must not erase an earlier committed Truthtrance answer or reapply one shipment's promise to the wrong action.

The pure Cunning receipt module records the original combined-turn event, native Guild owner, turn, canonical faction roster, original shipment flag, original movement count and whether Hajr had been played. createNexusGuildCunning checks the unallied owner's active phase-five turn. validateNexusGuildCunning checks historical facts without reading current hands, resources, alliances or force custody. The engine owns the independently bound mutable lifecycle and second-shipment intent/receipt. Actual shipment custody and payment remain in their existing continuations. Do not clear a shipped flag as the sole source of the extra right, and do not use current hand membership as proof after spending the Nexus. Reconnect and uncertain responses must preserve one debit, one arrival and one consumed allowance.

nexusGuildCunningMoves(receipt, currentHajrUsed, movesAfterSecond) returns only the remaining Hajr extra allowance. Ending ordinary movement forgoes at least one ordinary slot, so original movement counts zero and one both permit at most one Hajr move; an original count of two permits none. A newly played Hajr supplies that same one extra slot, while losing a previously recorded Hajr or claiming more moves than that allowance rejects. That original v1 bound remains compatible. Counted v2 supports genuinely replayed Hajr; v3 additionally records actual completed physical Ornithopter credits through the optional fourth current-count argument. The engine retains unfinished-flight rights separately; the helper does not reset or mutate the original movement counter. Its pure tests cover declined and used first actions, Hajr before and after, spent allowances, native ownership, exact signatures, JSON restoration and private-field getter traps.

Integrated verification should exercise first shipment followed by moved/declined ordinary movement, all three second-shipment forms, Hajr before/after and already consumed, cancellation of only the selected native advantage, paid BG/entry continuations, native Homeworld routes, private offers, stale requests and actual SQLite restoration. Passing the pure receipt tests does not establish those engine or persistence behaviors.

Nexus Guild Betrayal

1 October 2026 bounded prototype contract. The authority for the effect is the original printed Guild face, transcribed in nexus-card-reference.ts. The internal player guide is /rules?topic=nexus-guild-betrayal#nexus-guild-betrayal; source links stay in developer documentation, not the player-facing guide.

Entry, physical cost and funding

The explicit fresh guild-betrayal development profile admits two to six ready classic-faction seats in Basic or Advanced, including native Guild and at least one other faction. It uses physical base decks and Nexus; Homeworlds are optional only without Skills and when genuinely enabled and seeded during setup. It does not retrofit games, silently add Homeworlds, admit other expansion factions/decks or combine Discoveries, Tech Tokens, Stronghold Cards, Semuta, Kull or Richese previews.

Explicit --profile guild-betrayal --leader-skills instead retains the original all14 setup and native classic Guild roster with no Homeworlds or other overlays. The ordinary skill quote layer admits this exact composition rather than silently disabling Mentat questions, Sandmaster movement or related skill bands. The user-ruled Bureaucrat offer follows the original completed invoice; on a qualified third-party share it diverts two from the holder receipt to Bank. Payer costs, donor escrow, physical Nexus discard and shipment remain original. See Bureaucrat ruling and evidence.

Only original native shipment producers are admitted here. Native Guild Nexus Cunning's second shipment and Richese Nexus Secret Ally's discounted shipment are blocked in this profile before spending either singleton or creating a native parent. Those effects outside this profile remain unchanged. Guild Secret Ally is already unavailable because native Guild is seated, not because this preview establishes a new prohibition on its printed panel.

Use requires an unallied non-Guild player holding the actual singleton Guild Nexus while another seated player is native Guild. The accepted Use discards that physical Nexus once. It spends no Treachery Card, Treachery hand slot or extra activation spice. Cunning and Secret Ally remain distinct modes; temporary leader control, a borrowed price or an empty Guild board does not change native roster identity.

Bind the full original positive charged fee, its payer, authorized contributions and exact source quote before settlement. Redirect that one fee to the holder instead of any ordinary Guild, bank or occupied-Junction receipt. Do not reduce the award to guildIncome, add a bank award alongside normal income, or charge a second invoice.

Own payment must already be affordable from personal spice and any actually authorized ally funding. Pay the original cost first, then receive the entire redirected fee; a solely self-funded holder has net zero spice change, not a free declaration financed by future income. pledgeAid has already removed the donor's spice into escrow: settlement consumes the original g.aid contribution once rather than debiting the donor again. The payer's own remainder and original donor allocation do not change because the recipient changes. Current voluntary-spend promises and committed-resource restrictions still apply.

Original native shipment adapters

Saved producer	Original adapter and facts to retain
reserve	commitShipment: ordinary physical reserves onto Arrakis, including native elite/advisor classification and valid explicitly selected native Homeworld reserve sources; original destination, tariff and own/authorized-ally contributions.
guildTransport	commitGuildTransport: the exact native Guild cross-planet or return group, typed force identities, tariff and contributions.
homeworld	commitHomeworldShipment: an already legal native Homeworld route, its exact source custody, destination, physical groups and paid quote. This grants no foreign route or Secret Ally Homeworld-return permission.
junction	performJunctionTransport: the original accepted Junction sponsor/offer, route, physical sources, quote and contributions. Replacement does not create another sponsor or transport opportunity.

Source feasibility and full funding are rechecked before the gate. Existing native special-stop and applicable native rate responses occur first; a stopped, declined, invalid or zero-cost declaration supplies no positive payment and cannot spend Nexus or create an award. Ordinary free Fremen reinforcement and free Guild Ambassador transport stay free. This sequencing is the bounded application's settlement boundary, not a new general Nexus/Karama priority or immunity ruling.

For every admitted producer, the original native payment and physical shipment complete once. Preserve reserve withdrawal, elite/advisor classification, source and destination custody, storm/entry checks, shipment-used flag and applicable arrival/response suffixes. Ordinary movement afterward remains the shipper's own opportunity; Betrayal grants no extra shipment, no extra move, no altered rate and no rerouted force.

Occupied Junction: full-payment override only

The printed face expressly overrides income for occupying Junction. On accepted Use, deliver all of the original charged payment to the holder and suppress the ordinary Guild/bank/occupier allocation for that invoice. A four-spice fee produces four spice for the holder, not two while an occupier receives the other two. Preserve the full fee before any low-Junction division; neither an ordinary eligible Guild subtotal nor its rounded half is the card's award.

This source-clear exception does not decide first-versus-current occupier entitlement, departure/replacement/contest expiry, retained occupation penalties or ordinary contributor rounding. Existing Homeworld payment and occupation restrictions remain for non-overridden settlement. Passing does not select a disputed owner or arithmetic interpretation; any source that cannot settle unchanged must retain its native pre-offer guard rather than use a hypothetical Betrayal play to bypass it.

Neutral acknowledgement, private Use and saved continuation

Every publicly possible responder sees the same event and shipper: unallied non-Guild seats with public held-Nexus presence, including the shipper when eligible. A seat with an irrelevant secret face still acknowledges with Pass; only the privately eligible Guild-card holder sees Use and its own unavailable reason. Public membership never depends on the hidden face. No publicly possible responders means automatic ordinary settlement. This is an application privacy protocol, not printed timing authority, a new user ruling or blanket Karama immunity.

The fixed projection is {event, shipper, canPass, hasPassed, canUse, blocked}. It reveals no new price, force count, route, source family/world, destination, donor, balances, recipient, raw signature or private receipt. Existing own-source and public inspection entitlements remain unchanged. The neutral wait/acknowledgement log does not disclose secret fee or source; only actual Use and the source's normal committed-result logging may report information already appropriate after shipment. A printed reference inspector is not evidence of anybody's held face.

guildBetrayalPass and guildBetrayalUse carry only the offered event. The server binds the payment and recipient; a client cannot choose them. Pass keeps Nexus and spends nothing; a recorded pass cannot be undone for that event. Every required pass resumes the original settlement once with its original receiver. Accepted Use closes the gate, spends one physical Nexus and resumes the same native delivery with the fee receiver replaced. Underlying shipping, movement, pledging, cards and other decisions remain suspended until resolution.

Save the typed producer continuation, original private invoice, pass set and independent pending/completed cursor/receipt. Restore must authenticate the acting seat and retain the same source, event and once-only outcome; never replay a raw shipment Action or infer permission from a missing frame. Stale/foreign events, malformed or orphaned ownership, competing Use/final-Pass and historical card recycling require unchanged rejection or one authenticated committed winner, not a repeat payment, donor debit, Nexus spend or force move.

Verification and release boundary

Bounded verification: locally verified; broader acceptance Partial. npm run check passes types, lint and 6,114 offline tests; the production build passes. The selected Guild/profile/turn/control and related Kull recovery set passes 147/147 across nine files. Engine and authenticated SQLite cases exercise all four native adapters, source-consistent revoked-grant rejection, own pre-funded refund, other/escrow payment, all-pass, occupied low Junction, singleton/force custody, neutral projections, JSON/restart, races and stale/orphan rejection. Source feasibility uses actual current native quotes rather than fixed storm-sensitive routes; durable rejection checks real SQLite changes, not attempted SQL text.

Independent review and actual before/after reproduction repaired an accepted Advanced Richese Secret Ally parent that could not resume: the bounded profile now blocks that unsupported offer before card expenditure. Native transport permission is revalidated independently at declaration, restore and commit; a purchased rate is not a transport grant. Final scoped rules/persistence re-reviews report no actionable finding. Unrelated native Cunning/Secret Ally behavior remains outside this profile's guard.

Eight actual ready QA lobbies entered via exact-version guild-betrayal CLI with private backups and their original authenticated seats. Preparation reused each admitted setup/code/roster, completed genuine native setup/phases and source actions, and arranged conserved pre-action resources; no saved room was replaced by a separately constructed game. At 390 pixels, actual controls and own printed-card inspector prove Basic own refund, occupied low-Junction full fee, native Guild return and all-pass; Advanced Homeworld bank fee, authorized escrow, native Junction and free Fremen; irrelevant-face Pass, private Use, source locking, contextual rules navigation and refresh. Read-only saved-state verification matches the original native force suffix, exact whole-fee money ledger, authorized escrow, physical Treachery/Nexus inventory and closed receipt across all eight rooms.

Local built-worker HTTP is 48/55: five POST 503 responses and two timeouts retain the known Wrangler-dev limitation, not green HTTP acceptance. Pushed code 8a56299155d0f12c8c4678bfbe5913be71fea5bb has completed/success workflow 36798718410 for that exact source; the mandatory isolated full HTTP/storage verifier precedes immutable-image publication. This is separate from local Wrangler and live deployment; no deployed/full-mode claim follows from publication.

The new preview does not inherit verification from Guild Cunning/Secret Ally, ordinary shipment tests or the twelve-face catalog. Complete Guild/Nexus/Homeworld families, wider factions/modules, strategic AI and difficulty calibration, full games, public starts and live deployment remain gated.