Commit a0a633

2026-09-08 15:46:42 Anonymous: Resolve focused review of rigid joins, completion state, gallery evidence, and death cycling

hold the flood/connecting the station.md ..
@@ 16,7 16,7 @@
	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.
+	**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.
	**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.
@@ 38,39 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.
-	**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.
+	**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.
	**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.
+	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.
	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.
+	**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.
-	**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.
+	**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.
	**Successful sequence.** Proposed example:
-	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.
+	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.
+	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.
	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.
+	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.
-	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.
+	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.
	## 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.
+	- **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.
-	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.
+	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.
	## Mistake and recovery with actual access
@@ 84,21 84,22 @@
	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.
+	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.
+
+	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.
	## Conditional completion consequence
-	The owner's answer about stabilisation is pending, and the physical rule must follow it.
+	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.
-	- **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.
+	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.
	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.
+	- **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.
	- **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.
+	- **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.