2026-09-08 13:29:48
Anonymous:
Resolve focused language review (PM 254)
hold the flood/language and journal.md ..
@@ 38,27 38,27 @@
At the three-way junction the player captures `KETH SORAN VEL` above the left way, `SORAN KETH VEL` above the middle and `TAAN` above the right. They pin the first two, highlight the swapped groups and may note “first token says what a place is for; later tokens qualify it.” The note is ungraded.
-
Walking the ways is voluntary and costs ordinary oxygen/exposure. In the left room, pumps are bolted and plumbed to terminate there while cable trunking merely crosses between walls. In the middle, cables terminate in banked connections while one pump serves only that room’s cooling loop. Token order therefore correlates with what terminates rather than passes through. This supports a purpose-and-order reading over meaningless order, while compound place names remain a live rival. The bare `TAAN` above a stair-only vestibule is another consistent case, not proof. The journal records the places reached; it never marks `KETH` as “pump,” asserts a grammatical subject or upgrades the note to fact.
+
Walking the ways is voluntary and costs ordinary oxygen/exposure. Two visible mains run along this spine. In the left pump hall, the pump main terminates at the pumps while the cable main crosses between walls. The middle way reaches a cable junction and continues past it; there the cable main terminates in banked connections while the pump main crosses and carries on. A small cooling pump also terminates in the junction, but it is visibly fed by a local branch rather than forming the end of the pump main. Token order therefore correlates with which of the two mains ends in the room, not with everything that terminates there. This supports a purpose-and-order reading over meaningless order, while compound place names remain a live rival. The bare `TAAN` above a stair-only vestibule is another consistent case, not proof. The journal records the places reached; it never marks `KETH` as “pump,” asserts a grammatical subject or upgrades the note to fact.
Yeva can truthfully call the first two the crew’s pump road and cable road because she worked this spine. Her attributed gloss supplies referents, not the positional rule. The player must still compare order, interpret `TAAN` and decide whether the pattern applies elsewhere. Multiple persistent runs give an unaided route without guaranteeing every player notices it.
### Visitors’ paired language
-
The player separately records a visitor threshold half ending `OSH·a` plus a further token beside the middle doorway. Earlier, they recorded and walked another visitor pair end to end; across that pair, its further tokens consistently marked the end entered from and the end moved toward. That is an observed precedent for this register, not a rule for the entire visitors’ language.
+
The player separately records a visitor threshold half ending `OSH·a` plus a further token beside the middle doorway. Before making any prediction about the far bay, they have recorded two or three other pairs at the ends of transfers whose direction is independently visible: a driving device pushes into a line at one end, while a vessel receives and fills at the other. Across those pairs, one further token recurs at the driving end and another at the receiving end. This small comparison supports a source/destination distinction in this distributed register; it does not translate either token or establish a rule for the entire visitors’ language.
-
Much later, beside a far bay whose builder run begins `SORAN`, the player finds `OSH·b` with the corresponding “from” placement, while the junction half carries the “toward” placement. They can pin both halves and manually link them. An on-request recorder suggestion may surface the visually similar bracket token, but does not assert a semantic pair or direction; recognising how the further tokens correspond to the traversed precedent remains interpretation.
+
Much later, beside a far bay whose builder run begins `SORAN`, the player finds `OSH·b` carrying the receiving-end token, while the junction half carries the driving-end token. They can pin both halves and manually link them. An on-request recorder suggestion may surface the visually similar bracket token, but does not assert a semantic pair, relation or direction; recognising how the further tokens correspond to the observed transfers remains interpretation.
The visitor pair suggests a route from the junction toward the bay; the builder runs independently suggest both concern cabling. The player previously turned back at the junction on supply, so the passage continuing beyond it remains untraversed. They may link that continuation to the far-bay record and attempt it. The test completes only by continuously traversing the continuation and emerging at an identified outlet. Reaching the far-bay anchor records **arrived at linked destination**. Reaching a terminal outlet at another persistent anchor records **arrived elsewhere**. Neither event translates `OSH`, proves every pair is a route or confirms the builder grammar.
-
Yeva says plainly that she never read the visitors’ hand. Her road names constrain a token-to-place comparison but do not translate tokens; the visitor relation and combined route inference remain the player’s. If `OSH·a` was missed, another persistent pair can expose the distributed use, while the builder runs alone support a weaker route hypothesis. A completed wrong route consumes oxygen but reveals a destination. A blockage, intermediate junction, unanticipated branch, retreat, interruption, abandonment or death before the defined terminal records **attempt incomplete**, not “arrived elsewhere”; only a fully traversed candidate with no unresolved continuation yields an incompatible destination. The known long route or retreat remains subject to supply and threats.
+
Yeva says plainly that she never read the visitors’ hand. Her road names constrain a token-to-place comparison but do not translate tokens; the visitor relation and combined route inference remain the player’s. If `OSH·a` was missed, another persistent pair can expose the distributed use, while the builder runs alone support a weaker route hypothesis. A completed route spends world time and oxygen and reveals a destination; a detour may interrupt the work planned for that expedition. Under the owner’s death rule, every item still carried comes home, so the player may press on, retreat where practical or end the trip by dying and return aboard with that load. A blockage, intermediate junction, unanticipated branch, retreat, interruption, abandonment or death before the defined terminal records **attempt incomplete**, not “arrived elsewhere”; only a fully traversed candidate with no unresolved continuation yields an incompatible destination. Supply and threats still shape what happens before the trip ends, without requiring equipment loss or a perilous walk home.
The same distinction applies to controls. A powered, intact control with the relevant component can record the visible state after activation. Missing power, a removed component, interruption or an unfinished action records absent test conditions or an incomplete attempt—not evidence against the prediction and not a general diagnostic guarantee.
## Withheld correctness versus bounded confirmation
-
**Withhold structured result records.** The player relies on the world and their notes, with no arrival/test status. This keeps interface authority low and allows ambiguity, but does not uniquely create ownership: explicit help or an observed result can still leave comparison, generalisation and action to the player. Its cost is later diagnosis; oxygen, damage, missing power and contextual exceptions can make an unfinished test look like a failed reading.
+
**Withhold structured result records.** The player relies on the world and their notes, with no arrival/test status. This keeps interface authority low and allows ambiguity, but does not uniquely create ownership: explicit help or an observed result can still leave comparison, generalisation and action to the player. Its cost is a possible diagnostic burden; oxygen, damage, missing power and contextual exceptions can make an unfinished test harder to distinguish from a failed reading. Visible environmental evidence remains available and may explain the outcome even without a journal status.
-
**Bounded observation and help — preferred.** Record the reached place, visible control state or incomplete condition, and keep testimony attributed. The player chooses what to compare, words the hypothesis, judges whether the observation bears on it, reconciles human knowledge and pays the world cost of acting. The cost is authored outcome states, comparison consistency and a risk that even factual status labels feel more authoritative than intended.
+
**Bounded observation and help — preferred.** Record the reached place, visible control state or incomplete condition, and keep testimony attributed. On-request visual suggestions among already captured records are provisionally kept. Their accepted cost is some reduction in unaided noticing, which the earlier wording underplayed. The reason to keep them is visible in the complete episode: surfacing a lookalike only brings two records together; the player still appraises whether the halves pair, infers the source/receiver distinction from independent transfers, applies it to a new pair and chooses whether to act. Manual comparison remains fully usable. Predictions that every player will ask or that matching alone is the whole discovery are not established facts. The player still words the hypothesis, judges whether an observation bears on it, reconciles human knowledge and pays the world cost of acting. The other costs are authored outcome states, comparison consistency and a risk that even factual status labels feel more authoritative than intended.
[Language Design Evidence](/Hold%20The%20Flood/Language%20Design%20Evidence) describes shipped uses of uncertainty, candidate meanings, repeated contexts and validation, but provides no public dataset proving transfer to this oxygen-limited station. Its multiple-context precedent supports planned redundancy, not a mandatory instance count or guarantee.
