Skip to content

0054 — Region-Lifecycle Cascade Composition (Group B)

Status

Folded into SYSTEMS/region-lifecycle.md, SYSTEMS/ship-registry.md, OPERATIONS/monetization.md, and SYSTEMS/realtime-bus.md — all 6 items (X-D1, X-D3, X-V1, X-V2, X-I2, X-I3) shipped and verified live in each target doc's own prose (region-lifecycle.md's stakeholder-ingress rule + transactional-outbox section + wallet row-lock; ship-registry.md's auto-bounty target_player_id section; monetization.md's GC-lapse liquidation window). Graduated from Distributed-fold (6/6) 2026-08-07 by impl-sectorwars, per the README's own exit criterion — defer to those pages for the canonical description. (re-verified 2026-08-07)

Context

Six findings in the audit Group B identified composition gaps in the region-lifecycle cascade where two systems compose poorly: suspended-state player access (X-D1), GC lapse with foreign-region assets (X-D3), in-flight realtime events crossing transaction rollback (X-V1), stolen-ship auto-bounty escrow trapped on destroyed-ship rows (X-V2), wallet read race during cleanup (X-I2), and cascade-compensation Bank access for GC-lapsed owners (X-I3). See Related docs below for the canonical current description of each.

The original Decision/Consequences/Alternatives-considered sections (X-D1/X-D3/X-V1/X-V2/X-I2/X-I3, ~185 lines) are preserved in git history as of the fold date (2026-08-07) — their content now lives as canonical prose in the target docs below, not duplicated here per the Folded-into convention.