2026-09-15 14:57:45
Anonymous:
Make the language journal readable through player examples
hold the flood/language and journal.md ..
@@ 1,69 1,80 @@
-
# Hold The Horde — Language and Journal
+
# Language and Journal
-
This page is the journal contract for [Language Expedition](/Hold%20The%20Flood/Language%20Expedition), extending [Clues and Help](/Hold%20The%20Flood/Clues%20and%20Help) and [Oxygen and Observation](/Hold%20The%20Flood/Oxygen%20and%20Observation). The station shifts on death ([Owner Brief](/Hold%20The%20Flood/Brief)), so old inscriptions, locations, route links and arrival records describe the configuration observed at the time and cannot promise current connectivity; a different destination after a shift does not by itself refute a language interpretation.
+
You reach a junction between horde fights. Two doorway inscriptions use the same groups of signs in a different order. You frame and capture them with their doorways visible, then open the journal. **The whole game pauses: enemies, oxygen and unfinished actions stop, even during combat.**
-
## Record the test, not correctness
+
Pin the records beside each other, zoom in and highlight the swapped groups. Your note might say: “Does the first group describe what this place is for?” Close the journal and follow one way. In the pump hall, a great pump main ends at the machinery while a cable main crosses the room. The signs have given you a reason to look at the architecture differently.
-
The journal preserves what was observed, supports comparison and records a voluntary test. It never grades freeform notes, labels a hypothesis supported/disproved or declares a word solved. For a route link it may record only **arrived at linked destination**, **attempt incomplete** or **arrived elsewhere**, with the actual place and interruption attached. Survivor help is attributed testimony, not system truth.
+
That is the journal’s purpose: carry observations between places, give you time to think and help you choose an experiment. Recognition becomes a prediction you can act on. Later evidence may change the note; its earlier wording remains part of your discovery.
-
This reversible feedback separates a completed traversal from an interrupted one while leaving later evidence free to change the interpretation.
+
## What you can do with a record
-
## The information cycle
+
A record is one player-framed still, with its visible context, place, capture time and observed arrangement. Anything outside that frame remains unrecorded. Getting a new angle, watching motion, operating a machine and committing each capture happen while the world runs. The pause lets you examine stored evidence and the frozen view already visible to the astronaut. It cannot finish or batch-complete captures, or reveal a later state.
-
| Step | Player interaction | What the game may assert | What remains the player’s |
-
|---|---|---|---|
-
| Acquire | Frame and commit an inscription with visible context and location | Captured pixels, place and time; nothing outside the frame | What mattered, what was omitted, whether to spend time while the game runs |
-
| Compare | Pin records side by side; zoom; manually highlight candidate recurring groups | Which crops the player linked; an optional visual-match suggestion is labelled software-generated | Whether marks are the same sign, word or role |
-
| Interpret | Write a freeform note; optionally link the current route to a stored destination as a prediction | The note’s authorship and revision history; the selected links, not their truth | Meaning, confidence and generalisation |
-
| Test | Commit the link, leave the journal and traverse voluntarily | The location actually reached, or why the attempt ended before arrival | Whether the local route claim survived and what it says about language |
-
| Ask | Show a specific record or comparison to a survivor | Speaker, exact statement and stated basis | Whether to trust, combine or challenge it |
-
| Retain | Reopen after death or on a revisit | Original record, annotations, testimony and past result | Reinterpretation under the new context |
+
| Tool | Your action | What is kept |
+
|---|---|---|
+
| Comparison | Pin records, zoom and manually highlight recurring groups | Your chosen crops and links, marked as player-linked |
+
| Notes | Write a guess, quotation or plan; revise it later | Freeform wording and earlier revisions, without parsing, grading or scoring |
+
| Prediction and result | Voluntarily link a route or control to a stored destination or expected outcome, then test it outside the journal | The selected link and the actual arrival, visible state or interruption |
+
| Testimony | Show a specific record or comparison to a survivor | Who spoke, the statement, their firsthand basis and their interpretation |
-
Capture, positioning, waiting and manipulation happen while the game runs, with its oxygen/exposure. Opening, comparing and annotating pause the game, including enemies and oxygen during combat. A paused view cannot reveal a new angle, sample a later state, operate a control or complete capture.
+
On request, the recorder can suggest a **visually similar record you already captured**. Suggestions are labelled software-generated and can be wrong. They help bring distant observations together; you decide whether the marks belong together and what they mean. Manual comparison remains available throughout. The journal does not fill a translated dictionary, award correctness or uncover unseen sites.
-
## Additions to the current journal
+
## The builders’ language: which main ends here?
-
The existing framed still, visible context and location remain. This page adds four tools:
+
The [Language Expedition](/Hold%20The%20Flood/Language%20Expedition) uses three existing ways: Pump Hall, Cable Junction and a stair-only vestibule. Here the recorded shapes are represented by readable placeholders:
-
1. **Comparison board.** The player pins records and highlights groups; links say “player-linked.” On-request visual suggestions are fallible recorder assistance, not automatic pairing or meaning.
-
2. **Revision-preserving notes.** Editing keeps earlier wording, so contradiction shows learning rather than rewriting history. Freeform text is never parsed for meaning.
-
3. **Prediction/result pair.** The player links a route/control to a stored destination/outcome; afterwards the journal attaches the place, state or interruption. Selected records drive it, and it awards no correctness or rule.
-
4. **Attributed help.** A response records who spoke, what they did or saw and what is interpretation. One record cannot reveal unseen inscriptions.
+
- Pump Hall’s way: `KETH SORAN VEL`.
+
- Cable Junction’s way: `SORAN KETH VEL`.
+
- The vestibule’s way: `TAAN`.
-
Automatic semantic labels, a confirmed dictionary, batch completion and undiscovered-site hints are excluded. All four additions survive return and death as knowledge. A revisit never overwrites an old still or outcome: the player captures a new state beside it, so an earlier arrival remains historical rather than promising the route is unchanged.
+
In Pump Hall, the pump main ends and the cable main crosses. In Cable Junction, the cable main ends in banked connections while the pump main continues. A small cooling pump also ends there, visibly fed by a local branch. The useful comparison is **which of the two continuous mains ends**, rather than every piece of equipment in the room.
-
## Applying the contract to both languages
+
Swapped order now tracks an observable difference. “First position describes the primary purpose; the rest qualify it” becomes a useful working reading. Compound place names remain possible. The short `TAAN` run fits the stair-only case, but one short inscription settles little. The journal keeps the captures and places reached; the grammatical inference remains yours.
-
### Builders’ ordered language
+
If Yeva is aboard, she can identify the crew’s “pump road” and “cable road” from a shown record because she worked this spine. Those attributed names supply place references, not a translation or the positional rule. Either room can be visited first, and repeated physical examples support an unaided reading. A later valid control test may challenge your generalisation; an interrupted observation does not.
-
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.
+
## The visitors’ language: which end receives?
-
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.
+
The visitors wrote in a different hand. One use of their language places related marks at opposite ends of a transfer. At the junction you record a half written here as `OSH·a`, with another token beside it. Much later, reached by the long route, a far bay has `OSH·b` beside a receiving fitting; its builders’ inscription begins `SORAN`.
-
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.
+
The direction comes from other observations. Across two or three previously recorded transfer pairs, a driving device visibly pushes into a line and a vessel at the other end fills. One extra token recurs at driving ends, another at receiving ends. Those actions support a local source/receiver distinction without telling you everything either token means.
-
### Visitors’ paired language
+
Pin the junction and far-bay records. Their additional tokens match the driving and receiving roles respectively. A lookalike suggestion may surface their shared bracket shape; recognizing the roles is your inference. The builders’ runs independently suggest cabling. Together, the two languages point toward a particular connection worth investigating.
-
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 partial local role interpretation — a source/destination distinction in this distributed register — without settling either token’s full meaning or a rule for the entire visitors’ language.
+
There is physical reason to try: beside the junction mark, a conduit enters a human-sized maintenance continuation where you previously turned back on supply. At the far bay, the receiving fitting stands beside another maintenance opening. Material can pass where a person cannot, so neither the paired marks nor those separate openings prove a continuous walkable route or an oxygen saving. You may link the continuation to the far-bay record and attempt it, or use the long route already walked.
-
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.
+
Yeva says she never read the visitors’ hand. Her road names cannot supply this inference. Missing `OSH·a` need not end the investigation: another persistent pair can reveal the paired use, and the builders’ runs alone support a weaker route hypothesis. Richer examples of both languages are in the [Two Language Discovery Map](/Hold%20The%20Flood/Two%20Language%20Discovery%20Map).
-
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.
+
## What a test tells you
-
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 time and oxygen while the game runs and reveals a destination; a detour may interrupt the work planned for that expedition. Every item still carried comes home on death, 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.
+
A voluntary route test attaches one factual result to your prediction:
-
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.
+
| Recorded result | What actually happened |
+
|---|---|
+
| **Arrived at linked destination** | You continuously traversed the candidate and emerged at the identified destination you selected. |
+
| **Arrived elsewhere** | You fully traversed it to a different identified terminal, with no unresolved continuation; the actual place is recorded. |
+
| **Attempt incomplete** | A blockage, intermediate junction, unresolved branch, retreat, abandonment, interruption or death ended the attempt before that terminal. The interruption is attached. |
-
## Withheld correctness versus limited confirmation
+
A different terminal can challenge the proposed route without disproving the transfer roles. A blocked passage tells you about present access. It does not establish that the inscription was misunderstood. Even a wrong reading may predict one journey correctly; further comparisons matter.
-
**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.
+
Controls follow the same principle. A powered, intact control in a valid state, with its relevant component and completed activation, can yield a recorded visible result. Missing power, a removed component or unfinished work leaves absent test conditions or an incomplete attempt, rather than linguistic disproof. You judge what the observation bears on.
-
**Limited 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 kept. Their cost is some reduction in unaided noticing. 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. The player still words the hypothesis, judges whether an observation bears on it, reconciles human knowledge and pays the in-game cost of acting. The other costs are outcome states, comparison consistency and a risk that even factual status labels feel more authoritative than intended.
+
Testing costs live time, oxygen and exposure, and may consume the rest of an expedition. You can press on, retreat where practical or return through death with everything still carried. Already consumed oxygen/material stays spent; installed or handed-over objects stay outside the carried set. Temporary combat growth ends at home. Your records, notes, testimony and previous results remain.
-
[Language Design Evidence](/Hold%20The%20Flood/Language%20Design%20Evidence) describes shipped uses of uncertainty, candidate meanings, repeated contexts and validation. Its multiple-context precedent supports planned redundancy, not a mandatory instance count.
+
## An old record is still useful
-
## Open questions
+
Capturing a place again adds a dated record beside the earlier one. After a death shift, both can still inform a language comparison. Their old unbound routes become historical; reaching somewhere different in the new arrangement does not by itself refute a reading. Completed work, objects and persistent joins follow the [current continuity rules](/Hold%20The%20Flood/Death%20Shift%20And%20Rescue%20Continuity). Current neighbours and access need current observation. Neither testimony nor a matching image supplies them.
-
- How object identities and relational clues survive the station’s rearrangement on death remains to be designed.
-
- Reopen the choice to record the test rather than correctness if observation of players shows them treating arrival records as language answers, unable to diagnose attempts, or using comparison as clerical transcription; stronger confirmation or fully withheld structured feedback would then be the alternatives.
-
- These rules are untested; numbers are proposals.
+
The [moving scan](/Hold%20The%20Flood/Moving%20Scan%20Expedition) makes the distinction tangible. Its dated captures survive when a changed arrangement invalidates partial or complete instrument samples. The visible return chain rewinds the carriage from its current notch while the game runs; paused comparison cannot rescan or replay it. A living return preserves a valid partial scan for resumption, or a completed bridge for reuse. The journal preserves evidence; the instrument and walked route establish current conditions.
+
+
## Why keep factual results?
+
+
The preferred proposal records limited observations and attributed help. It saves the player from confusing a broken test with a failed interpretation while leaving the deduction, confidence and next action to them. Optional visual matching sacrifices some unaided noticing; its benefit is bringing already-owned evidence into a comparison the player can actually use.
+
+
The substantial alternative withholds structured arrival/test statuses and relies on the world and personal notes. Environmental feedback can still explain a failure, and ambiguity may feel more natural. The cost is greater difficulty separating oxygen, damage, missing power and contextual exceptions from a wrong reading. Neither approach automatically guarantees ownership of a discovery.
+
+
Factual labels can also feel too authoritative. Comparison, result states, repeated contexts and testimony need consistent authoring, and “record everything, sort later” can turn attention into clerical work. The [language-design precedents](/Hold%20The%20Flood/Language%20Design%20Evidence) support repeated contexts, without establishing a universal number of examples for this game.
+
+
Revisit this proposal if later player observation shows that statuses are treated as translations, attempts remain hard to diagnose or comparison becomes transcription. Stronger confirmation and fully withheld structured feedback remain alternatives; the owner’s full journal pause stays in place.
+
+
These tools and examples remain design proposals. Continue with [Clues and Help](/Hold%20The%20Flood/Clues%20and%20Help) for practical inference and survivor advice, [Oxygen and Observation](/Hold%20The%20Flood/Oxygen%20and%20Observation) for live observation, or [Player Information and Options](/Hold%20The%20Flood/Player%20Information%20And%20Options) for the journal’s layout and controls.
