Hold The Horde — Connecting The Station

Status. Practical comparison for the owner's selected direction: certain actions connect rooms or groups persistently, and connecting the entire station is one of the deepest/latest puzzles. The owner has not selected the mechanism or answered whether completion stabilises the layout. Everything below is proposed; no story ending, corruption rule, exact machine, or implementation is established.

Shared local rule

A death can place two unbound thresholds physically adjacent. Adjacency only makes an attempt possible. A persistent join is latch-compatible when the visible service signatures at those two faces can exchange the required pulse. A mismatch refuses before the latch completes. A successful mechanical latch opens a walkable threshold and survives later deaths until deliberately released.

Power is an activation tool, not a global ordering rule. A source may charge seam A, be recovered without undoing A, then charge seam B. Both latches remain. Scarcity alone therefore adds travel, not depth.

The owner-selected opening—one reusable part operating both carried equipment and station machinery—can prepare the player to look for shared causal behaviour. It does not prove that room machinery uses personal-rig ports or the same protocol. That relationship remains analogy unless separately adopted.

Three candidate experiences

1. Room-transformer network

Rooms visibly accept one service-pulse pattern and emit another after their machinery acts. Reversing or reconfiguring a rare room changes its exposed pattern. The late realisation is that previously “incompatible” regions need converter rooms between them: the station can be assembled as a causal network, much like a build at room scale.

Earlier clues. The player has seen Decontamination turn an amber double pulse into blue single when its steriliser runs; a Freight Split branch one pulse to a shutter and rack; and a charged Foundry–Archive latch refuse while both faces visibly pushed blue double outward. The reused source was sufficient—the directions were not.

Strongest case. It gives the player a predictive rule and an action beyond finding matching doors. Familiar rooms acquire new uses, and multiple converter sequences can support authorship rather than one prescribed solution.

Cost. If every room has modes and transformations, the station becomes an enormous circuit editor. Signals, directions, walking paths, and latch states could overwhelm the discovery. Authoring must guarantee readable converters and viable constructions without quietly giving the player a solved network.

2. Static signature families and bridges

Most thresholds belong to visible signature families. A bridge room has an A-family face on one side and a B-family face on another. It can join an A group and later present its B face to a B group.

The evidence must actually show the difference: inspecting Glass Theatre reveals an A signature on its west face and a B signature on its north face; records across different shifts show the west face beside A-family rooms and the north face beside B-family rooms. Two identical marks on one face would not establish a bridge.

Binding the A/B bridge to B first normally leaves its A face available, so order alone does not create a failure. The real discovery is which rooms span families and which exposed face is needed, not a hidden “correct first side.” A mistake occurs only if the player uses a needed bridge face on an irrelevant same-family branch and thereby buries or occupies that face; that must be visible and reversible.

Strongest case. Families make old adjacency records useful without requiring every room to be programmable. A rare bridge can explain why two broad regions never meet directly.

Cost. Once bridges are identified, patient matching may solve the rest. Its late insight may be classification rather than construction, and invisible family boundaries risk making ordinary bad luck look like impossibility.

3. Simple complementary matching

Every threshold displays one counterpart signature. When compatible faces become adjacent, the player charges and latches them. The whole station is complete when all regions join one network.

Strongest case. This can still support discovery: the player learns where a rare counterpart appears, recognises a previously ignored face, and chooses which current opportunity matters. It is clear, inexpensive to teach, and hard to softlock.

Cost. The deepest puzzle risks becoming the longest collection of pair matches. Knowledge helps search, but it does not substantially change how the player acts.

Provisional recommendation: rare transformer bridges

Use simple signature compatibility as the common rule, but give a small number of bridge rooms a visible transformation and, occasionally, a reversible mode. Most rooms remain static. The late discovery is not “every room is a circuit” or “bridges have a secret order”; it is that a familiar service room can convert the family presented by a growing group and thereby join regions that no direct seam can connect.

This combines the family model's legibility with the transformer model's actionable payoff while accepting more complexity than unique matching. The main unresolved cost is authored combinatorics: converter scarcity could still create one mandatory sequence, and mode displays could become a disguised solved-map interface. The design should allow more than one viable converter placement where feasible, but prose cannot establish that the complete content set supports it.

Failed action and successful action

Failed. Foundry Block and Archive Stack are physically adjacent after a shift. Each exposed threshold shows blue-double flowing outward. The player brings a charged source and attempts the join. The latch preview displays two opposing output arrows and refuses final engagement. The source remains available and no existing bind changes. More charge or sequential source reuse cannot turn either output into an input.

What the later insight changes. In Synchronization Gallery, a test display overlays three earlier records: Decontamination's reversible amber/blue conversion, Freight's branch, and the Foundry–Archive collision. It shows transformations, not room names or a route. The player can now predict that a converter sequence may expose the receiving pattern Archive needs.

Successful sequence. Proposed example:

Reverse Decontamination so its free face accepts Foundry's blue-double and its other face emits amber-single. This machine state persists.
On an ordinary later arrangement where Decontamination is adjacent to Foundry, latch them. A known transformation suggested this opportunity; it did not guarantee when the shifting station would offer the adjacency.
Join the group's amber-single face to Imaging Exchange, a rare bridge whose other face can emit red-triple.
When that growing group later meets Archive's red-triple receiving face, latch it. Walk from Foundry through Decontamination and Imaging into Archive.
Send the diagnostic pulse from the ship-rooted side. Each included region returns its own acknowledgement.

No death is required solely to advance this sequence. The player can pursue other expeditions while unbound regions continue to receive new neighbours after natural deaths. Whether the necessary opportunities appear often enough without encouraging death farming is an authored shift-distribution requirement and later test question, not a guarantee.

Three states that must not be confused

Walking connectivity: a completed latch leaves a traversable connection. Changing a converter mode does not close it.
Persistent join state: the mechanical latch survives power loss, mode changes, and death until deliberate release.
Diagnostic coverage: the current pulse configuration reaches a region and returns its acknowledgement. Changing a mode can break or restore coverage without erasing the walkable latch.

Thus a player may have every relevant room physically joined but still need to tune converters so the diagnostic reaches them all. A mode change never silently destroys permanent work.

Mistake and recovery with actual access

Late station-wide construction should extend a ship-rooted walkable network, or merge an encountered island into it. This is a proposed authoring rule, not something prose proves about every possible shuffle.

Suppose the player latches Imaging by its red face to an irrelevant branch, occupying the face Archive needs. Because the new join extends the ship-rooted network, the player can walk from the ship to the release lever on the network side. They may first try a mode change; the walking latch remains while diagnostic coverage changes. If the wrong physical face is occupied, they deliberately release that one seam. Other latches and machine states remain. The released rooms stay adjacent for the current life and become eligible to separate only on the next death-triggered shift; random power loss erases nothing.

Recovery costs travel, oxygen, and perhaps waiting through ordinary play for a useful new adjacency. It does not require an inaccessible terminal, a replacement part, or deliberate death. Every critical latch needs controls reachable from both sides, and every merge path needs a network-side control; those are explicit layout obligations still to design.

What “every region” means

Completion requires one ship-rooted, traversable persistent network containing every authored playable region, including hidden and optional regions—not every possible door pairing. A compact inseparable assembly counts as one region only if all its interior spaces are actually reachable. No unseen room latches itself.

Repairing Synchronization Gallery may expose a proposed heartbeat roster: acknowledged regions, discovered-but-uncovered regions, and anonymous unanswered signatures. It supplies no unseen names, routes, or locations. A player who has not found every region can therefore know the station is incomplete, but must still discover, visit, latch, and diagnostically cover each missing region. This roster and a complete region inventory are authoring requirements, not demonstrated guarantees.

Conditional completion consequence

The owner's answer about stabilisation is pending, and the physical rule must follow it.

If completion stabilises the station: the finished persistent network becomes one rigid connected arrangement, a proposed late exception to death-triggered shifting.
If shifting continues: the joins cannot be rigid seams. They must be represented as persistent articulated transfer sleeves or equivalent flexible connections: selected paths remain walkable while rooms re-seat around their unselected incidental thresholds. That adds substantial spatial, visual, and implementation burden and needs its own design; it is not automatic.

Neither outcome is inherently an ending, escape, or release of the captive being.

Decision record

Provisional recommendation: simple local matching plus a few legible, sometimes reversible transformer bridges.
Why: a concrete failed prediction becomes a solvable adapter problem, earlier machinery gains new meaning, and all regions can form one player-authored network.
Accepted cost: more signal language, converter states, content bookkeeping, recovery access, and compatibility testing than static families or unique pairs.
Unresolved objection: the simpler matching design may deliver the owner's station-wide ambition more cleanly; complexity has not been validated as readable, fun, or feasible.
Reopen the choice if: converter modes require a solved-map UI, one rare bridge dictates a single order, adjacency availability promotes death farming, or the heartbeat roster cannot cover every playable region honestly.