Hold The Horde — Hospital Story Directions

Status. Two story options developing the owner's leading draft, for early reaction. Neither is canon and no player penalty is selected.

The shift approach is no longer open: the owner chose that certain actions connect rooms into groups that stay connected through shifts, and asked that connecting the whole station this way be one of the game's deepest and latest puzzles. What remains open is how links are discovered and made, which connections qualify, how unconnected areas keep shifting, and what completing the station-wide connection does to later shifts. Both options below are compatible with that direction and neither depends on a particular mechanism for it.

What both options share

Scope of the field. (Stated as this fiction's rule, not as a claim about real biology.) It repairs living tissue toward a template of form, brains included. The template describes anatomy, not content, so it never rolls memory back: what a person learned yesterday is still there tomorrow, because the field was never holding a copy of it to restore.

A mind is tissue, so repairing a brain toward a drifted template changes the substrate while leaving what is stored in it. The core team kept everything they knew and became different people while knowing it — altered temperament, perception and sense of themselves. Their notes read as madness because a stranger was writing them with their memories.

The field does not touch objects. Besides repair it relocates, returning the repaired body and whatever is on it to where that body was registered, so evidence and carried property survive because the field was never positioned to take them.

Why a door the player opened stays open. Nothing restores object state. Reconfiguration moves architecture rather than rewinding it: a section re-seats elsewhere with its door still open, because the machinery that moves fabric has no opinion about that fabric's state.

What ties a shift to the player. Registration is of a docking vessel's occupant, at the moment that vessel docks — it couples one person to one berth. It is not "whoever crosses the collar". A rescued survivor walking from station side to ship side is not arriving on a docking vessel, so nobody is registered by being brought aboard, no colonist gains a return point this way, and their deaths cause no shifts.

Reconfiguration is driven by that registration's intake cycle. Ward patients revive where they lie and trigger nothing. Rooms never move while the player stands in them, and no live rearrangement is proposed. Whether survivors are covered by the field at all is deliberately outside this comparison; global survivor mortality and eligibility remain undecided.

When revival actually stops. Only by leaving the field, and the game says so before the player commits, so undocking never ends it unknowingly. Whether the player may keep exploring mortally after a deeper action is a separate proposed exception, not adopted here.

Option A — the one they made

The ancient aim, and why they left. They set a field in the core to make one of their own unable to die. It worked, and the result could not leave the field without dying: a person bound permanently to a room. Unwilling to kill it or live beside it, they sealed the core and went.

The human misreading, and the failed intervention. Humans found wounds closing and the dead getting up, and built a hospital. Research traced the effect to the core and opened the seals to strengthen it. Widening the field coupled it to the one inside, and the template began to include that anatomy — so healing now repairs toward something not entirely human, which is why healing machines turned harmful, the over-restored become creatures, and the core team changed without ever losing what they knew.

Two legacies, and ship revival. Builders' containment — isolator seals, pressure gates, field regulators in their cut script — against hospital machinery: restraint beds, dosing lines and triage stations under human labels, still working toward a drifted template. The docking intake registered the astronaut to a restoration point inside this ship, on the ship side of its airlock; the field returns them aboard here.

Both alien languages, doing semantic work. The builders' operational script covers seals, ports and regulator states, and the player uses it to work the containment.

The second is the being's own, used for utterances rather than labels. The observable distinction is not the address but a terminal element that comes in two forms. Inscriptions ending one way always sit beside a physical change made at that spot — a fitting pulled, a line cut, a panel left off. Inscriptions ending the other way never do. One candidate reading is request versus refusal, but the same correlation also fits completed versus pending records. These cases provide a hypothesis, not a decoded grammatical distinction. A second context that distinguishes those readings is still needed before the player can know what the being is asking.

Answering it, concretely. The proposed later reading is that the most recent inscription asks for the seals to be closed. If further evidence establishes that reading, answering means performing that act for the one it will shut in. Leaving the seals open is the alternative, with healing still dangerous. A player who never decodes the inscription can still close them for practical reasons. The being's reason remains open, and the semantic evidence that would establish this request is not yet designed.

A survivor with bounded evidence. Yeva ran the hospital's plant and pressure systems: she knows which machines humans installed and which were already here, and that the core team came back different. She reads neither script. Her stake is Dorn, treated after the seals opened, changing in a way she cannot name.

Three discoveries that change what the player can do.

1. Marks on creatures reveal a pattern shared by certain builders' isolators. Changes, if a player-attunement branch is selected: recognised marks allow passage. An evidence-only branch instead makes this a clue to treatment and its bypasses; it grants no automatic player access power.
2. Ward logs show healing was stable until the seals opened. Changes: the regulators can isolate the contaminated repair template while preserving revival coverage.
3. The being's inscriptions address individual builders in sequence, the last addressing whoever comes now. Changes: it can be answered — an act the player performs, not a document they read.

Consequential actions. The apparent escape is undocking, which ends revival.

The deeper action is re-seating the builders' seals. Sealing restores the template, not the field's reach: decoupled from the one inside, the field goes back to repairing toward an ordinary human form, so healing becomes safe, no new creatures form, and revival continues working exactly as before. Continued exploration stays non-mortal. The cost of sealing is not mechanical — it cuts off the one inside, who is the party asking for it.

Sealing and answering are therefore the same act, taken for different reasons: a player who never reads the being seals a dangerous machine, and a player who does seals it because they were asked.

Player corruption — mapped to the three options, not chosen here. Resurrection and Corruption sets out three, and this story supports all three without changing.

• Evidence only. Marks appear and mean something, and revival stays ordinary. Cost: the menace stays external, about Dorn and never about the player.
• Voluntary treatment. A discovered treatment offers real capability at a readable hazard the player accepts knowingly — a genuine third option rather than a variant of the others.
• Marks advance with repeated revival, granting passage through pattern-reading isolators. Accumulating marks that gate access are tracked state, whether or not a number is shown. The honest consequence is that deliberate death becomes a visible way to buy access.

Safe carried property does not by itself rule out a corruption hazard; property and person are separate stakes. Systems recommends the first as ordinary rule with the second as a player-facing branch, and that recommendation is a proposal rather than owner canon. This article deliberately does not choose.

Option B — the one that left

The premise this changes: the captive being. In the owner's draft the core holds one; here it holds nothing alive. The creative cost, plainly: the draft's strongest image goes, and with it a prisoner to free and a person to answer, replaced by a machine with no one inside — colder, and giving the player nothing that can reply.

The ancient aim. The same attempt succeeded: the ascendant stopped needing the field and left, and the builders sealed the core and went, because the engine would not stop and there was no longer anyone it was for.

The core, and the failed intervention. The core holds the engine's retained template of the departed — a mould, not a body. Researchers who opened the seals took it for a patient and tried to treat it; treating a template corrupted it, and every body repaired since has been mended toward a corrupted mould. Legacies are as above, plus approach machinery that admits candidates and turns others back. Ship revival is the same intake registration.

Shifts with a direction, and their cost. The collar cycle re-seats fabric toward the core, since the engine reads each arrival as a candidate approaching. Trigger: the intake cycle. Limits: movable builders' fabric only. Cost: the station grows harder to cross without nearing the core, and repeated death accelerates it — though a carried regulator part damps the steering, so it can be declined.

This is not a reason to prefer B. Directed shifting does not require an empty core — a captive drawing architecture toward itself works equally well, and Option A can have it. It is a map question separable from the prisoner-versus-empty choice, and it now sits beneath the owner's selected direction: whatever is bound stays bound, and steering describes only how the unbound remainder moves. Each option could motivate that steering differently — an engine seeking a candidate, or a captive pulling the station toward itself — and neither needs it.

Both alien languages, and the survivor. The builders' script, and the departed one's, which the engine reproduces: its structure names a candidate, so a player who learns it can read which name the engine currently holds. Yeva is as above, and her stake is that Dorn's name has started appearing.

Three discoveries that change what the player can do. Late human notes in a script no human could have known — the player can read who is held. The core holds a mould, not a body — the throne can be approached rather than feared. The shifts have a direction — a damper can be carried to stop being steered.

Consequential actions. Undocking ends revival. The deeper action is that the engine will take a template: supplying a stable one stops the drift and the creatures, and binds whoever is used — including the astronaut.

Recommendation

Option A. It keeps the captive image the owner leaned toward and could let the same physical act mean either making treatment safe or answering a person. Its unresolved cost is that the second reading still needs convincing semantic evidence; the current inscription correlation does not establish it.

Option B's advantage is not directional shifting, which either option can have. It is that a machine with nothing inside is a colder explanation, and that its final act — supplying a template, possibly the astronaut's own — implicates the player rather than asking a favour. Its cost remains the prisoner: nothing left to answer, and the owner's strongest image gone.