Support staged group shipment funding
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
624f95dde4
commit
34aa64cdef
13 files changed
+828
-16
No files matched your search
+14
-4
@@ -40,6 +40,16 @@ cases. The three-member option remains
|
||||
unavailable: faction benefits, funding, and other group interactions still
|
||||
need integration. [Scope](OPTIONAL_ALLIANCE_VICTORY.md#group-nexus-negotiation--28-october-2026).
|
||||
|
||||
**Staged group shipment funding — 28 October. Prototyped / Partial.** Two
|
||||
allies can pledge separately to a group member, who may use named shares for
|
||||
one ordinary Basic shipment; an outside Guild receives the payment and unspent
|
||||
pledges return to their donors. The staged table has private pledge and share
|
||||
controls. The related eight-file batch passes 48 cases, with real Nexus and
|
||||
shipment actions following a staged starting position. Guild-member groups,
|
||||
group bidding and special transports remain
|
||||
unsupported; group play is still not exposed in the lobby.
|
||||
[Scope](OPTIONAL_ALLIANCE_VICTORY.md#group-ordinary-shipment-funding--28-october-2026).
|
||||
|
||||
**Basic allied No-Field transit — 28 October. Prototyped / Partial.** Richese
|
||||
may offer its ally an immediately revealed shipment into a Richese-occupied
|
||||
territory. The recipient may depart or accept the existing provisional loss
|
||||
@@ -132,10 +142,10 @@ enabled or claimed complete by the standalone foundation. Shipment entry and
|
||||
visitor consequences now use the group-aware receipt and physical baseline.
|
||||
The staged Nexus negotiation is connected; group funding, faction benefits
|
||||
and other engine paths still need integration before the option can be offered.
|
||||
Connected staged Nexus controls and a funding quote model unanimous consent,
|
||||
explicit donor allocations and edge-bound pledge authorizations. The engine
|
||||
still must issue and revoke unique edge authorizations, settle and refund
|
||||
escrow atomically, and connect group funding controls to native actions and AI.
|
||||
Connected staged Nexus and shipment controls model unanimous consent, explicit
|
||||
donor allocations and edge-bound pledge authorizations. The engine issues and
|
||||
revokes those authorizations and refunds shipment escrow; group-funded bidding,
|
||||
special transport and Guild-allied rates still require integration.
|
||||
The separate printed unlimited-size / three-stronghold variant remains missing;
|
||||
the current group model deliberately caps membership at three. The combined
|
||||
earlier batch passed 189 cases; the shipment batch passed 58 cases. The latest
|
||||
|
||||
Reference in new issue
Block a user