Support Truthtrance No-Field shipment promises
Verify and publish checkpoint container / container (push) Canceled after 0s
Verify and publish checkpoint container / container (push) Canceled after 0s
This commit is contained in:
1 parent
9ab9b9a613
commit
7fccd62814
16 files changed
+658
-32
No files matched your search
@@ -2,6 +2,26 @@
|
||||
|
||||
Original checkpoint, 7 September 2026; Advanced follow-up, 13 September 2026. The [14 September compound follow-up](COMPOUND_SHIPMENT_PROMISES.md) adds shipment-only AND/OR while retaining the boundaries below. This implements a bounded reserve-shipment future-action predicate. It does not certify complete Truthtrance, Advanced play or expansion interactions, and opens no new mode gate.
|
||||
|
||||
## Owned No-Field shipment question — 29 October 2026
|
||||
|
||||
**Prototyped / Partial.** A shipment expression addressed to Richese may now
|
||||
ask whether its own concealed No-Field will be shipped from reserves this turn,
|
||||
optionally to a selected printed territory or sector. The public question and
|
||||
receipt contain no token identity or denomination. A Yes requires a qualifying
|
||||
shipment while it remains possible; a No forbids that proposition and can
|
||||
still allow a different destination. The original physical-force conditions
|
||||
continue to count actual physical counters, not the concealed marker. AND/OR
|
||||
conditions refer to one shipment and share the existing feasibility search.
|
||||
|
||||
The owned completion may reveal an already-deployed marker before shipping a
|
||||
different legal one. A successful declaration does not fulfill the answer until
|
||||
the real shipment commits; opposing prevention can release an impossible Yes.
|
||||
This composes the printed No-Field shipment in the CHOAM/Richese rules, p. 6,
|
||||
with the existing provisional Truthtrance fulfillment and release policy. It
|
||||
does not cover allied marker grants, Homeworld routes, marker shipments with
|
||||
physical companions, or arbitrary prose. Those future profiles need their own
|
||||
completion search before being enabled.
|
||||
|
||||
The former Advanced Guild exclusion is superseded by the
|
||||
[18 October native Guild composition](#advanced-guild-interception-and-rates--18-october-2026).
|
||||
The [24 October waiting-turn follow-up](#same-phase-waiting-respondents--24-october-2026) supersedes the active-only timing boundary. The [earlier Basic phase follow-up](#earlier-basic-phases--24-october-2026) extends current-turn timing before Movement; the [26 October Advanced extension](#earlier-classic-advanced-phases--26-october-2026) adds bare classic Advanced while retaining earlier module fences. The [native-faction follow-up](#native-factions-and-owned-choam-opening--26-october-2026) adds native early scope and owned CHOAM income. Earlier scope descriptions and verification totals remain historical.
|
||||
|
||||
Reference in new issue
Block a user