Compose Guild Cunning with physical Ornithopter movement
Provisionally let either physical card mode replace an earned unused Hajr movement after the second shipment. Keep active group rights separate from actual completed credits and original movement counts. Add v3 original-count receipts while preserving old formats; abandon partial flights through a bound discard suffix before Cunning resumes. Connect persistent controls and minimal legal bot candidates. Validation: frozen13-file125/125, types/lint/build and eight original-action/rendered-table continuations. Public ready/start, cache1/Hajr1 purchases, real worm/alliance/Guild Nexus draw and paid first2/second1 shipments cover both modes, earlier flights and Basic early endings. Eight minimal policy proposals are legal. No frozen repair; bounded continuation review found no concrete defect. New Semuta grammar lacks direct combined claim/capture proof. Wider combinations, complete modes, final assurance and browser/deployed acceptance remain open. No saved-room/reset/restart/deployment operation.
This commit is contained in:
1 parent
7fe84ffbbd
commit
561152d58e
16 files changed
+887
-54
No files matched your search
@@ -1,5 +1,16 @@
|
||||
# Rule decision index
|
||||
|
||||
## Guild Cunning and physical Ornithopter — 18 October 2026
|
||||
|
||||
The printed Nexus grants a second shipment with Hajr required for later movement.
|
||||
Under the standing recommended-composition instruction, the physical card may
|
||||
replace an earned unused Hajr allowance. Completed flight credits preserve actual
|
||||
movement counts; unfinished groups grant no extra credit when abandoned. New
|
||||
v3 original-count receipts retain exact old receipt formats. This is provisional
|
||||
composition, not publisher clarification or complete-combination acceptance.
|
||||
[Canonical contract](NEXUS_GUILD_CUNNING_RUNTIME.md#physical-ornithopter-composition--18-october-2026).
|
||||
|
||||
|
||||
Updated 18 October 2026. This is the authoritative navigation index for existing decisions, not a replacement rulebook or a new ruling. Detailed linked contracts retain their source citations and exact supported boundaries. Runtime follow-ups supersede historical absence claims; passing tests establish software behavior, not publisher authority.
|
||||
|
||||
## Fremen Nexus and Great Maker riding — 18 October 2026
|
||||
|
||||
Reference in new issue
Block a user