Blame
|
1 | # Hold The Horde — Connecting The Station |
||||||
| 2 | ||||||||
|
3 | **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. |
||||||
|
4 | |||||||
|
5 | ## Shared local rule |
||||||
|
6 | |||||||
|
7 | 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. |
||||||
|
8 | |||||||
|
9 | 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. |
||||||
|
10 | |||||||
|
11 | 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. |
||||||
|
12 | |||||||
|
13 | ## Three candidate experiences |
||||||
|
14 | |||||||
|
15 | ### 1. Room-transformer network |
||||||
|
16 | |||||||
|
17 | 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. |
||||||
|
18 | |||||||
|
19 | **Earlier clues.** The player has seen Decontamination's forward mode accept amber-single and emit blue-double, then its reverse mode accept blue-double and emit amber-single; 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. |
||||||
|
20 | |||||||
|
21 | **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. |
||||||
|
22 | |||||||
|
23 | **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. |
||||||
|
24 | |||||||
|
25 | ### 2. Static signature families and bridges |
||||||
|
26 | |||||||
|
27 | 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. |
||||||
|
28 | |||||||
|
29 | 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. |
||||||
|
30 | |||||||
|
31 | 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. |
||||||
|
32 | |||||||
|
33 | **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. |
||||||
|
34 | |||||||
|
35 | **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. |
||||||
|
36 | |||||||
|
37 | ### 3. Simple complementary matching |
||||||
|
38 | |||||||
|
39 | 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. |
||||||
|
40 | |||||||
|
41 | **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 and inexpensive to teach. It has fewer stateful mistakes than transformer modes, but still needs the same authored guarantee that a mistaken join has a reachable release. |
||||||
|
42 | |||||||
|
43 | **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. |
||||||
|
44 | |||||||
|
45 | ## Provisional recommendation: rare transformer bridges |
||||||
|
46 | |||||||
|
47 | 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 provisional recommendation assumes rigid mechanical joins and is therefore compatible with eventual layout stabilisation; the pending owner answer can reopen it. |
||||||
|
48 | |||||||
|
49 | 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. |
||||||
|
50 | |||||||
|
51 | ## Failed action and successful action |
||||||
|
52 | |||||||
|
53 | **Failed.** The Foundry Block group and Archive Stack group 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. |
||||||
|
54 | |||||||
|
55 | **What the later insight changes.** Synchronization Gallery shows only its own locally observable behaviour: a test pulse enters each of its current thresholds, and the display shows the pattern before and after the gallery's present machine state acts. It does not import, curate, or explain the player's old captures. In the paused journal, the player may compare that behaviour with their own Decontamination, Freight, and Foundry–Archive records and infer that familiar rooms can be converters. The player can then predict that a converter sequence may expose the receiving pattern Archive needs. |
||||||
|
56 | |||||||
|
57 | **Successful sequence.** Proposed example: |
||||||
|
58 | |||||||
|
59 | 1. Reverse Decontamination so its free face accepts Foundry's blue-double and its other face emits amber-single—the exact inverse pair the player observed earlier. This machine state persists. |
||||||
| 60 | 2. On an arrangement where Decontamination's blue-accepting face is physically adjacent to Foundry's blue-emitting face, latch them. A known transformation identifies a useful face pairing; it does not guarantee when the shifting station will offer that exact orientation. |
|||||||
|
61 | 3. Join the group's amber-single face to Imaging Exchange, a rare bridge whose other face can emit red-triple. |
||||||
| 62 | 4. When that growing group later meets Archive's red-triple receiving face, latch it. Walk from Foundry through Decontamination and Imaging into Archive. |
|||||||
|
63 | 5. Send a local diagnostic pulse through the new path to verify that the chosen converter states behave as predicted. This is useful evidence and troubleshooting, not a second condition for geometric completion. |
||||||
|
64 | |||||||
|
65 | Because new adjacencies arrive on death, the player may deliberately die to request another arrangement after finishing useful work in the current one. The owner's carried-property rule makes that a legitimate late strategy rather than a recovery penalty: carried equipment and loot return, consumed supplies remain spent, and installed work stays in place. The player may instead pursue other expeditions until a natural death shifts the station. Hunting one exact face orientation could still become repetitive death cycling; its frequency is an unresolved pacing and authored-distribution cost, not a guarantee this document solves. |
||||||
|
66 | |||||||
|
67 | ## Three states that must not be confused |
||||||
|
68 | |||||||
|
69 | - **Walking connectivity:** a completed latch leaves a traversable connection. Changing a converter mode does not close it. |
||||||
| 70 | - **Persistent join state:** the mechanical latch survives power loss, mode changes, and death until deliberate release. |
|||||||
|
71 | - **Diagnostic signal state:** the current pulse configuration may reach a region and show how its machinery transforms the pulse. Changing a mode can break or restore that local evidence without erasing the walkable latch. |
||||||
|
72 | |||||||
|
73 | Thus a player may have every region physically joined even while part of the diagnostic signal is unpowered or misconfigured. Physical inclusion is the base objective; tuning the pulse is optional local evidence and troubleshooting unless a separate later proposal gives it a distinct payoff. A mode change never silently destroys permanent work or turns a joined region into a false “incomplete” result. |
||||||
|
74 | |||||||
|
75 | ## Mistake and recovery with actual access |
||||||
|
76 | |||||||
|
77 | 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. |
||||||
|
78 | |||||||
|
79 | 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. |
||||||
| 80 | ||||||||
| 81 | 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. |
|||||||
| 82 | ||||||||
| 83 | ## What “every region” means |
|||||||
| 84 | ||||||||
| 85 | 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. |
|||||||
| 86 | ||||||||
|
87 | Repairing Synchronization Gallery may expose a proposed **persistent latch roster**, independent of current diagnostic power: regions already joined to the ship-rooted network, discovered regions not yet joined, and anonymous registered regions not yet encountered. A temporarily unpowered joined region remains counted as joined. The roster supplies no unseen names, routes, faces, or locations, and never latches anything itself. A player who has not found every region can therefore know the physical network is incomplete, but must still discover, visit, and latch each missing region. |
||||||
| 88 | ||||||||
| 89 | Publishing the number of anonymous regions intentionally turns the existence and count of hidden spaces into known unknowns. That is a spoiler cost accepted here so “the entire station” is verifiable rather than guesswork; their nature and location remain secret. The roster and complete region inventory are proposed authoring requirements, not demonstrated guarantees. |
|||||||
|
90 | |||||||
| 91 | ## Conditional completion consequence |
|||||||
| 92 | ||||||||
|
93 | The current candidate uses **rigid joins throughout**: connected rooms travel as one group, and their selected internal relationships do not rearrange. If every region enters one rigid group, the candidate consequently stabilises the station's connected layout as a proposed late exception to death-triggered shifting. |
||||||
|
94 | |||||||
|
95 | The owner's answer about that payoff is pending. If the owner instead wants rooms to keep rearranging after full completion, this is not a cosmetic terminal variation. Rigid joining would have to be rejected or materially redesigned from the first bind—perhaps as flexible connections, though none is selected here—and the recommendation must be re-examined under that different physical rule. This page does not claim both behaviours work automatically. |
||||||
|
96 | |||||||
| 97 | Neither outcome is inherently an ending, escape, or release of the captive being. |
|||||||
| 98 | ||||||||
| 99 | ## Decision record |
|||||||
| 100 | ||||||||
|
101 | - **Provisional recommendation:** if full completion stabilises the layout, use simple local matching plus a few legible, sometimes reversible transformer bridges. Reopen the mechanism if the owner chooses continued rearrangement. |
||||||
|
102 | - **Why:** a concrete failed prediction becomes a solvable adapter problem, earlier machinery gains new meaning, and all regions can form one player-authored network. |
||||||
| 103 | - **Accepted cost:** more signal language, converter states, content bookkeeping, recovery access, and compatibility testing than static families or unique pairs. |
|||||||
| 104 | - **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. |
|||||||
|
105 | - **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 latch roster cannot cover every playable region honestly. |
||||||
