Commit 004045

2026-09-08 13:43:55 Anonymous: PM final integration: observable language lead and owner carried-return consistency

hold the flood/language and journal.md ..
@@ 44,11 44,11 @@
	### Visitors’ paired 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.
+	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 supports a partial local role interpretation without settling either token’s full meaning or a rule for the entire visitors’ language.
	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.
+	The visitor pair suggests a transfer connection from the junction toward the bay; the builder runs independently suggest both concern cabling. A transfer connection does not prove a walkable route. Beside the source mark, a conduit enters a human-sized maintenance passage continuing beyond the junction; at the far bay, the receiving fitting stands beside another maintenance opening. The player previously turned back at the junction on supply. Those visible accesses make the untraversed continuation worth investigating for a possible connector, without establishing continuity, destination or a shorter journey. 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 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.