Connect provisional Basic Guild and Karama allied No-Field prices

docs/CURRENT_STATUS.md

@@ -59,6 +59,12 @@ physical forces plus reserve-limited token materialization, visibly marked as a
 provisional formula. Native sealing/reveal, casualties, controls and legal AI
 are connected. One before/after engine smoke completes the battle; types pass.
 Advanced mixed battles and combined Occupy remain guarded.
+**Basic Richese allied discounted prices prototype.** Guild recipients and
+already-active Karama rates can receive allied No-Field shipments. The explicit
+provisional policy is one spice at the rounded one-force Guild rate, entirely
+to bank even when Richese pays. Shared quotes connect engine, owned controls
+and AI. Two before/after engine scenarios pass, including an actual native
+Karama purchase and Easy consent; types pass. Advanced counterparts remain guarded.
 
 
 

docs/RICHESE_ALLIED_SHIPMENT_AUDIT.md

@@ -2,6 +2,40 @@
 
 Primary-source audit, 2026-09-06. This narrows the broad integration warnings in the earlier No-Field audits. Ordinary turn ownership, consent and typed force selection can be composed without inventing extra faction powers. The genuinely unresolved payment and interruption intersections below remain distinct. The ordinary contract is now implemented in development fixtures as recorded below; this document does not activate a mode or certify all combinations.
 
+## Basic discounted allied shipment prototype — 8 October 2026
+
+The Basic-first pass connects Guild recipients and already-active Karama
+shipment rates. **Provisional price/payee policy:** use the rounded
+one-force Guild fee, one spice for either printed destination class, and
+send the entire payment to the bank even when Richese funds it. This
+chooses the ordinary discounted-rate reading for a usable first version;
+it is not a publisher answer to the precedence conflicts below.
+
+`alliedNoFieldShipmentPricing` supplies the same immutable price/policy
+quote to the engine, supplier controls and legal AI. Private pending-offer
+and recipient-consent views carry the explanatory `pricingPolicy` only
+to the pair. One payer funds the one-spice cost; the two-spice equal split
+is not offered for this price. Native acceptance/commit revalidation,
+token history, recipient force composition, cancellation/prevention,
+prior-marker reveal and shipment ownership remain in their original paths.
+Karama must already have been played through its own grant; this does not
+spend a second card implicitly or grant another shipment.
+
+The Guild income adapter routes these Basic payments entirely to bank;
+Guild gains no self-shipment/donor fee. The native Heighliner call still
+uses the force recipient, not the token supplier. Advanced Guild/active
+Karama combinations remain guarded. Ordinary undiscounted allied prices,
+on-planet Fremen exclusion, destination restrictions and public-mode gates
+are unchanged.
+
+**Brief smoke:** both old Basic guards reproduced. Guild-recipient and
+actual native Karama-purchase scenarios now reach a private one-spice
+offer and legal Easy consent, materialize five actual recipient forces,
+spend only the supplier's one spice, leave Guild income unchanged and
+consume only the recipient shipment. Supplier/consent SSR controls were
+observed in Chromium with matching price and provisional warning. Types
+pass; no broad suite, recovery campaign or deployed acceptance was run.
+
 ## Sources checked
 
 - **R2**, [GF9 CHOAM & Richese rulebook](https://www.gf9games.com/dune/wp-content/uploads/2021/11/CHOAM-Rulebook-low-res.pdf), pp6,11–12: allied offer, prior-marker reveal, shared last-use history, explicit one/two-spice payment and either payer, Guild-recipient Heighliner exception, No-Field cancellation. The full publisher-authored mirror `/tmp/dune-rules/choam-lelekan-mirror.pdf` and `.txt` were read; fresh official-domain search results reproduced the relevant pages. Mirror provenance is in `RICHESE_NO_FIELD_RULES.md`.
@@ -55,7 +89,7 @@ Test supplier-versus-recipient turn ownership, both full payers and any supporte
 
 ## Implemented ordinary contract before final checks
 
-**Implementation — Partial.** The engine opens `richeseAllyOpportunity` once for the active eligible recipient’s unused shipment, holding that turn for Richese to offer or pass. A direct voluntary offer also records the opportunity. `richeseAllyShipment` then requires the recipient’s explicit acceptance of exact private terms and legal typed mix, or decline. The proposal/payment implementation supports either full payer, plus `payer: both` only at cost two with one spice each. The recipient’s actual regular/elite reserves constrain composition. Fremen’s ordinary on-planet pool remains ineligible; Guild-recipient and active-Karama pricing remain guarded pending the specific ruling.
+**Implementation — Partial.** The engine opens `richeseAllyOpportunity` once for the active eligible recipient's unused shipment, holding that turn for Richese to offer or pass. `richeseAllyShipment` requires recipient consent and legal typed composition, or decline. Ordinary full/equal-split funding remains supported. Basic Guild and already-active Karama recipients now use the explicit discounted prototype above; their Advanced counterparts remain guarded. Fremen's ordinary on-planet reserves remain ineligible.
 
 Prevention precedes commitment. At successful commit the prior owner marker reveals first, the new allied token materializes immediately, exact funding settles once and only the recipient’s shipment is consumed. Decline/cancellation preserves the prior concealed marker and custody. This is the documented transaction composition above, not an explicit publisher FAQ about online action ordering.
 

docs/RICHESE_NO_FIELD_ENGINE_AUDIT.md

@@ -14,6 +14,14 @@ states the unresolved formula and refinement boundaries. The earlier
 mixed-battle absence/avoidance claims in the checkpoint below are historical,
 not the current Basic implementation.
 
+Basic Guild-recipient and already-active Karama allied offers now also use
+a visibly provisional one-spice/bank quote, with connected supplier,
+recipient and AI paths. Two direct before/after cases and current types
+pass; SSR offer/consent surfaces were observed in Chromium. Advanced
+counterparts remain guarded. This supersedes the earlier blanket price
+absence below; [the payment contract](RICHESE_ALLIED_SHIPMENT_AUDIT.md)
+retains the unresolved publisher precedence.
+
 ## Current resolution of the audited hooks
 
 - **Implemented in development fixtures:** separate physical `Player.noField` custody; public `force-presence` counting and location keys; own No-Field shipment with cancellation/payment stages; physical-plus-marker or marker-only movement; event-fenced voluntary reveal; collection and occupancy/control consumers; exact exposed storm sector and unprotected worm materialization/casualties; marker-only prospective battle pools, joint reveal and persistent zero-battle identity; server-enforced ordinary prescience no-dial restriction; allied opportunity/private consent/typed immediate shipment with fixed full or equal-split funding; Gamont reveal at a selected marker location followed by one actual force returned when present, including zero and colocated ordinary-unit cases.

docs/RICHESE_NO_FIELD_RULES.md

@@ -2,6 +2,19 @@
 
 Audit date: 2026-09-06. This document distinguishes the printed token lifecycle from engine integration and unresolved combinations. It does not certify Richese, Homeworlds, or any other gated game mode.
 
+## Basic discounted allied price prototype — 8 October 2026
+
+Guild recipients and already-active Karama rates now have a connected
+Basic first version: rounded one-force Guild price, one spice, entirely to
+bank even when Richese pays. Supplier and recipient controls label this
+as provisional; it does not settle the printed price/payee precedence.
+The shared quote supplies engine, controls and AI without charging for
+the materialized unit count or granting another shipment.
+[Canonical payment contract](RICHESE_ALLIED_SHIPMENT_AUDIT.md).
+Two before/after direct engine cases cover a Guild recipient and an actual
+native Karama purchase, private offers, Easy consent, five actual arrivals
+and one bank payment. Types pass. Advanced counterparts remain guarded.
+
 ## Basic mixed battle prototype — 8 October 2026
 
 The Basic-first pass now admits an ordinary Richese battle containing both
@@ -92,7 +105,7 @@ This table records the original adapter contract. The implemented subset and cur
 3. **Full-plan special Karama and structured Truthtrance.** The ordinary Atreides dial prohibition is explicit. Whether a broader entire-plan power or a particular promise question overrides it was not resolved by a retrieved specific answer. Do not leak the value through private legal-plan previews, public maximum dials, error strings or bot reasoning.
 4. **Homeworld use.** R3 recommends Richese in a Homeworld combination but supplies no retrieved No-Field-specific rule defining off-planet hidden custody, one-on-planet versus off-planet coexistence, or homeworld threshold disclosure. General module availability is not an answer to those lifecycle questions. The isolated model represents a single Arrakis marker and does not authorize Homeworld placement.
 5. **Capturing, transferring or returning a concealed marker as a force.** Movement-as-a-force and Gamont's explicit forced reveal do not establish a general conversion for every card or Guild transport-to-reserves. A generic return helper must not erase a hidden token without a source-backed reveal/custody cause. This module exposes no such automatic escape from last-use history.
-6. **Allied discounts and reserve source.** Ordinary rules compose recipient consent, typed physical-force allocation and allied funding; these are now integrated as described in `RICHESE_ALLIED_SHIPMENT_AUDIT.md`. Guild-recipient and active-Karama pricing/payee precedence remain guarded pending a ruling. Ordinary Fremen reserves are on-planet and do not qualify for this off-planet shipment method; this is a source-location exclusion, not a missing elite-allocation rule.
+6. **Allied discounts and reserve source.** Ordinary consent, typed allocation and funding are integrated. Basic Guild-recipient and already-active Karama price/payee have the explicitly provisional prototype above; their Advanced counterparts remain guarded pending resolution. Ordinary Fremen reserves are on-planet and remain ineligible for this off-planet method. See `RICHESE_ALLIED_SHIPMENT_AUDIT.md`.
 7. **Supply orientation.** Concealed denomination is explicit. Hiding unused IDs/values in public JSON is the minimum privacy consequence, not a claim about an otherwise undocumented physical supply layout. The last revealed used face is public until another deployment; historical log knowledge may legitimately remain.
 
 ## Required verification

docs/RULE_DECISIONS.md

@@ -16,6 +16,8 @@ They supersede earlier software-absence claims only within their named scope.
 | Tleilaxu Ambassador leader alternative | First-death own native leader revives free instead of forces, independently of ordinary revival allowance. | [Ambassador](TLEILAXU_AMBASSADOR_RULES.md) |
 | Ordinary allied shipment transit | Depart during the shipper's turn; excess new physical visitors still present at ending go to Tanks, even when exit was prevented. Old co-occupation timing is separate. | [Allied transit](ALLIED_TRANSIT_RULES.md) |
 | Ordinary mixed No-Field battle | Private pool is physical forces plus reserve-limited token materialization; both plans seal before one reveal. Advanced and combined Occupy remain separate. | [No-Field](RICHESE_NO_FIELD_RULES.md) |
+| Guild-recipient allied No-Field | Rounded one-force Guild fee: one spice to bank, even when Richese funds it; no Guild self-shipment income. | [Allied No-Field payment](RICHESE_ALLIED_SHIPMENT_AUDIT.md) |
+| Already-active Karama / allied No-Field | Honor the already-played rounded one-force Guild rate and bank routing; no implicit additional card or shipment. | [Allied No-Field payment](RICHESE_ALLIED_SHIPMENT_AUDIT.md) |
 
 No publication or faction/mode gate is opened. The exact 7 October user
 rulings below remain distinct from these prototype choices.