Compose native Richese No-Field and Stone with Advanced Occupy

docs/COMPOUND_SHIPMENT_PROMISES.md

@@ -45,14 +45,25 @@ support this composition; it is not a new expansion or timing ruling. Earlier
 phases, other future actions, expansion shipment modes and arbitrary prose
 enforcement remain outside the bounded implementation.
 
-Twelve actual programs cover mixed truth/skip/shipment/changed-spice, all four
-legal policies and a second joint pure+mixed promise. The affected
-truth/ship/discard rule batch passes88/88; mixed/reference23/23, types/lint and
+Eight actual programs cover the four mixed truth/skip/shipment/changed-spice
+paths and all four legal policies. Nested and joint promises have rule
+regressions. The affected truth/ship/discard rule batch passes88/88;
+mixed/reference23/23, types/lint and
 build pass. Human390px **4PVKRRWB v10** authored and answered the actual OR
 claim, then spent all20 spice as a bribe, skipped shipment and fulfilled the
 promise while the public answer stayed Yes. This is bounded local evidence, not
 complete Truthtrance, module or deployed acceptance.
 
+The later390px **FCGZTEGV v11** control check authored an outer OR around
+`(current spice >=10 AND ship4 to Arrakeen)`, with an alternative shipment6
+to Carthag. The respondent answered Yes at20 spice, paid a real12-spice bribe,
+then shipped4 to Arrakeen at a four-spice cost. The frozen nested branch
+fulfilled the whole answer with only4 current spice; native end-movement
+continued the original turn and the exact grouped question/Yes survived refresh.
+This is additional human control evidence, not another program case or an
+expanded timing/module claim.
+
+
 
 ## Meaning and authority
 

docs/CURRENT_STATUS.md

@@ -16,6 +16,27 @@ open mode gates.
 
 ## Current checkpoint and work
 
+**Native Richese Occupy — bounded Development Verified:**
+Richese-present Advanced tables now resolve their mandatory Ecaz coalitions
+instead of rejecting unrelated native factions. Ordinary or marker-only Richese
+pools retain the selected plan owner, original force owners and concealed
+0/3/5 reveal timing. Stone/Mirror compare actual undialed physical counters,
+including the fixed Ecaz remainder; cancellation uses only the selected own pool.
+The original same-owner mixed No-Field, whole-plan disclosure, Ix Stone/Tooth,
+Harass/Stone and optional-module guards remain. Basic/public starts are unchanged.
+Affected363/363, types/lint, build and26 actual native programs pass.
+The previously failed genuine six-native Advanced sample finishes2424 accepted
+actions/no rejection/65 JSON continuations. Fresh CLI **GQ4FEWNW v8** and
+human390px **T78EFNZK v22** exercise original setup, private combined total5/
+support2, No-Field5 materializing only two reserves, actual owner losses and
+native CHOAM income/Collection. See
+[native Richese composition](ECAZ_OCCUPY_RULES.md#native-richese-no-field-and-stone-composition--3-october-2026).
+The final guide is readable at390px; the original human v22 state remains at
+Collection after the required isolated worker reload. A stale prior-build guide
+chunk required a cache-free local navigation; deployed cache-upgrade acceptance
+is not claimed.
+
+
 **Mixed current-fact/shipment Truthtrance — bounded Development Verified:**
 structured questions now combine supported current facts with this-turn reserve
 shipments in bounded nested AND/OR trees. Current facts freeze privately at a
@@ -26,10 +47,10 @@ only the respondent receives the compiled fixed answers.
 Two bounded owners supplied the pure expression logic and nested authoring
 controls; one integration owner wired the question, private projection,
 promise receipt, public redaction, policies and existing continuation.
-Types/lint, affected88/88, mixed/reference23/23 and build pass. Twelve actual
-program cases cover truth/skip/shipment/changed-spice, all four policies and a
-second joint promise. Human390px **4PVKRRWB v10** authored and answered the
-actual OR question, then spent all20 spice as a bribe, skipped shipment and
+Types/lint, affected88/88, mixed/reference23/23 and build pass. Eight actual
+program cases cover the four truth/skip/shipment/changed-spice paths and all four
+policies; nested and joint promises have rule regressions. Human390px **4PVKRRWB v10**
+authored and answered the actual OR question, then spent all20 spice as a bribe, skipped shipment and
 fulfilled the promise while its public answer stayed Yes. Earlier phases, other
 future actions and existing module gates remain unfinished. See
 [mixed compounds](COMPOUND_SHIPMENT_PROMISES.md#mixed-current-facts-and-future-shipment--3-october-2026).
@@ -38,8 +59,8 @@ Code **cd985c7c34a05057ed98b34838effdbcddb7697d** is pushed.
 job111031663449, completed/success. Existing isolated storage/HTTP verification
 and verified-image publication pass:
 `ghcr.io/quintine/dune:sha-cd985c7c34a05057ed98b34838effdbcddb7697d`.
-The full offline suite also keeps one pre-existing combined-Occupy sample
-failure (reproduced at 0ceb28b), documented as an open bot-offer defect.
+The prior full offline run exposed a pre-existing native combined-Occupy
+integration failure, not an illegal bot offer; native Richese composition now repairs it.
 No deployment or new assurance campaign; live **ab5c782** remains last observed.
 
 **Requested priority — 2 October 2026:** throughput improvements are verified
@@ -978,8 +999,9 @@ guarded; no complete Ecaz start is certified.
 
 The bounded [Mirror Weapon battle path](MIRROR_WEAPON_ENGINE_AUDIT.md#user-selected-cleanup-interpretation-28-september-2026)
 admits the canonical physical card in CHOAM/Richese-deck Basic/Advanced
-classic/CHOAM/Richese battles without combined optional modules. Effective
-copied attacks, copy-first Tooth/Stone choices, public Stone feasibility,
+classic/CHOAM/Richese battles and source-clear Advanced Ecaz/Moritani
+composition without optional overlays. Effective copied attacks, copy-first
+Tooth/Stone choices, public Stone feasibility,
 saved custody, human controls and legal AI are connected. A victorious
 physical Mirror can be kept even after a copied activated Tooth or Artillery
 attack under the user's interpretation, not a GF9 clarification. Combined

docs/ECAZ_OCCUPY_RULES.md

@@ -153,6 +153,56 @@ returned Ecaz2 reserves, sent original fixed3 to Tanks and left Guild2.
 real equal-leader comparison, paid three Ecaz reserves, left Ecaz2/Guild2 and
 sent six total Ecaz counters to Tanks. Both reach original Collection.
 
+### Native Richese, No-Field and Stone composition — 3 October 2026
+
+Advanced native tables now admit Richese alongside the already supported
+families. The actual six-native failure was Ecaz+Ixians versus CHOAM at
+Carthag with Richese elsewhere, not a Richese opponent or an illegal bot offer.
+The roster-wide guard and fresh-label-only runtime restriction prevented a
+mandatory source-clear battle. Native composition now selects the real lead
+and original force owners; it does not suppress that battle or fall back to
+an ordinary one-army plan. Optional overlays remain guarded.
+
+The supplied Advanced PDF **physical p36, Richese No-Field B** says a concealed
+0/3/5 marker counts as one force for all effects until reveal, materializes
+only available reserves, and reveals with Battle Plans. A marker-only Richese
+ally therefore remains original battle presence even with a zero prospective
+pool. The selected plan actor receives its private variable pool; rivals do
+not receive that pool or an Occupy profile containing the secret denomination.
+The physical Richese owner reveals once after both seals. Dial prescience and
+whole-plan restrictions follow the actual variable-force owner rather than the
+original chooser. Preventing Occupy with Ecaz lead makes only Ecaz's own pool
+inspectable; the unrelated marker stays concealed until original reveal timing.
+Richese's own ordinary-plus-marker dialing and broader disclosure rulings remain.
+
+Stone Burner compares **floor(E/2) + native ally physical undialed tokens** for
+active Occupy, or the **selected lead's own pool only** after prevention.
+Its total dial offset is removed before native typed casualty enumeration.
+Mirror copies use the same comparison and original physical-card retention.
+Public opposing No-Field preflight enumerates possible native pools, never the
+actual secret denomination. Ix Stone/Poison Tooth timing, Harass/Stone and
+genuinely winner-changing typed allocations retain their existing guards.
+Native Ecaz/Moritani Mirror admission is Advanced only; Basic is unchanged.
+
+The affected rule batch passes **363/363**, with types/lint and build passing.
+**26 actual native programs** cover ten ordinary/marker owner cases, eight
+Stone/Mirror active/prevented lead cases and eight four-policy concealed-pool
+cases, with original Collection and JSON continuation. These are genuine
+setup followed by explicitly conserved board/card/bank staging, not unstaged
+games. All four policies remain minimal legal participants; strategy is deferred.
+The formerly stalled genuine Advanced combined seed20260932 now completes
+**2,424 accepted actions, no rejection and65 JSON continuations**, at turn9.
+
+Original CLI **GQ4FEWNW v8** and human **T78EFNZK v8** admitted fresh native
+setups with real authenticated seats. Human390px **T78EFNZK v22** selected
+Ecaz lead and sealed total5/support2 with Sanya Ecaz. Both seals revealed the
+original No-Field5 into only two available Richese reserves; settlement left
+Ecaz2, Ecaz Tanks3 and Richese Tanks2. Native CHOAM received its original
+one-spice support income, and original Collection returned Ecaz's wallet to30.
+Refreshing retained the actual continuation. No reset, re-deal, public start,
+deployment or new comprehensive assurance campaign.
+
+
 ### Encounter evidence correction — 2 October 2026
 
 Earlier “no combined lead choice” statements were incorrect: the compact

docs/EFFECTIVE_BATTLE_WEAPONS.md

@@ -10,7 +10,7 @@ Tooth and Stone copies each receive their own choice, with the copy before its s
 
 `game/battle-cards.ts` consumes the descriptors for ordinary attacks, self-attacks, Artillery suppression/no-bounty behavior and a shared Lasgun explosion predicate. The authoritative engine and AI's fully known battle calculations use that predicate. Single-card knowledge remains single-card knowledge; no new hidden-hand access was added to AI evaluation. Actual Shield and Shield Snooper trigger explosions; defensive Weirding Way and Portable Snooper do not.
 
-Physical plan IDs, Atreides inspection, Truthtrance commitments, custody, winning card retention and Moritani retention remain physical. The engine admits canonical Mirror only for CHOAM/Richese-deck classic/CHOAM/Richese rosters without combined optional modules; it rejects unsupported setups before commitment. It validates the original and copied Stone casualty possibilities using public force pools and checks reserved physical Mirror custody across saved zones.
+Physical plan IDs, Atreides inspection, Truthtrance commitments, custody, winning card retention and Moritani retention remain physical. Canonical Mirror supports CHOAM/Richese-deck classic/CHOAM/Richese Basic/Advanced rosters and source-clear Advanced native Ecaz/Moritani composition without optional overlays. It rejects unsupported setups before commitment. Original and copied Stone compare native physical undialed counters, including the separate fixed Ecaz remainder; public hypothetical No-Field pools never become the actual secret denomination. Ix Stone/Tooth timing and genuinely winner-changing typed allocations remain guarded.
 
 ## Evidence and boundaries
 

docs/IMPLEMENTATION_STATUS.md

@@ -1,5 +1,59 @@
 # Dune implementation status
 
+## 3 October 2026 — native Richese, No-Field and Stone Occupy composition
+
+Two bounded owners implemented physical Stone normalization and native Richese
+fixtures/zero-marker metadata. One integration owner composed admission,
+selected-plan inspection, original physical revelation, private legal pools,
+controls, four-policy filtering and internal guidance.
+
+The pre-existing combined sample failure was a mandatory Ecaz+Ixians versus
+CHOAM Carthag battle rejected because Richese was elsewhere at the table.
+Native composition replaces that blanket guard, not the battle itself. Original
+Richese reveal ownership persists even when Ecaz supplies the plan; zero markers
+remain original presence through response/Traitor validation and public reveal.
+Stone preflight/resolution subtract the fixed dial offset and count the separate
+physical Ecaz remainder; public hypothetical pools remain authoritative.
+Advanced native Mirror uses the same comparison and original physical cleanup.
+Basic and existing unresolved timing/disclosure/optional-module guards remain.
+
+Affected363/363 and types/lint/build pass. Twenty-six actual native programs
+cover ten owner/marker cases, eight Stone/Mirror lead/cancellation cases and eight
+four-policy private-pool cases, reaching original Collection after JSON reload.
+Fixtures are explicitly controlled conserved board/card/bank positions after
+genuine setup. The actual combined seed20260932 completes2424 accepted actions,
+zero rejection and65 JSON continuations at turn9, versus the prior2353-action
+stall. No new whole-suite/HTTP/storage assurance wave was run.
+
+Original CLI **GQ4FEWNW v8** admits a fresh ready four-seat Advanced
+Ecaz/Richese/Guild/CHOAM setup. Human390px **T78EFNZK v22** uses the same original seat identities and
+fresh admitted setup before a conserved Carthag position. Actual Ecaz lead/
+Sanya Ecaz/total5/support2 controls seal against Guild Representative. Both
+plans reveal the original No-Field5 into only two Richese reserves. Native
+Traitor decline, CHOAM one-spice support income and closing-market continuation
+leave Ecaz2/Tanks3, Richese Tanks2 and original Collection/Ecaz wallet30 after
+refresh. The physical field, variable losses and payer remain distinct.
+
+Corrected the previous mixed Truthtrance log: eight actual programs, not twelve;
+nested/joint cases are regressions, and its phase/positions were explicitly
+staged after genuine setup. Deleted obsolete presentation/wording/wiring pins
+instead of re-pinning changed labels. No reset, public start or deployed claim.
+
+Final native/reference76/76 passes. The new fixture now explicitly declines
+an unrelated optional Face Dance rather than depending on randomized native
+identity draws. Final guide paragraphs are readable at390px after the required
+isolated worker reload; original **T78EFNZK v22** remains at Collection with
+the same relevant owner losses. The old guide chunk was cached in the managed
+browser, so final guide navigation disabled that prior-build cache; production
+cache-upgrade acceptance remains open.
+
+Additional mixed controls **FCGZTEGV v11** actually authored outer OR with an
+inner current-spice>=10/Arrakeen4 AND and alternative Carthag6. Yes at20 spice
+survived a real12-spice bribe, four-force/four-spice Arrakeen shipment and native
+end-movement with wallet4. The promise is fulfilled and exact grouped Yes history
+survives refresh. This is a second human journey, not another program case.
+
+
 ## 3 October 2026 — mixed current-fact/shipment Truthtrance
 
 Two bounded owners supplied the public mixed tree/compiler/matcher (including
@@ -23,11 +77,12 @@ mixed promise as if it must ship; and two workspace type errors
 shipment-only promises retain their original behavior.
 
 Types/lint, the affected truth/ship/discard batch88/88, mixed/reference23/23 and
-build pass. Twelve actual programs cover OR-true-skip, AND-false-ship,
-AND-true-required, OR-false-ship, a nested branch after spending, all four legal
-policies and a second joint pure+mixed promise. Fixtures use genuine base setup
-and conserved rule-unit movement positions; no staged phase or promise was
-fabricated.
+build pass. Eight actual programs cover OR-true-skip, AND-false-ship,
+AND-true-required, OR-false-ship and all four legal policies. Nested branches
+after spending and a second joint pure+mixed promise have rule regressions.
+Fixtures use genuine base setup followed by explicitly staged turn-two
+Shipment and Movement, conserved positions and wallets; accepted native
+Truthtrance actions create the promises.
 
 Human390px **4PVKRRWB v10** authored the actual "hold at least10 spice OR ship4
 to Arrakeen" question, answered Yes, spent all20 spice as a public bribe,
@@ -36,12 +91,13 @@ refresh retained it. Earlier phases, Advanced Guild/other modules, expansion
 shipment modes, other future actions and arbitrary prose enforcement remain
 unfinished. No new assurance campaign, public start or old-game retrofit.
 
-The full offline suite still reports one pre-existing failure unrelated to this
-wave: the `combined` Advanced CLI sample stalls at phase6 when a bot offers an
-Advanced combined-Occupy battle against a Richese/No-Field seat that the engine
-correctly rejects. The same 2353-action failure reproduces at the prior pushed
-checkpoint 0ceb28b, so this wave neither introduced nor hid it. It remains an
-open sample/bot-offer defect for a later combined-Occupy slice.
+The prior full offline run exposed a pre-existing failure unrelated to this
+wave: the `combined` Advanced CLI sample stalled at phase6 because the engine's
+roster guard rejected Ecaz+Ixians versus CHOAM at Carthag merely with Richese
+elsewhere at the table. The same2353-action failure reproduced at0ceb28b.
+This was missing native Occupy composition, not an illegal bot offer, a
+Richese opponent or a new ruling question. The later Richese checkpoint
+repairs it without suppressing the mandatory battle.
 
 Code **cd985c7c34a05057ed98b34838effdbcddb7697d** is pushed.
 [Exact CI37065338944](https://github.com/Quintine/Dune/actions/runs/37065338944)