Support Truthtrance No-Field shipment promises
Verify and publish checkpoint container / container (push) Canceled after 0s

This commit is contained in:
Quintine committed 2026-10-29 10:07:00 +11:00
1 parent 9ab9b9a613
commit 7fccd62814
16 files changed
+658 -32

No files matched your search

+13
View File
@@ -17,6 +17,19 @@ open mode gates.
## Current checkpoint and work
**Truthtrance and native No-Field shipment — 29 October. Prototyped / Partial.**
The shipment question builder can ask whether Richese will ship its own
No-Field this turn, optionally to a specific territory or sector, and combine
that with physical shipment conditions. Token identity and denomination remain
private; existing physical minima retain their meaning. Owner-only guidance
can reveal an existing marker before a different eligible marker ships. Real
actions exercise Yes/No, zero marker, prevention/retry, invalid target and all
four minimal bot profiles; some physical cards and an existing marker are
staged with conserved custody. Twelve related files pass 97 cases; types/lint
and production build pass. Allied grants, Homeworlds, physical companions,
other combinations and deployed acceptance remain open.
[Scope](TRUTHTRANCE_SHIPMENT_PROMISES.md#owned-no-field-shipment-question--29-october-2026).
**Basic Ecaz/Moritani Richese interactions — 29 October. Prototyped / Partial.**
Previously supported clean No-Field interruptions now work with selected
Ecaz/Moritani factions and their native deck. Semuta also receives Sabotage,
+9
View File
@@ -1,5 +1,14 @@
# Rule decision index
## Truthtrance and a native No-Field shipment — 29 October 2026
The structured shipment question can explicitly refer to Richese's owned
No-Field, without disclosing its identity or value. It shares the existing
current-turn feasibility and fulfillment policy with physical shipment claims;
physical minima do not count the marker. Other marker shipment sources and
arbitrary commitments remain outside this first version.
[Scope](TRUTHTRANCE_SHIPMENT_PROMISES.md#owned-no-field-shipment-question--29-october-2026).
## Basic Ecaz/Moritani Richese interactions — 29 October 2026
Supported clean No-Field reveal interruptions extend to the native Ecaz and
+20
View File
@@ -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.