Allow Richese No-Field reveal during Basic openings and markets
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
ac7db3cb35
commit
0d55333d5d
9 files changed
+617
-3
No files matched your search
@@ -17,6 +17,19 @@ open mode gates.
|
||||
|
||||
## Current checkpoint and work
|
||||
|
||||
**Basic Richese No-Field interruptions — 29 October. Prototyped / Partial.**
|
||||
In supported Basic native Ix/CHOAM games the owner can reveal a deployed
|
||||
No-Field during an Ix opening and selected economic decisions without replacing
|
||||
the pending parent. Genuine setup, paid shipment, the next opening, Richese
|
||||
cache/unbid and CHOAM market/trade choices exercise physical reveal and native
|
||||
continuation; the owner control and private commitment boundary have focused
|
||||
checks. Five related files pass 25 cases; type checking, lint and the production
|
||||
build pass. Current-turn Truthtrance history,
|
||||
active commitments, older saves without public history, nested responses,
|
||||
arrival children and optional modules remain outside this slice. An automatic
|
||||
parent can still finish before a human uses the control; deployed acceptance
|
||||
remains open. [Scope](RICHESE_NO_FIELD_RULES.md#basic-phase-opening-and-economic-interruptions--29-october-2026).
|
||||
|
||||
**Basic Fremen ally revival scheduling — 29 October. Prototyped / Partial.**
|
||||
An automated mutual ally now waits for a useful human Fremen free-revival grant
|
||||
in concurrent Basic Revival, until the grant resolves or the Fremen selects the
|
||||
|
||||
Reference in new issue
Block a user