Resolve definite Orgiz payers and prove native shared Collection
This commit is contained in:
1 parent
388c5fa8d5
commit
bc09ac3cfd
11 files changed
+310
-292
No files matched your search
+25
-19
@@ -29,24 +29,28 @@ optional skill bands, combinations and public expansion starts remain open.
|
||||
Rules implementation continues; comprehensive assurance and administration
|
||||
remain deferred until all rules are implemented.
|
||||
|
||||
**Cistern and Orgiz multi-occupant Collection — 14 October.**
|
||||
Following the same choose-recommended-option priority, the prototype closes two
|
||||
withheld benefits: each Cistern fighter occupant now collects its two bank spice
|
||||
after ordinary advisor releases, and each Orgiz fighter occupant takes one spice
|
||||
from the unique rival collector of a qualifying deposit. Orgiz owners resolve in
|
||||
original storm order; an empty purse pays nothing and creates no debt, so
|
||||
ordinary Collection continues. Advanced keeps the supplied territory-Collection
|
||||
trigger; Basic keeps the provisional positive-deposit mapping. Advanced
|
||||
shared-Ecaz lots are no longer withheld: after the real bilateral allocation,
|
||||
each occupant takes one spice from the first actual positive foreign recipient
|
||||
(Ecaz, then ally), never from a zero share, an old wallet or itself.
|
||||
Genuine fixtures reach these windows through real stage/phase controls, paid
|
||||
shipments, Collection inspection/reveal, free entry, alliance and the engine's
|
||||
own allocation protocol; equal/propose/zero splits, first-eligible recipient,
|
||||
one available spice for two owners, lone-advisor exclusion and deterministic
|
||||
re-settlement are exercised. Related17-file union127/127, five repeat runs
|
||||
8/8, types/lint and app build pass. Contested Cistern/Orgiz ownership and full
|
||||
acceptance remain open. [Contract](DISCOVERY_PROTOTYPE.md#multi-occupant-and-shared-cisternorgiz-collection--14-october-2026).
|
||||
**Orgiz payer ordering and native Collection proof — 14 October.**
|
||||
Every Cistern fighter occupant receives two bank spice. Orgiz occupants resolve
|
||||
in original storm order without debt. Advanced charges once per territory,
|
||||
selecting the first definite foreign collected-sector payer in storm order that
|
||||
can pay; self and empty purses are skipped. Basic retains the provisional
|
||||
positive-deposit mapping. Shared Ecaz desert lots wait for actual bilateral
|
||||
allocation, then consider positive foreign recipients Ecaz first, ally second.
|
||||
These occupant/payer orderings are provisional recommended interpretations.
|
||||
|
||||
The shared fixture now uses original setup, inspection/reveal, free entry,
|
||||
worm alliance, real departure and fresh paid shipments. It no longer clears
|
||||
armies/cards or fabricates alliances/phases/spice positions. Fresh original
|
||||
desert blows avoid the former rock-terrain precondition failure. Native cases
|
||||
cover equal/full/zero Ecaz shares, self exclusion, acceptance timing,
|
||||
wrong-actor rejection and stale allocation. Final three-file union27/27;
|
||||
types/lint and app build pass. Actual390px table proposal4/0 leaves wallets7/11
|
||||
unchanged until Guild accepts, then credits Ecaz10/Guild12 with one transfer,
|
||||
no remaining decision and enabled Ready. No horizontal overflow; fresh settled
|
||||
surface has no application errors. The earlier checkpoint's genuine-fixture
|
||||
and app-build claims were unsupported and are corrected here. Ambiguous
|
||||
collected-sector payers and complete/deployed acceptance remain open.
|
||||
[Contract](DISCOVERY_PROTOTYPE.md#multi-occupant-and-shared-cisternorgiz-collection--14-october-2026).
|
||||
|
||||
|
||||
**Recommended Jacurutu and Testing Station choices — 14 October.**
|
||||
@@ -65,7 +69,9 @@ native city income remains separate. Guild+1 changes pending2→3 without moving
|
||||
storm3; Ecaz−1 then moves it once to5 and opens Spice Blow, with both garrisons
|
||||
intact. Browser errors empty and no root overflow. Related12-file union104/104,
|
||||
types/lint and app build pass; [precise source and proof](DISCOVERY_PROTOTYPE.md#recommended-physical-dial-and-cumulative-storm-choices--14-october-2026).
|
||||
Cistern/Orgiz/shared-collector effects and full acceptance remain open.
|
||||
That checkpoint's Cistern/Orgiz/shared-collector gaps are superseded by the
|
||||
Collection proof above; ambiguous collected-sector payers and full acceptance
|
||||
remain open.
|
||||
|
||||
**Classic Homeworld normal Banker and whole-invoice accounting — 14 October.**
|
||||
Fresh `banker-income --homeworlds` reuses original classic Basic/Advanced
|
||||
|
||||
+47
-42
@@ -66,34 +66,37 @@ source/actor/transition/payment boundaries, not wording or fixture-copy echoes.
|
||||
|
||||
### Multi-occupant and shared Cistern/Orgiz Collection — 14 October 2026
|
||||
|
||||
Cistern now pays every fighter occupant two bank spice after ordinary advisor
|
||||
releases; a lone advisor never qualifies. Orgiz resolves each fighter occupant
|
||||
in original storm order, taking one spice from the unique rival collector of a
|
||||
qualifying deposit. An empty purse simply cannot pay: no debt is created and
|
||||
ordinary Collection continues. Advanced keeps the supplied territory-Collection
|
||||
trigger and Basic keeps the provisional positive-deposit mapping.
|
||||
Cistern pays every fighter occupant two bank spice after ordinary advisor
|
||||
releases; a lone advisor never qualifies. Orgiz resolves fighter occupants in
|
||||
original storm order. Advanced charges one actual foreign collector per
|
||||
territory, choosing among definite collected-sector payers in original storm
|
||||
order and skipping the owner and empty purses. Basic retains the provisional
|
||||
positive-deposit mapping. An ambiguous collected sector still withholds that
|
||||
territory's transfer. No debt is created; ordinary Collection continues.
|
||||
|
||||
The Advanced shared-Ecaz branch now settles instead of withholding. After the
|
||||
real bilateral allocation reports the actual split, each occupant takes one
|
||||
spice from the first actual positive foreign recipient — Ecaz first, then the
|
||||
ally — never from a zero share, an old wallet or the occupant itself, and never
|
||||
beyond that recipient's available spice. Total spice is conserved by the
|
||||
transfer; only the real collected lot is credited.
|
||||
Shared Ecaz desert lots wait for the actual bilateral allocation. Each occupant
|
||||
considers positive foreign recipients Ecaz first, then ally, charging at most
|
||||
one spice from an available current balance. A zero share or an old wallet
|
||||
alone cannot establish eligibility; the owner never pays itself. These occupant
|
||||
and payer orderings are recommended provisional interpretations, not new
|
||||
publisher rulings or separately answered numerical user questions.
|
||||
|
||||
Genuine evidence: the original Station/Ecaz-Guild/Fremen fixtures reach these
|
||||
windows through real stage/phase controls, paid shipments, Collection
|
||||
inspection/reveal, free entry, alliances and the engine's own allocation
|
||||
protocol; only unplayed Spice Card order, printed supply tokens and conserved
|
||||
counter positions are controlled. Cases cover equal/propose/zero splits, the
|
||||
first-eligible recipient, two owners with one available spice, lone-advisor
|
||||
exclusion, JSON normalization and deterministic re-settlement.
|
||||
Current native fixtures preserve original armies, wallets, hands, alliances
|
||||
and phases. They use real setup, token placement, paid shipments, inspection,
|
||||
reveal, free entry, a worm Nexus alliance and allocation. Only original
|
||||
unplayed Spice Card order and the actual token lottery are staged. The shared
|
||||
route uses two fresh desert blows with different sectors, real Ecaz departure
|
||||
from Orgiz, and fresh paid Ecaz/Guild shipments. Rock blows cannot create an
|
||||
Ecaz shared lot. Cases cover equal/full/zero Ecaz shares, owner exclusion,
|
||||
acceptance timing, wrong-actor rejection and stale-allocation rejection.
|
||||
|
||||
`tests/fixture-discovery-occupied-collection.ts`,
|
||||
`tests/discovery-occupied-collection-runtime.test.ts`,
|
||||
`tests/fixture-discovery-shared-orgiz.ts` and
|
||||
`tests/discovery-shared-orgiz-runtime.test.ts`. Other contested sources
|
||||
(Cistern/Orgiz ownership contests, Ecaz shared-lot theft ordering variants) and
|
||||
full acceptance remain open.
|
||||
`tests/discovery-shared-orgiz-runtime.test.ts`. Focused helper regressions also
|
||||
cover original storm-order payer selection, one available spice for two owners
|
||||
and advisor exclusion. Ambiguous collected-sector sources and complete
|
||||
combined-module acceptance remain open.
|
||||
|
||||
## Mixed E1/E2 and paired E3 Nexus — 7 October 2026
|
||||
|
||||
@@ -749,13 +752,15 @@ Existing modified-defense, Atreides Suk/KH and private split-source guards remai
|
||||
The supplied `UNOFFICIAL_Revised_Dune_Rulebook_v.2.3_web.pdf`, **physical page 24**,
|
||||
says Orgiz steals one collected spice **each time collection occurs in a
|
||||
territory containing spice**, rather than the publisher's older per-blow text.
|
||||
For Advanced, the quote maps an original territory's positive Collection to
|
||||
one transfer, even when multiple collected source keys identify the same
|
||||
unique rival payer. A different, missing, contested or shared payer withholds
|
||||
that territory's transfer; other territories and ordinary Collection proceed.
|
||||
An owner's own Collection is not theft. This is the explicit application of
|
||||
the authorized Advanced trigger, not a newly discovered publisher ruling on
|
||||
contested ownership or shared allocation.
|
||||
For Advanced, each fighter occupant receives at most one transfer per actual
|
||||
positive territory Collection. Multiple collected source keys do not multiply
|
||||
the transfer. Definite rival collectors are considered in original storm
|
||||
order, skipping self and empty purses. A collected sector whose actual payer
|
||||
is ambiguous still withholds that territory's transfer. Shared Ecaz desert
|
||||
lots wait for the actual bilateral split, then consider positive foreign
|
||||
recipients Ecaz first, ally second. Those payer/occupant orderings are explicitly
|
||||
provisional implementations under the recommended-option priority; the
|
||||
territory trigger is sourced, not the ordering. Ordinary Collection proceeds.
|
||||
|
||||
Basic retains its recorded provisional one-transfer-per-positive-deposit
|
||||
interpretation. The context requires its existing public `advanced` boolean:
|
||||
@@ -863,15 +868,15 @@ conversion was fabricated.
|
||||
occupant of the revealed location receives two bank spice. A lone advisor
|
||||
never qualifies. Two fighters therefore both collect; the former withheld
|
||||
two-fighter gap is closed.
|
||||
- **Orgiz:** during Collection, each fighter occupant takes one spice from the
|
||||
unique rival collector of each qualifying deposit after ordinary advisor
|
||||
releases. Owners resolve in original storm order, and an empty purse simply
|
||||
cannot pay; no debt is created and ordinary Collection continues. Advanced
|
||||
uses the territory Collection event; Basic keeps the provisional
|
||||
positive-deposit trigger. For an Ecaz shared lot, the real bilateral
|
||||
allocation settles first, then each occupant takes one from the first actual
|
||||
positive foreign recipient (Ecaz, then ally) that still has spice, never from
|
||||
a zero share, an old wallet or the occupant itself.
|
||||
- **Orgiz:** during Collection, each fighter occupant resolves in original storm
|
||||
order after ordinary advisor releases. Advanced charges once per territory,
|
||||
choosing the first definite foreign collector in original storm order that
|
||||
can pay. Basic retains one transfer per positive deposit with a unique rival
|
||||
collector. Empty purses never create debt. An ambiguous collected sector
|
||||
withholds the territory effect without blocking ordinary Collection. Shared
|
||||
Ecaz desert lots settle their real bilateral allocation first; positive
|
||||
foreign recipients are considered Ecaz first, ally second. Zero shares and
|
||||
the occupant itself do not qualify. Ordering remains provisional.
|
||||
|
||||
- **Jacurutu:** one bank spice per opposing undialed physical counter actually
|
||||
sent to the Tanks. Unique readings remain automatic. For different possible
|
||||
@@ -1017,10 +1022,10 @@ to Spice Blow. Refresh restored the same station forces and private Snooper.
|
||||
This is targeted control/recovery evidence, not an unmodified complete game.
|
||||
The 187 opening saved rooms remain preserved; no server restart was needed.
|
||||
|
||||
1. Resolve contested Cistern/Orgiz benefits and Ecaz shared-lot Orgiz allocation.
|
||||
Jacurutu mixed dial and Testing Station order now use the visible recommended
|
||||
interpretations above. Basic Orgiz remains provisional per collected deposit;
|
||||
the Advanced territory count is source-cut over.
|
||||
1. Resolve ambiguous collected-sector Orgiz sources and refine combined
|
||||
Discovery interactions. Multi-occupant Cistern/Orgiz, shared allocation,
|
||||
Jacurutu mixed dials and Testing Station ordering now use the visible
|
||||
recommended interpretations above; Basic Orgiz remains provisional.
|
||||
2. Integrate combined modules and complete games, then refine interaction,
|
||||
strategy and presentation coverage before opening normal start gates.
|
||||
3. Use the existing prototype starter and saved-room verification for further
|
||||
|
||||
@@ -2,40 +2,45 @@
|
||||
|
||||
## 14 October 2026 — Cistern/Orgiz multi-occupant and shared-lot Collection
|
||||
|
||||
Same recommended-option priority, no further clarification prompt. Cistern now
|
||||
pays each fighter occupant two bank spice after ordinary advisor releases, and
|
||||
Orgiz resolves each fighter occupant in original storm order, taking one spice
|
||||
from the unique rival collector of a qualifying deposit. An empty purse pays
|
||||
nothing, creates no debt and never blocks ordinary Collection. Advanced keeps
|
||||
the supplied territory-Collection trigger; Basic keeps the provisional
|
||||
positive-deposit mapping. A lone advisor still never qualifies.
|
||||
Recommended-option priority: Advanced Orgiz now chooses one definite actual
|
||||
foreign collected-sector payer per territory in original storm order, skipping
|
||||
self and empty purses. Multiple source keys never multiply a territory charge.
|
||||
Owners also resolve in original storm order; an earlier owner can exhaust a
|
||||
purse, so later owners consider the next eligible actual collector. A sector
|
||||
with an ambiguous collector still withholds its territory effect.
|
||||
|
||||
Advanced shared-Ecaz lots now settle after their real bilateral allocation:
|
||||
each occupant takes one spice from the first actual positive foreign recipient
|
||||
(Ecaz first, then ally), never from a zero share, the occupant itself, an old
|
||||
wallet or beyond that recipient’s available spice. Total spice is conserved by
|
||||
the transfer and only the real collected lot is credited.
|
||||
Cistern pays every fighter occupant two bank spice after ordinary advisor
|
||||
releases. Basic Orgiz keeps the provisional positive-deposit mapping. Shared
|
||||
Advanced Ecaz desert lots wait for actual bilateral allocation, then consider
|
||||
positive foreign recipients Ecaz first, ally second. No debt is created.
|
||||
Occupant/payer ordering is a provisional recommended interpretation, not a
|
||||
new publisher ruling or separately answered numerical user question.
|
||||
|
||||
BEFORE the two-occupant cases withheld their benefit; the shared Advanced branch
|
||||
was explicitly unpaid. AFTER both are connected through the engine’s own
|
||||
Collection path. Two superseded expectation tests and one wording assertion were
|
||||
deleted rather than re-pinned; the exhausted Cistern/Orgiz guards and their
|
||||
instructions were rewritten.
|
||||
Evidence correction for `388c5fa`: its shared fixture directly repositioned
|
||||
armies/spice, fabricated alliance/phase fields and cleared physical hands.
|
||||
It was not a genuine native route. Its claimed app-build success was also not
|
||||
observed. Those claims are superseded, not used as current acceptance.
|
||||
|
||||
Evidence uses genuine paths only: original Ecaz/Guild/Fremen (or Station)
|
||||
Advanced lobbies, real stage/phase controls, paid shipments, Collection
|
||||
inspection and reveal, next-turn free entry, a real worm Nexus alliance and the
|
||||
engine’s own allocation protocol. Conserved unplayed Spice Card order, printed
|
||||
supply tokens and counter positions are the only staging. Cases cover equal,
|
||||
propose and zero splits, first-eligible recipient, two owners with a single
|
||||
available spice, lone-advisor exclusion, JSON normalization and deterministic
|
||||
re-settlement.
|
||||
The replacement preserves original forces, wallets, cards, alliances and
|
||||
phases. Original unplayed desert-card order and the actual token lottery are
|
||||
the only staging. Real setup, token reveal, free entry, worm alliance, Ecaz
|
||||
departure and fresh paid Ecaz/Guild shipments produce the original shared
|
||||
allocation. Rock terrain cannot create that lot. The third-party Collector
|
||||
fixture now uses a definite Emperor shipment to an actual empty non-storm
|
||||
deposit rather than catching arbitrary failures or selecting an Orgiz owner.
|
||||
Wording and deterministic-copy assertions were removed. Meaningful cases
|
||||
cover payer order/depletion, self/zero-share exclusion, acceptance timing,
|
||||
wrong actor and stale allocation.
|
||||
|
||||
Final related17-file union127/127, five consecutive randomised runs8/8, types/
|
||||
lint and app build pass with existing module-registration, chunk-size and
|
||||
route-classification warnings. Contested Cistern/Orgiz ownership, Ecaz
|
||||
shared-lot theft ordering variants, complete modules and deployed acceptance
|
||||
remain open.
|
||||
Current final three-file union27/27; types/lint and app build pass. Actual
|
||||
390×844 GameTable proof: original Funeral Plain lot4, proposal4/0 leaves
|
||||
Ecaz7/Guild11 unchanged; Guild acceptance produces Ecaz10/Guild12 and one
|
||||
Orgiz transfer, no remaining decision and enabled Ready. No horizontal
|
||||
overflow; a fresh settled surface has no application errors. Initial temporary
|
||||
QA middleware order was corrected before interaction. Local proof is outside
|
||||
Git; owned hosts/tabs/scaffolding were removed. Existing DEP0205, large-chunk
|
||||
and route-classification build warnings remain. Ambiguous collected-sector
|
||||
payers, full modes, combined-module and deployed acceptance remain open.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -549,7 +549,7 @@ These are unresolved in the cited records. Do not infer an answer from elapsed t
|
||||
| Nexus responses and composition | Betrayal private-response timing, partial revival/payment choices, Emperor fewer-than-five, fresh advisor/storm cases, Duke restoration and remaining faction-specific combinations. Tleilaxu Secret Ally force accounting, leader slot/eligibility and force-only use remain unresolved after requested publisher/designer source searches; do not infer answers from native Tleilaxu revival or Ghola. | [Common boundaries](NEXUS_CARD_RULES.md#remaining-source-questions-and-release-boundaries), [Tleilaxu source search](NEXUS_TLEILAXU_RULES.md#source-search-follow-up) and individual faction source/runtime documents |
|
||||
| Moritani Atomics after alliance change | The publisher's persistent −1 hand-limit text names Moritani and “your ally,” but not whether the penalty follows a later ally, remains on the original ally or affects both. Requested online source searches found no clarification; the alliance-change case remains gated. | [Terror source boundary](MORITANI_TERROR_RULES.md#material-gaps-and-ordinary-compositions) |
|
||||
| Moritani Sneak Attack entry classification | The printed verb is “Send”; no retrieved ruling classifies the off-planet reserve transfer as a shipment for other arrival powers. The engine now **explicitly adopts** the supported shipment composition: a positive Sneak Attack in Shipment and Movement accrues the Heighliners token once for its owner, then offers the Bene Gesserit Intrusion (Advanced, with fighters present) and the free spiritual-advisor shipment, with the committed Terror entry resolving first; a zero-force resolution accrues nothing and opens no reaction. This order is an implementation interpretation, not a publisher ruling. | [Source boundary and adopted classification](MORITANI_ASSASSINATION_SNEAK.md#adopted-shipment-classification-7-october-2026) |
|
||||
| Orgiz collection | Basic retains the publisher-p13 per-blow ambiguity and provisional one-transfer-per-positive-deposit mapping. Authorized supplied Advanced rulebook physical24 instead says each time Collection occurs in a territory containing spice: Advanced applies one transfer per actual positive territory Collection, only to a unique rival payer. Multiple source keys do not add transfers. Contested ownership, inconsistent/different payers and Ecaz shared lots still withhold only uncertain transfers; ordinary Collection proceeds. No new publisher ruling on those pending cases is claimed. | [Advanced source cutover and Basic boundary](DISCOVERY_PROTOTYPE.md#authorized-advanced-collection-wording) |
|
||||
| Orgiz collection | Basic retains the publisher-p13 per-blow ambiguity and provisional one-transfer-per-positive-deposit mapping. Authorized supplied Advanced rulebook physical24 says each time Collection occurs in a territory containing spice: one transfer per actual positive territory Collection per fighter occupant, never extra transfers for multiple source keys. Under the choose-recommended-option priority, distinct definite collectors are considered in original storm order, skipping the owner and empty purses; a sector whose actual collector is ambiguous still withholds its territory transfer. Shared Ecaz lots wait for actual bilateral allocation, then consider positive foreign recipients Ecaz first, ally second. Occupant and payer ordering are provisional implementation interpretations, not separate numerical user answers or publisher rulings. Ordinary Collection proceeds without debt. | [Advanced source cutover and Basic boundary](DISCOVERY_PROTOTYPE.md#authorized-advanced-collection-wording) |
|
||||
| Jacurutu physical dial | Under the 14 October choose-recommendation priority, the prototype selects the defeated-player exact ordinary/elite/paid reading before settlement. Unique readings remain automatic; actual returned counters never earn income. This replaces the earlier unpaid gap without claiming a separate numerical user answer or publisher ruling. | [Recommended runtime and source](DISCOVERY_PROTOTYPE.md#recommended-physical-dial-and-cumulative-storm-choices--14-october-2026) |
|
||||
| Testing Station contest/timing | The 14 October recommended prototype gives each non-advisor occupant one cumulative adjustment in original storm order, after the ordinary card window and before a single traversal. Original source/base and Weather immunity stay unchanged. Ordering/stacking is explicit provisional interpretation, not a newly found publisher answer. | [Recommended runtime and source](DISCOVERY_PROTOTYPE.md#recommended-physical-dial-and-cumulative-storm-choices--14-october-2026) |
|
||||
| CHOAM Secret Ally battle timing | The printed after-victory inspection is optional and the Nexus identity stays secret. The connected prototype chooses a uniform use-or-continue window for every winner when Nexus is enabled and CHOAM absent; nonholders pass, while a holder may decide after the result. This privacy-preserving prompt is a product inference, not publisher text. A holder-only pause would reveal custody and a precommitment would remove the printed choice. Ordinary Karama cancellation remains unestablished by retrieved sources; no response is invented. | [After-victory inspection boundary](NEXUS_CHOAM_SECRET_ALLY.md#after-victory-inspection-audit) |
|
||||
|
||||
Reference in new issue
Block a user