**Status.** An early-reaction proposal for the owner's selected direction: certain actions join rooms into groups that stay connected through shifts, and connecting the entire station is one of the deepest and latest puzzles. Nothing here is canon — not the machinery, not the architecture, not any ending. Early shift uncertainty and permanent connections are preserved. The local latching rules are a candidate; the required deep, station-wide insight is still unresolved, and the source-sequencing claim below is not established.
+
**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.
-
## The proposal
+
## Shared local rule
-
**Legality is a seam signature.** Every coupling face carries a short signature in the builders' cut script. Two sections whose facing signatures match were built adjacent. At a matching seam the coupling can be latched; at a mismatch it visibly refuses.
+
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.
-
**Making the latch needs a live run.** The coupling only engages while a service main runs live across the seam. Restoring that run is the work.
+
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.
-
**Once latched, it is permanent.** This is the part that matters most for the owner's requirement: **a latched coupling is mechanical and remains until a deliberate release.** Power loss does not. De-energising the main does not. A circuit accident cannot erase progress, because after the latch the run's state is irrelevant.
+
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.
-
## Proposed source constraint — station-wide depth still unresolved
+
## Three candidate experiences
-
The additional candidate constraint is at the moment of latching: **source fittings are scarce and reusable.** Whether this creates meaningful global planning still needs a concrete design example.
+
### 1. Room-transformer network
-
A main carries **one live source**. To latch a seam you must energise that main from one fitting. Having latched, you can pull the source and use it elsewhere — the latch holds. This suggests a possible **sequencing** puzzle: which main to energise, from which fitting, and when. The current rules do not establish that any particular order is necessary.
+
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.
-
The unresolved counterexample is simple: use a source to latch one seam, retrieve it without undoing that latch, then use it on the next seam. Scarcity and one-source-at-a-time operation alone do not prevent this. Reachability or compatibility might create an ordering dependency, but a concrete failed sequence and a successful sequence based on a discovered rule are still missing. The proposal may currently add travel rather than a deep insight.
+
**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.
-
## A local example
+
**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.
-
**Working.** Blue Ward's east flange and Lift Service's west flange carry the same signature. The cable main between them is dead at a pulled contact. Re-seat the contact: the run goes live from Lift Service's source fitting, the coupling latches, and the pair is bound for good.
+
**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.
-
**Refused, mismatch.** Cold Storage's north flange carries a different signature from anything it currently touches. The lock refuses on contact. Cost: the trip, nothing else.
+
### 2. Static signature families and bridges
-
**Refused, two sources.** Recovery Stair's flange *does* match Lift Service's north face, but Recovery Stair sits on a stub already driven by its own fitting.
+
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.
-
- *Seeing it beforehand:* a source fitting shows plainly whether it is driving, and a live main carries a flow tell along its length. Standing at the seam, the player can see tells running **toward each other** from both directions. Two feeds, one main.
-
- *The action:* pull the drive contact at one of the two fittings — the same class of work as re-seating one.
-
- *The observed result:* that side goes dead, the opposing tell stops, the run is live from a single source, and the coupling latches.
+
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.
-
A failed attempt teaches the constraint and costs only the attempt. Nothing is destroyed, no bind is lost, and no penalty is proposed beyond time and oxygen.
+
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.
-
## Effects, stated exactly
+
**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.
-
| Event | Existing binds | Doors and installed parts | When it takes effect |
-
|---|---|---|---|
-
| Power loss anywhere | Unaffected | Unchanged | — |
-
| Failed join (mismatch or two sources) | Unaffected | Unchanged | Nothing changes at all |
-
| Deliberate de-energising to reuse a source | Unaffected | Unchanged | Immediately, and it is the intended move |
-
| Successful latch | New bind added | Stay unlocked, stay installed | Immediately; survives the next death |
-
| Deliberate release | That bind ends | Stay unlocked, stay installed | Immediately eligible for the next death-triggered shift; no live rearrangement |
+
**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.
-
**Undo** is unlatching, and it needs the run live again — the same requirement as latching. So undoing is symmetrical work rather than a free reset.
+
### 3. Simple complementary matching
-
## The later insight that changes a plan
+
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.
-
The intended later insight is that **the same fitting can serve different mains at different points in a plan**. That alone is ordinary reuse, not yet the required late discovery. The design still needs an observed constraint that changes which sequence works, or a different station-wide insight. This objective remains open; the local latching exercise must not be presented as its completed solution.
+
**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.
-
## Reaching an undo — an access requirement, not a proof
+
**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.
-
A mistaken bind's release point sits inside the group it made, and a group's interior stays connected. But that does not show the player can get to it **from the ship**, and I no longer claim it does.
What the design actually requires: **every coupling point must be reachable from the ship's point through some sequence of re-seats.** That is an authored connectivity condition on the arrangement — something a designer must guarantee, not something the fiction proves. Its cost to the player is real: a group out of reach may take several expeditions and several deaths before it comes around, and the undo then still needs the run re-energised. Softlock is *designed against*, not demonstrated.
+
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.
-
## What I am leaving unestablished
+
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.
-
My earlier claim that historical adjacency records stay predictive after binding does not hold up. The player knows the binds they made; they do not know the whole free set, because they have not seen every section. **Any order among re-seats is an unestablished authored condition.** If it exists, its legibility has to be designed, and nothing here shows the player could derive it. No forced death is proposed to prove any of it.
+
## Failed action and successful action
-
## Completion, provisionally
+
**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.
-
**Every room and region in one connected network.** Not selected hubs — everything genuinely belongs. I am dropping the spanning-versus-every-seam question: extra latches beyond a connected whole would mostly duplicate geometry, and asking the owner a technical question with no player-visible difference is not worth his time.
+
**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.
-
**Stabilisation is a proposed payoff, not an accepted rule.** With nothing unbound, nothing re-seats, and the station holds one shape. Contents still vary — population, hazards, machine states — so it is stable rather than inert. This is a proposed change to every-death shifting and needs the owner's acceptance; it is separate from any ending, and completion is not required for one.
+
**Successful sequence.** Proposed example:
-
## The simpler alternative, kept
+
1. Reverse Decontamination so its free face accepts Foundry's blue-double and its other face emits amber-single. This machine state persists.
+
2. 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.
+
3. Join the group's amber-single face to Imaging Exchange, a rare bridge whose other face can emit red-triple.
+
4. When that growing group later meets Archive's red-triple receiving face, latch it. Walk from Foundry through Decontamination and Imaging into Archive.
+
5. Send the diagnostic pulse from the ship-rooted side. Each included region returns its own acknowledgement.
-
**Seams alone.** One rule: matching signatures latch, mismatches refuse. It is the simpler candidate to teach and author, and fits the selected persistent-connection direction; it does not yet supply the deep station-wide insight.
+
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.
-
Seams alone is the simpler local baseline. Both versions still need a convincing deep puzzle; the extra source system has not yet demonstrated the ordering problem that would justify its teaching and authoring cost. It remains a candidate rather than the preferred rule on an established depth advantage.
+
## Three states that must not be confused
-
The choice is not established as light versus deep. The source system should earn its extra complexity through a concrete discovery; merely adding it does not satisfy the owner's late-puzzle ambition.
+
- **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.
-
## Notes and remaining dissent
+
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.
-
Registration is not a rival: a terminal could be the **readable interface to the source plan**, showing which fittings drive what and why a latch refused. That is worth exploring and does not add a system.
+
## Mistake and recovery with actual access
-
Nothing here requires the binding puzzle to carry both alien languages; that would be an invented obligation.
+
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.
-
**Remaining dissent:** whether the one-source rule reads as reasoning or as arbitrary plumbing is unresolved and I cannot settle it on paper. It is the thing I would most want checked once observation is authorised.
+
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.
