Connect Harkonnen Nexus to Ecaz Occupy
Verify and publish checkpoint container / container (push) Successful in 11m17s
Verify and publish checkpoint container / container (push) Successful in 11m17s
This commit is contained in:
1 parent
007508185e
commit
a2e7029a72
12 files changed
+529
-19
No files matched your search
+11
-2
@@ -17,11 +17,20 @@ open mode gates.
|
||||
|
||||
## Current checkpoint and work
|
||||
|
||||
**Ecaz Occupy and canceled Traitor reveal — 16 November. Prototyped /
|
||||
Partial.** Standalone Advanced Ecaz Occupy can bind the Harkonnen Nexus
|
||||
reaction with either coalition lead and Harkonnen on either side. A Harkonnen
|
||||
Traitor revealed before Nexus cancellation provisionally still prevents a
|
||||
same-battle Moritani assassination. Simultaneous replacements, a real legacy
|
||||
pending-source continuation, wider modules and complete games remain open.
|
||||
Sixteen related unit files pass 107 cases.
|
||||
[Scope](NEXUS_HARKONNEN_RULES.md#ecaz-occupy-and-revealed-moritani-traitor--16-november-2026).
|
||||
|
||||
**Advanced standalone Ecaz/Moritani Harkonnen Nexus — 16 November.
|
||||
Prototyped / Partial.** Fresh Nexus-only Advanced games with Harkonnen and one
|
||||
Ecaz or Moritani faction can use the existing declared-Traitor cancellation and
|
||||
delayed private replacement. Ecaz Occupy battles retain their native call but
|
||||
do not yet offer this reaction. Simultaneous Moritani replacement, wider module
|
||||
delayed private replacement. The newer checkpoint above adds Ecaz Occupy
|
||||
support. Simultaneous Moritani replacement, wider module
|
||||
combinations, complete games and deployment remain open. Eleven related unit
|
||||
files pass 73 cases, including Emperor purchase and Revival preservation.
|
||||
[Scope](NEXUS_HARKONNEN_RULES.md#advanced-standalone-ecaz-or-moritani--16-november-2026).
|
||||
|
||||
@@ -2,6 +2,26 @@
|
||||
|
||||
Source audit, 10 September 2026. This is a rules contract, not a runtime completion claim. The [common Nexus lifecycle](NEXUS_CARD_RULES.md) and existing expansion release gates still apply. The pending reaction-privacy question remains unresolved; this audit does not authorize a Betrayal reaction policy.
|
||||
|
||||
## Ecaz Occupy and revealed Moritani Traitor — 16 November 2026
|
||||
|
||||
**Prototyped / Partial.** The standalone Advanced Ecaz/Harkonnen Nexus
|
||||
reaction now binds the actual Occupy coalition profile and lead. A Harkonnen
|
||||
co-side voter calls directly, including when Ecaz owns the plan; an external
|
||||
allied call retains its native Karama response. The public test journey uses
|
||||
conserved staged forces and traitors, a real Nexus draw, battle, Use/Pass and
|
||||
Mentat continuation for both leads and Harkonnen on either side. Previously
|
||||
opened Basic pending sources retain their original source shape; the old-shape
|
||||
helper case passes, while a real saved pending continuation remains unverified.
|
||||
|
||||
The authorized revised Advanced source, physical page 35, requires no Traitor
|
||||
to have been revealed before Moritani's Assassinate Leaders. The provisional
|
||||
combined interpretation keeps that public fact when Harkonnen's subsequent
|
||||
Nexus cancellation removes the call's battle outcome. An actual normal
|
||||
Moritani loss confirms no assassination offer after this reveal; a no-reveal
|
||||
control still offers it. The source does not explicitly adjudicate this
|
||||
combination. Simultaneous Harkonnen/Moritani Mentat replacements, broader
|
||||
modules, complete games and deployment remain open.
|
||||
|
||||
## Advanced standalone Ecaz or Moritani — 16 November 2026
|
||||
|
||||
**Prototyped / Partial.** Fresh Advanced Nexus-only starts with Harkonnen,
|
||||
@@ -10,8 +30,8 @@ existing Betrayal reaction. Its native call, provisional neutral acknowledgement
|
||||
physical Traitor return and private Mentat replacement retain their existing
|
||||
continuation. Older games are not restamped. Ecaz Loyalty is excluded from the
|
||||
Traitor census; Moritani's retired identities remain outside the physical deck.
|
||||
In an Ecaz Occupy battle, the native call continues without a Betrayal offer:
|
||||
the existing source does not yet bind coalition voters. When Harkonnen and
|
||||
At that checkpoint Ecaz Occupy retained its native call without a Betrayal
|
||||
offer; the newer section above records the subsequent coalition support. When Harkonnen and
|
||||
Moritani replacements are both due, Harkonnen's draw precedes Moritani's;
|
||||
this online ordering is provisional and simultaneous obligations require
|
||||
further runtime proof. Leader Skills, Homeworlds, other modules, paired/mixed
|
||||
|
||||
+12
-2
@@ -1,10 +1,20 @@
|
||||
# Rule decision index
|
||||
|
||||
## Ecaz Occupy and canceled Traitor reveal — 16 November 2026
|
||||
|
||||
The existing provisional Harkonnen reaction timing extends to standalone
|
||||
Advanced Ecaz Occupy, preserving direct co-side calls. Under the provisional
|
||||
combined interpretation of the supplied Advanced PDF physical page 35,
|
||||
canceling a publicly revealed Traitor's battle effect does not undo the reveal
|
||||
for Moritani's Assassinate Leaders condition. Neither interpretation is a new
|
||||
publisher ruling.
|
||||
[Scope](NEXUS_HARKONNEN_RULES.md#ecaz-occupy-and-revealed-moritani-traitor--16-november-2026).
|
||||
|
||||
## Advanced standalone E3 Harkonnen Nexus — 16 November 2026
|
||||
|
||||
The existing provisional native-counter-first acknowledgement extends to
|
||||
Nexus-only Advanced Ecaz or Moritani starts. Ecaz Occupy remains outside the
|
||||
reaction; simultaneous Harkonnen and Moritani replacements currently draw in
|
||||
Nexus-only Advanced Ecaz or Moritani starts. The newer section above adds Ecaz
|
||||
Occupy; simultaneous Harkonnen and Moritani replacements currently draw in
|
||||
that order, provisionally, pending combined runtime evidence.
|
||||
[Scope](NEXUS_HARKONNEN_RULES.md#advanced-standalone-ecaz-or-moritani--16-november-2026).
|
||||
|
||||
|
||||
Reference in new issue
Block a user