2026-09-08 13:02:24
Anonymous:
PM 246 corrections: visible terminate-versus-pass-through observation, compound naming left standing as a rival, pair direction and a traversed precedent, untraversed continuation, precise limits on Yeva's help, feedback tradeoff stated
hold the flood/language expedition.md ..
@@ 1,14 1,14 @@
# Hold The Horde — Language Expedition
-
**Status.** A provisional proposal for review, not owner-approved. It works one expedition in which two alien languages both matter, showing what the player observes, believes, tests and decides. Token strings are readable text placeholders; no glyphs, alphabets, art or vocabulary catalogue are proposed. Who the builders and visitors were is replaceable candidate fiction, and the episode depends on no central-mystery direction.
+
**Status.** A provisional proposal for review, not owner-approved. It works one expedition in which two alien languages both contribute, and shows what the player observes, believes, tests and decides. Token strings are readable text placeholders; no glyphs, alphabets, conlang or vocabulary catalogue are proposed. Who the builders and visitors were is replaceable candidate fiction, and the episode depends on no central-mystery direction.
## The two languages
-
**Builders' runs.** Left by whoever built the structure, above and beside fittings and doorways, as short ordered sequences: `KETH SORAN VEL`. The structural rule available to the player is positional — the first token is what the run is about, and the rest qualify it. The same tokens in another order make a different statement. A run is read where it stands.
+
**Builders' runs.** Left by whoever built the structure, above and beside fittings and doorways, as short ordered sequences: `KETH SORAN VEL`. The candidate rule available to the player is positional — that the first token is what the run is about and the rest qualify it. A run is read where it stands.
-
**Visitors' halves.** Left by a later species, in a visibly different hand, on the builders' surfaces. A statement is split across two places, each half carrying a matching bracket token — written here as `OSH·a` and `OSH·b`. A half alone is not a statement, and a completed pair asserts a relation between its two locations. This language can only be read by travelling.
+
**The visitors' hand.** A later species wrote on the builders' surfaces in a visibly different hand. It is a language, and the player meets one *register* of it here: marks placed at thresholds in two halves, each carrying a matching bracket token — written as `OSH·a` and `OSH·b` — plus one further token. Pairing is a property of this use, not a claim about the whole language.
-
The difference is not what they are about. It is that one is read in place and the other cannot be.
+
Acquiring a half requires being where it is. Comparing halves happens later in the paused journal, once both records exist.
## What the player sees first
@@ 24,72 24,79 @@
## Readings the player can reasonably hold
-
- The runs are place names, and the tokens are syllables.
-
- The runs describe what each way is for.
-
- The order is stylistic and means nothing; two runs with the same tokens say the same thing.
-
- The single-token run is unfinished, or damaged.
-
- The `OSH·a` mark is graffiti, or the same language written badly by someone in a hurry.
+
- The runs are compound place names built from a shared stock of elements.
+
- The runs describe what each way is for, and order carries meaning.
+
- Order is stylistic, and two runs with the same tokens say the same thing.
+
- The single-token run is unfinished or damaged.
+
- The `OSH·a` mark is graffiti, or the same language written badly.
-
None of these is silly, and the article does not rank them for the player.
+
None of these is silly. The first in particular survives a long way, and the article does not pretend otherwise.
-
## The comparison that opens it
+
## The comparison, and the observation that gives it teeth
-
The two shared-token runs are the lever. If runs were place names, two different destinations sharing two of three tokens in swapped order is strange. If order carries meaning, they are a matched pair of statements about related things.
+
The two runs share all three tokens in different order. That alone distinguishes little: two places can perfectly well carry different compound names built from the same elements.
-
That is a reason to look, not a conclusion. The **test is voluntary and physical**: walk a way and see what is there. It costs oxygen and exposure like any traversal, and it can go wrong.
+
What makes the comparison worth acting on is a **visible difference in the rooms themselves**, and it needs stating precisely, because "each is about a different thing" is not something a player can see.
-
Walking both: the left way ends in a pump hall with cable trunking running through it; the middle way ends in a cable junction with a pump feeding it. Each holds both things, and what differs is which one the place is *for*.
+
The **test is voluntary and physical**: walk a way and look. It costs oxygen and exposure like any traversal.
-
That fits the positional rule and nothing else on offer — `KETH` first over a way serving pumps, `SORAN` first over a way serving cabling, each run's second token naming what else is present.
+
- The left way ends in a pump hall. Cable trunking crosses it — entering one wall, leaving another, terminating nowhere. The pumps are bolted down, plumbed in and end here.
+
- The middle way ends in a cable junction. The cables terminate: they fan into banked connections that go no further. A pump stands there too, feeding only that room's own cooling loop.
-
## What settles it enough to act on
+
So the observable is *what terminates here and what merely passes through*. In each room both systems are present, and only one of them ends.
-
The right way's single token, `TAAN`, over a stair the player has already used and knows leads to a vestibule with nothing in it but the stair.
+
That correlates with the token order. `KETH` leads over the way to the room where pumps terminate; `SORAN` leads over the way where cabling terminates.
-
Under the place-name reading, a one-token name among three-token names is odd. Under the positional rule it is exactly right: a bare subject with nothing to qualify — a place that is *about* only itself.
+
**What this supports, and what it does not.** It supports the purpose-and-order reading over the stylistic one, because order tracks something real. It does **not** eliminate compound naming: two places could be named from the same elements in different orders for reasons the player cannot see, and the correlation would look identical. The player leaves with a working rule, not a proof, and that is the honest state of it.
-
This does not prove the rule. It is a third instance consistent with it and awkward for the rivals, which is the honest state of the evidence, and enough to make a decision on.
+
`TAAN` over the right way adds a third case: a stair to a vestibule where nothing terminates and nothing passes through but the stair itself. That sits comfortably with a bare subject having nothing to qualify. On its own it settles little — a short name among long ones is unremarkable — but it fits the rule without strain.
+
+
## The visitors' register, and what a pair actually says
+
+
A pair is not only a link. Across pairs the player has completed, the *further* token differs between halves in a consistent way: one recurs at places they entered from, the other at places they moved toward. A completed pair therefore points.
+
+
That matters because of something the player already did. Earlier, they completed a pair whose halves sat at the two ends of a passage they walked end to end — their own evidence that this species marked the ends of ways they used, and which end was which.
## Where the second language earns its place
-
Much later, deep on the far side of the station and reached the long way round, the player finds `OSH·b` beside a bay whose own builders' run begins `SORAN`.
+
Much later, deep on the far side and reached the long way round, the player finds `OSH·b` beside a bay whose builders' run begins `SORAN`.
-
Now both halves exist and the pair can be read as a statement: these two places stand in some relation. It does not say what relation, and it does not say how to get from one to the other.
+
`OSH·a` at the junction carries the "toward" token; `OSH·b` at the bay carries the "from" token. Under the precedent the player established by walking one themselves, this pair marks a way the visitors used, running from the junction toward that bay.
-
But the builders' run at that bay says it is a place *about* cabling, and the junction's middle way says the same. Two independent languages, one saying what a place is for and the other saying these two places are related, together support a claim neither makes alone: the middle way probably reaches this bay.
+
There is also an untraversed continuation. The middle way was walked only as far as the cable junction, where the player turned back on supply; a passage runs on past it and has never been followed.
-
**Neither language is redundant.** Without the runs, the pair relates two anonymous places. Without the pair, two places are merely about the same subject, which is true of many places.
+
**What each language contributes here.** The pair asserts a visitor route between two specific places and gives its direction. The builders' runs say the middle way and the far bay are both about cabling, which is consistent with the pair rather than proof of it. Together they make attempting the continuation reasoned. Neither is claimed to be indispensable in general, and a player with only the runs has a weaker version of the same idea.
## The choice, and the cost of being wrong
-
The player can take the middle way, which they now predict comes out at the far bay, instead of the long route they have walked before. Shorter, less exposure, less oxygen.
+
The player can follow the continuation past the cable junction, expecting to come out at the far bay, instead of the long route they have walked before. If it connects, that is **expected** to be shorter and cheaper in oxygen and exposure — expected, not guaranteed, until they have actually done it.
-
If the reading is wrong they find out by arriving somewhere else, and they see where they actually are — information rather than a refusal. They have spent the attempt's oxygen and must fall back on the known route, subject to the station's state and their supply.
+
If the reading is wrong they find out by arriving somewhere else, and they see where they are: information rather than a refusal. They have spent the attempt's oxygen and must fall back on the known route, subject to the station's state and their remaining supply.
-
A wrong *rule* fails the same way and teaches more: a player who decided the last token is the subject predicts differently, walks, and finds the prediction broken in a specific place with the run still on the wall above them.
+
A wrong *rule* fails the same way and teaches more: a player who decided the last token is the subject predicts differently, walks, and finds the prediction broken in a specific place with the run still above them.
## Recovering from a wrong guess or a missed clue
-
Runs are plural and persistent, so none is load-bearing. Any two sharing tokens in different order support the same comparison, and any short run among long ones does the work `TAAN` does. Visitors' pairs recur, and a player who completes none still has the runs, which support a weaker but real version of the route decision.
+
Runs and pairs recur, so no single instance is load-bearing. A player who missed `OSH·a` can learn the paired structure from another pair; a player who never completes one still has the builders' runs and the weaker route hypothesis they support.
-
The design does not claim universal access. A player who never compares occurrences may not reach the positional rule, and the survivor route below does not fix that, because it hands over referents rather than the rule.
+
What the design does not claim is that any two swapped runs, or any short run, will do the same work. The rooms in this episode carry a visible terminate-or-pass-through difference; a different pair of rooms might carry nothing comparable. Nor does it claim universal access: a player who never compares occurrences may not reach the positional rule, and the survivor route does not fix that.
## Truthful, bounded survivor help
-
Yeva worked this spine for years and can say what the crew called two of the ways: the pump road and the cable road. That is true human practice, honestly reported, and she says plainly it is what the crew called them and not what the writing says.
+
Yeva worked this spine for years. She can say what the crew called two of the ways — the pump road and the cable road — and she says plainly that this is what the crew called them, not what the writing says.
-
It gives the player referents for `KETH` and `SORAN` at a stroke.
+
**Precisely what that gives.** It does not translate a token. It fixes which *place* each run sits above without the player walking there, so runs can be lined up against known destinations from the record alone. The token-to-purpose mapping, the positional rule, and whether order carries meaning at all remain inferred.
-
**What remains after asking.** The positional rule is untouched: knowing one way is the pump road does not say whether the first or last token names it, and the player must still compare the runs to see order doing work. `TAAN` stays unexplained. The visitors' hand stays wholly unexplained, because Yeva never read it and says so. The route inference still has to be made, and can still be wrong.
+
She never read the visitors' hand and says so, so the pair, its direction and the route inference stay with the player. Help shortens the road without walking it, and the unaided player is not treated as the only legitimate one.
-
Help shortens the road without walking it, and the unaided player is not treated as the only legitimate one.
+
## The feedback tradeoff, stated fairly
-
## What this proposes and what it leaves open
+
Withholding a correctness badge does not by itself maximise ownership, and explicit help does not by itself remove thinking. The real difference is diagnosis.
-
Proposed: two languages distinguished by structure rather than subject matter; a positional rule and a paired-halves rule small enough to infer from a handful of instances; physical traversal as the test; and a route decision that both languages contribute to.
+
Bounded confirmation — recording that a stated local prediction *matched here* — costs some ambiguity and risks a status label reading as more authoritative than intended. Withholding it preserves ambiguity, but a sound hypothesis can look wrong because of an unpowered control, a blocked passage, low supply or a death that ended the attempt, and the player cannot tell which. **I accept the first cost**, because in this episode the thing being confirmed is where the player arrived, never what a token means.
-
Aligned with the interface contract: a committed world test may record that a prediction matched or did not match *here*, without ever declaring a token correct. That is the right shape for this episode — walking the middle way confirms what the player found at the end of it, not that the first token is the subject. The rule stays theirs to hold or abandon.
+
## What remains open
-
Open, and belonging to [Language and Journal](/Hold%20The%20Flood/Language%20and%20Journal): how records are compared and revised, and whether a completed pair is flagged as related or left for the player to notice. The episode works either way, though the second changes how much thinking remains.
+
How records are compared and revised, and whether a completed pair is surfaced as visually similar or left entirely for the player to notice, belong to [Language and Journal](/Hold%20The%20Flood/Language%20and%20Journal). This episode works under either answer, though the second changes how much thinking remains.
-
Also open: what these tokens mean beyond the referents Yeva supplies, who the visitors were, and why they wrote across the builders' walls. Nothing here establishes that inferring a positional rule is enjoyable, or that players will test rather than wait to be told.
+
Also open: what these tokens mean beyond the placement Yeva's road names allow, who the visitors were, and why they wrote across the builders' walls. Nothing here establishes that inferring a positional rule is enjoyable, or that players will test rather than wait to be told.
