This page develops two open questions from [Connecting The Station](/Hold%20The%20Flood/Connecting%20The%20Station): whether several converter placements can produce complete stations, and whether obtaining the required adjacencies becomes repeated death cycling. It gives explicit sockets, two non-overlapping final layouts, a locally legal dead end and its recovery, and proposes one controlled meeting at the next shift.

The [Owner Brief](/Hold%20The%20Flood/Brief) selects persistent room-group connections and a late whole-station puzzle. [Shifting Station Options](/Hold%20The%20Flood/Shifting%20Station%20Options) records that selection; its earlier Option 2 recommendation is historical.

This example assumes rigid groups, reversible latches and separate walking and diagnostic states, as detailed in [Death Shift And Rescue Continuity](/Hold%20The%20Flood/Death%20Shift%20And%20Rescue%20Continuity). It also assumes that full connection stabilises the layout, which [Connecting The Station](/Hold%20The%20Flood/Connecting%20The%20Station) has not selected; if continued rearrangement within a fully joined station is chosen instead, this construction needs redesign.

Each region occupies one square cell in this example. East increases x; north increases y. Regions retain orientation, and a joined group translates without changing its internal arrangement. Real rooms need not be square.

BL, AM and RD identify three service families. They also have distinct non-colour marks: double bar, single ring and triple chevron. “In” and “out” describe the latch's service handshake; once latched, people can walk either way.

| ID and region | Persistent-latch sockets | Role in this example |

| W — Observation ward | West: RD-in | Another terminal region |

A reusable source activates each attempt locally. It can be recovered and reused without undoing an existing latch. The example has no global power budget. Its converters have fixed mappings; switchable modes are outside this example.

The choice has a clear consequence: Layout 1 gives a four/four split; Layout 2 gives a three/five split. If Archive is the player's frequent destination, the second may be attractive. If Ward matters equally, the first may be preferable. Crossing counts alone do not fix travel time, oxygen cost or safety; encounters and real room dimensions could change the preference.

More charge, cycling converter diagnostics or repeatedly reshuffling X cannot free an occupied socket. This is a counterexample to “keep making valid joins and eventually everything will fit.” A local preview was correct to permit G–W; it should not pretend it evaluated the whole construction.

Both sides of each seam need accessible release controls. In this mistake, G's control is reachable from the ship through two completed joins before anything is released.

The physical replacement needs W to vacate its former cell; it cannot be completed merely by changing a signal.

After discovering a late service controller, the player may register **one selected pair of previously inspected faces** to meet at the next death-triggered shift. One face must be on the ship-rooted group; the other belongs to a different, discovered group. This is an additional capability; it does not follow automatically from knowing the socket families.

The controller validates the chosen pair only. It does not search the journal, identify a missing converter, recommend which room to use or select a solution. Validating compatibility is the same limited kind of report contemplated in [Player Information](/Hold%20The%20Flood/Player%20Information).

| Journal is open | Allow notes about an intended pair; no registration or latch action completes while it is open |

The controller's feasibility check is a **content and technical-design obligation**, not an implemented solver. For arbitrary rigid room shapes, matching service labels is insufficient to promise collision-free placement. The eight-cell layouts above provide witnesses for their own requests; the full content set needs authored admissible arrangements or another separately specified method that can substantiate each acceptance.

A refusal may say that the selected groups lack clearance. It must not expose unseen room outlines as an explanation.

This repair costs **one release, two new joins and at most two requested shifts**, provided the player completes each offered join and does not invalidate a reservation. Oxygen and travel remain ordinary costs. There is no random retry count and no need to break S–F, F–D, D–I, I–A or F–G.

If new adjacencies arise only at death, the required pair is absent, and all other useful current work is finished, obtaining that pair still requires another death. A deterministic appointment cannot remove that dependency. Carried property returns on death, and deliberate death must not acquire a special confiscation penalty to conceal it.

The request removes **uncertain repeated deaths for the same pair**, not death as a possible assembly tool. Players can queue a useful meeting, pursue another expedition and let the next natural death deliver it. At the very end, they may choose deliberate death to obtain the final arrangement. That is the accepted cost.

For these eight already discovered, initially separate pieces, either listed construction order can grow from S in seven accepted meetings, with fewer requested shifts if some useful adjacencies already exist. This is a limit on this assembly sequence after discovery only.

Scaling one-new-component-per-request to forty initially separate playable instances could still mean thirty-nine requested shifts. The [Whole Game Outline](/Hold%20The%20Flood/Whole%20Game%20Outline)'s SMALL band distinguishes forty placed instances from four regions and twenty-four reusable modules; those counts are not interchangeable. Existing groups and incidental extra joins can reduce requests, but content counts alone do not fix the actual cadence.

If even limited deliberate death is unacceptable, the design needs a **living realignment action** or another way to change the relevant adjacency. That would be a larger new mechanic.

A possible evidence sequence:

The discovery is actionable: a familiar room can become an adapter or an intermediate piece in a larger construction. The player then chooses which destinations receive the shorter branch.

| Uncontrolled shuffles only | Least additional machinery; every useful meeting remains a discovery | No limit on the wait for a particular required pair unless the distribution supplies one |

**Recommendation:** retain the two-layout example as a design fixture, and consider one guaranteed registered meeting as a late-game capability.

- **Connecting The Station:** add socket occupancy to its constraints and replace its unlimited adjacency wait with the request contract above; preserve independent walking, latch and diagnostic states.

- **Whole Game Outline:** count ordinary joins and requested shifts separately from special converter sites; a small number of special puzzles does not measure the burden of assembling every placed instance.