2026-09-10 10:45:47
Anonymous:
Repair reference destinations after discovery and home rewrites
hold the flood/player information.md ..
@@ 111,7 111,7 @@
## Late-game states, conditional on an unchosen mechanism
-
[Connecting The Station](/Hold%20The%20Flood/Connecting%20The%20Station) has no selected mechanism, so these are the information consequences *if* the current candidate is adopted, not commitments:
+
[Connecting The Station](/Hold%20The%20Flood/Connecting%20The%20Station) explains the current discovery direction. The pulse and roster displays below belong to the conditional technical candidate in [Death Shift And Rescue Continuity](/Hold%20The%20Flood/Death%20Shift%20And%20Rescue%20Continuity) and [Station Room And Module Inventory](/Hold%20The%20Flood/Station%20Room%20And%20Module%20Inventory); the joining mechanism and completion display remain proposals:
| State | What the player sees | Not inferred |
|---|---|---|
@@ 119,7 119,7 @@
| Three states kept distinct | Walking connectivity, persistent join, and current diagnostic signal shown separately | That losing diagnostic power has undone a join |
| Latch roster | Counts of regions joined to the ship-rooted network, discovered but not joined, and anonymous registered regions not yet encountered | Any name, face, route or location for an anonymous region |
-
The roster's deliberate cost is already accepted on that page: publishing a count turns hidden spaces into known unknowns. The information rule it must obey is narrower and belongs here — **a persistent join stays known after death, because it is a fact about work already done; it must not thereby reveal an unbound adjacency the player has not yet seen.** Knowing the network is incomplete is not knowing where the gap is.
+
The proposed roster reveals that hidden spaces exist by publishing their count. This spoiler cost is described in [Station Room And Module Inventory](/Hold%20The%20Flood/Station%20Room%20And%20Module%20Inventory), and the display remains a proposal. The information rule it must obey is narrower and belongs here — **a persistent join stays known after death, because it is a fact about work already done; it must not thereby reveal an unbound adjacency the player has not yet seen.** Knowing the network is incomplete is not knowing where the gap is.
