Support Basic allied No-Field transit
Verify and publish checkpoint container / container (push) Canceled after 0s

This commit is contained in:
Quintine committed 2026-10-28 22:44:26 +11:00
1 parent 50c6201d33
commit 8083598cef
9 files changed
+282 -14

No files matched your search

+16 -1
View File
@@ -104,6 +104,21 @@ ending warnings with enabled finish. No broad suite, recovery campaign or
deployed acceptance was run.
## Basic own No-Field transit — 28 October 2026
**Prototyped / Partial.** Richese may ship its own single concealed No-Field
into an eligible ally-occupied territory, then move it out during its turn.
Storm and stronghold capacity remain in force. The owner sees a warning without
revealing the token value to other players. If the marker remains beside the
ally at turn end, the provisional no-departure policy reveals it, places up to
its value from available reserves and sends those newly materialized forces to
Tanks. A zero marker reveals without casualties. Physical visitors use the
same pre-arrival baseline; an earlier voluntary reveal is not repeated.
The source FAQ permits allied shipment transit and the Richese rules count a
concealed marker as one force; their combination and no-exit consequence are
provisional. Allied No-Field use, paired markers, paid companions and other
transport compositions remain separate.
## Basic ordinary allied shipment prototype — 8 October 2026
The content-first Basic pass connects the FAQ's ordinary physical
@@ -131,7 +146,7 @@ co-occupation deadlines still resolve separately. AI prioritizes available
native departures and does not retain a stronghold sentinel from a
visiting group.
Concealed and allied No-Field arrivals, mobile/homeworld transports and
Allied No-Field arrivals, mobile/homeworld transports and
optional arrival compositions are not expanded by the Basic prototype.
Advanced ordinary physical entry is connected in the follow-up above.
Refinement of interrupted and mixed-cohort interactions remains later work.