Connect bounded Richese Nexus Cunning No-Field pair

docs/NEXUS_RICHESE_RULES.md

@@ -60,6 +60,14 @@ A reveal is not another arrival; E3 explicitly distinguishes No-Field entry from
 
 Concrete Cunning boundaries requiring design or a selected interpretation are: how two same-shipment uses update the shared last-used history; whether an already deployed marker must reveal before the pair; how the immediate faceup component and the still-concealed one affect the next prohibited denomination; and composition with native high-Richese extra ordinary forces or an allied shipment. The present `RicheseNoField` shape has only `lastShipped` and one `deployed` record, so it cannot simply represent an atomic pair by calling single-deploy twice. These are Cunning custody issues, not reasons to withhold Secret Ally's ordinary actual-force shipment.
 
+## Bounded native Cunning prototype (27 September 2026)
+
+The connected path is deliberately narrower than every possible E2 composition: a genuine Richese/CHOAM paired Nexus game with only Richese, CHOAM and classic factions, Basic or Advanced, no Homeworlds, Leader Skills, Discoveries, Sandtrout or Ecaz module. An unallied native Richese holder with an unused native shipment and no deployed marker chooses two distinct available physical tokens. Neither token may equal the previous shipment's `lastShipped`; the remaining concealed token becomes the next `lastShipped`. A previously deployed marker must be resolved through native reveal/movement first. This same-shipment nonrepeat convention is a product interpretation of the one-record E2 custody model, not a published FAQ ruling.
+
+The card is discarded at declaration. The native No-Field Karama cancellation precedes settlement and preserves the two tokens, reserves, spice and ordinary shipment allowance but not the card. Advanced Guild special prevention also leaves the physical shipment unpaid and unplaced while consuming the attempted shipment allowance and the card. Otherwise the pair is one arrival, costs the ordinary one-marker price, immediately reveals one chosen denomination and places up to that value of actual normal forces from current reserves in the destination. Only the other token remains concealed, publicly counting as one force; it draws from then-current reserves on its later native reveal. The immediate group plus the concealed marker count as actual presence for subsequent territory-entry and board logic, not two independent shipments.
+
+An owner-only control distinguishes ordinary No-Field, Smuggler and Nexus pair choices. All four bot profiles have a minimal legal pair candidate. The pending frame binds both physical identities, owner, token event, destination and one-marker price through JSON and in-memory SQLite CAS recovery. Public logs disclose the immediate faceup value/actual force count after settlement; the rival projection contains no concealed token identity or owner-only offer. Signatures detect partial saved-frame corruption, not arbitrary save forgery. Combined modules, allied No-Fields, high-Richese additional-force effects, Betrayal, later faceup display mechanics and full Nexus acceptance remain open.
+
 ## Existing integration points and verification
 
 `game/shipment-price.ts` already separates ordinary reserve prices, Guild cross-shipment prices and contributor-filtered Guild income. The ordinary engine chain is `validatePhysicalShipment` → `offerShipment` → `commitShipment`; its checks use native reserve withdrawal, typed counters, arrival stance, actual geography and shipment promises. Introduce a validated charged-count basis without replacing the physical amount. Keep current low-Junction income and occupied-payment routing after the reduced gross is computed.