commit c3e5f8

Commit `c3e5f8`

2026-09-14 19:13:33 Anonymous: Remove text slop: disclaimers, process metadata, restatements and hedge tags; no rule changes (owner readability review, 14 Sep)

`hold the flood/paired transfer discovery detail.md` ..
@@ 1,6 1,6 @@
	# Hold The Horde — Paired Transfer Discovery Detail

-	Status. One M4 detail sample: Two Language Discovery Map's chain 3, the visitors' paired transfer register, worked to the depth a writer and a level author could build from. It adds no room, mechanism, encounter, person or objective, answers no central mystery, and fixes no story as canon. Everything new is a string or an occurrence inside an existing host, and each is flagged where it appears. All five owner questions remain unanswered.
+	This page works out chain 3 of the Two Language Discovery Map — the visitors' paired transfer register, one chain of four — to the depth a writer and a level author could build from.

	## 1. The discovery, as it plays

@@ 16,23 16,23 @@

	## 2. Occurrence and evidence inventory

-	All hosts exist in Station Room and Module Inventory; all identities are reused. `A-TRANSFER` is the crosswalk's index alias for the shared observation.
+	All hosts are existing rooms in the Station Room and Module Inventory. `A-TRANSFER` is the crosswalk's index alias for the shared observation.

	\| Occurrence \| Host (existing) \| What is physically there \| Status \|
	\|---\|---\|---\|---\|
-	\| Pair 1, both ends \| R21 Drive Pair Bay (O7, M13) \| Driving screw and filling vessel in one room; bracket halves and one role token at each end \| Existing pair; role tokens and bracket form newly proposed \|
-	\| Pair 2, both ends \| R22 Receiving Supply Booth (O7, M17) \| Second complete pair; the receiving fitting's token also appears in an utterance body slot (the existing cross-register case) \| Existing pair; bracket form newly proposed \|
-	\| Pair 3, both ends \| R23 Material Sorting Bay (O7, M13, encounter 7) \| Corrective third pair, on separated evidence stations under the existing Veilbearer/Boltspitter placement \| Existing pair; the suffix flip is the newly proposed detail \|
+	\| Pair 1, both ends \| R21 Drive Pair Bay (O7, M13) \| Driving screw and filling vessel in one room; bracket halves and one role token at each end \| Existing pair; role tokens and bracket form new \|
+	\| Pair 2, both ends \| R22 Receiving Supply Booth (O7, M17) \| Second complete pair; the receiving fitting's token also appears in an utterance body slot (the existing cross-register case) \| Existing pair; bracket form new \|
+	\| Pair 3, both ends \| R23 Material Sorting Bay (O7, M13, encounter 7) \| Corrective third pair, on separated evidence stations under the existing Veilbearer/Boltspitter placement \| Existing pair; the suffix flip is the new detail \|
	\| Framing and choice position \| R24 Transfer Service Gallery (O7, M04) \| Three sight-separated branch mouths; the player frames pair records and picks the uncertain continuation from here \| Existing; no change \|
	\| `OSH·a`, untested pair \| R15 Cable Junction (O5, M11) \| Existing `OSH·a` beside the existing open wall crawl — the untraversed continuation \| Existing token and host \|
	\| `OSH·b`, untested pair \| R18 Sealed Receiving Section (O6, M18) \| Existing far-bay `OSH·b` beside the receiving fitting, in a bay whose builders' run begins `SORAN`; the existing non-reversing ratchet sits in the same room \| Existing token and host \|
-	\| Later application \| R36 Pressure-Receiver Vault (O11, M22) \| Existing `OSH·b` beside the existing inward flow arrow \| Existing; relationship deliberately left open (§5) \|
+	\| Later application \| R36 Pressure-Receiver Vault (O11, M22) \| Existing `OSH·b` beside the existing inward flow arrow \| Existing; relationship left open (§8) \|

-	Newly proposed strings — five, all inside existing hosts: the role tokens `NEB` and `KUR`, and the bracket forms `MEV`, `ANK`, `TEL`. The supplied tokens `OSH·a`, `OSH·b`, `SORAN`, `KETH`, `VEL`, `TAAN` are preserved unchanged and none is reassigned. Nothing here is presented as pre-existing that is not.
+	New strings — five, all inside existing hosts: the role tokens `NEB` and `KUR`, and the bracket forms `MEV`, `ANK`, `TEL`. The existing tokens `OSH·a`, `OSH·b`, `SORAN`, `KETH`, `VEL`, `TAAN` are unchanged and none is reassigned.

	## 3. Inscriptions and physical tells

-	Transliteration only — no glyph art, image, model or voice is proposed, and the cut forms themselves are for a later art pass.
+	Transliteration only — no glyph art, image, model or voice; the cut forms themselves are for a later art pass.

	The marks, as the player would transcribe them.

@@ 62,7 62,7 @@

	Both readings agree on which two marks are one pair, so both send the player down the same continuation at R15. The route test cannot adjudicate between them — only operating a pair and watching can. That separation is the point of the chain, and the interface must not blur it.

-	Other rivals the source names stay live and are not refuted here: pair identity without direction; ownership rather than flow; the pair marks material flow but not passage; visually similar brackets being unrelated.
+	Other rival readings the source page names stay live: pair identity without direction; ownership rather than flow; the pair marks material flow but not passage; visually similar brackets being unrelated.

	The third pair. If the player generalised from the suffix, R23 is a correction: their rule fails against a machine they can watch as long as they like. If they used the role token, R23 is redundancy and confirms it. Either way nothing is graded, no badge appears, and the earlier note keeps its original wording in revision history.

@@ 77,21 77,21 @@
	\| Death before a terminal \| Attempt incomplete; every still-carried item returns once; spent oxygen stays spent \| The trip ended there \| No penalty is added and no record is lost \|
	\| Revisit after a shift \| A new capture beside the old one \| The current state of what is now there \| The old route claim becomes historical and is drawn as such; it never re-labels itself current \|

-	The pair observation at R21/R22/R23 is unaffected by every one of these. A complete local transfer observation remains valid when a route application fails — the player learned a role rule from machines and a walkability fact from walking, and only the second one was tested.
+	A complete local transfer observation remains valid when a route application fails: the pair observations at R21/R22/R23 are unaffected by every one of these outcomes — the player learned a role rule from machines and a walkability fact from walking, and only the second one was tested.

	## 5. Orders, missing evidence, help and later use

-	Language-and-network first (`1→5→7→3→6→9→4→8→11→2→10→12`). Objective 5 comes before 7, so the player meets `OSH·a` at R15 beside a crawl before any pair teaches them what a bracketed half-mark is. It reads as one more unexplained mark. Objective 7 then supplies three pairs and the role rule, and the R15 record becomes retroactively legible — the reinterpretation the design keeps asking for. Objective 6 follows, and R18's `OSH·b` completes the pair.
+	Language-and-network first (`1→5→7→3→6→9→4→8→11→2→10→12`). Objective 5 comes before 7, so the player meets `OSH·a` at R15 beside a crawl before any pair teaches them what a bracketed half-mark is. It reads as one more unexplained mark. Objective 7 then supplies three pairs and the role rule, and the R15 record becomes retroactively readable — the reinterpretation the design keeps asking for. Objective 6 follows, and R18's `OSH·b` completes the pair.

	Build-and-ship first (`1→2→3→4→8→6→10`, then `5→7→9→11→12`). The order is inverted: objective 6 comes early, so R18's `OSH·b` is seen before the pairs exist, and R15's `OSH·a` is not seen until objective 5, late. The player accumulates two halves of a pair they cannot yet recognise as a pair, then meets the pairs afterwards. The chain still completes, and the route attempt is available whenever both halves are recorded; what changes is how much of the work is recognition rather than discovery.

-	Evidence out of order or missing. With one pair the directional hypothesis is unsupported and the interface says nothing; the player may still attempt the continuation on a guess and get a real arrival record. With two agreeing pairs the suffix rule and the role rule are indistinguishable, which is the intended trap. With R23 only and neither earlier pair, there is one observation and no rule. If the R15 half is never found, the far-bay `OSH·b` stays an isolated mark; if the R18 half is never found, the R15 continuation is a route with no predicted destination — the player can walk it as ordinary exploration. No objective is gated on any of this: Regional Discovery Map keeps the authored long route and gauges viable, and objective 6 completes from gauges and long access without language.
+	Evidence out of order or missing. With one pair the directional hypothesis is unsupported and the interface says nothing; the player may still attempt the continuation on a guess and get a real arrival record. With two agreeing pairs the suffix rule and the role rule are indistinguishable, which is the intended trap. With R23 only and neither earlier pair, there is one observation and no rule. If the R15 half is never found, the far-bay `OSH·b` stays an isolated mark; if the R18 half is never found, the R15 continuation is a route with no predicted destination — the player can walk it as ordinary exploration. No objective is gated on any of this: Regional Discovery Map keeps the long route and gauges viable, and objective 6 completes from gauges and long access without language.

-	Optional survivor help, requiring no unselected first survivor. Whoever is aboard responds only to a record the player deliberately shows them, and only from their own basis. A survivor may say that crews used the maintenance crawls, or that a bay of that kind received rather than sent — attributed testimony with its stated basis. No survivor reads either script, none knows current topology, and every chain-3 step is completable with nobody aboard. Nothing is withheld to protect the deduction.
+	Optional survivor help, which does not depend on the first survivor (not yet chosen). Whoever is aboard responds only to a record the player deliberately shows them, and only from their own basis. A survivor may say that crews used the maintenance crawls, or that a bay of that kind received rather than sent — attributed testimony with its stated basis. No survivor reads either script, none knows current topology, and every chain-3 step is completable with nobody aboard. Nothing is withheld to protect the deduction.

-	Later use. The role rule makes objective 6's redirected pressure line and objective 11's inward receiver more predictable. At R36 the existing `OSH·b` sits beside an existing inward flow arrow, and a player holding the role rule has a consistent expectation there while a suffix-only reader has no rule left after R23. What that third `OSH·b` occurrence means is deliberately not answered here — repeated pair identity, a class mark, or a different fitting reusing the form are all open, and settling it belongs to the language map, not to this sample.
+	Later use. The role rule makes objective 6's redirected pressure line and objective 11's inward receiver more predictable. At R36 the existing `OSH·b` sits beside an existing inward flow arrow, and a player holding the role rule has a consistent expectation there while a suffix-only reader has no rule left after R23. What that third `OSH·b` occurrence means is an open question (§8).

-	Time and provenance. Framing and committing a capture, operating a fixture and traversing a continuation are world actions with oxygen and threats running. Opening the journal freezes enemies, oxygen, projectiles, readiness, mechanisms, warnings and work progress and completes none of them; comparison and annotation happen there. The display refuses to translate a token, to mark a note right or wrong, to name a direction the player has not watched, or to show a route not walked.
+	Time and provenance. Framing and committing a capture, operating a fixture and traversing a continuation all happen while the game runs, with oxygen and threats running. Opening the journal freezes enemies, oxygen, projectiles, readiness, mechanisms, warnings and work progress and completes none of them; comparison and annotation happen there. The display refuses to translate a token, to mark a note right or wrong, to name a direction the player has not watched, or to show a route not walked.

	## 6. State, cues and recovery

@@ 106,18 106,21 @@

	Cue text examples (plain, no verdicts): "Plate: `MEV·a NEB`. Screw advancing." — "Collar: `TEL·a KUR`. Vessel filling in steps." — "Arrived elsewhere: terminal outlet at [named anchor]." — "Attempt incomplete: branch unresolved."

-	Recovery choices. A wrong reading is corrected by walking to another pair and watching it, which costs a trip and no progress. A failed route costs oxygen, exposure and possibly the expedition's remaining objective window; carried property still returns on death, so no equipment loss is added. A shift makes the walked continuation historical and a fresh check necessary; the pair observations and the role rule survive untouched, because they were never claims about geography.
-
-	Materially distinct cases this sample covers — twelve: one pair only; two agreeing pairs; three pairs with the suffix rule broken; three pairs with the role rule confirmed; arrival at the linked destination; arrival elsewhere; incomplete by blockage; incomplete by retreat; incomplete by death; revisit after a shift; the far half missing; the near half missing. What remains later: every string occurrence across the whole station, the other three chains at this depth, the full cross-register relationship with chain 4, exact fixture geometry and timing, the R36 `OSH·b` question, and any art or audio.
+	Recovery choices. A wrong reading is corrected by walking to another pair and watching it, which costs a trip and no progress. A failed route costs oxygen, exposure and possibly the expedition's remaining objective window. A shift makes the walked continuation historical and a fresh check necessary; the pair observations and the role rule survive untouched, because they were never claims about geography.

	## 7. Content and authoring requirements

-	Exactly what is new, deduplicated against first-pass material: five strings (`NEB`, `KUR`, `MEV`, `ANK`, `TEL`); eight plate occurrences across five existing hosts (R21×2, R22×2, R23×2, R15×1, R18×1); one authored asymmetry (R23's suffix flip); five physical tell types (advancing head, check flap, stepped level, vent puff, overflow residue) reused across all four pairs rather than authored per site; and four record-description templates. No new room, module, mechanism, encounter, creature, person, scene, objective or portable object. Every host, the R24 framing position, the R15 crawl, the R18 ratchet and the R36 arrow are existing first-pass content.
+	What is new: the five strings listed in §2, in eight plate occurrences across five existing hosts (R21×2, R22×2, R23×2, R15×1, R18×1); the R23 suffix flip; five physical tell types (advancing head, check flap, stepped level, vent puff, overflow residue) reused across all four pairs rather than authored per site; and four record-description templates. No new room, module, mechanism, encounter, creature, person, scene, objective or portable object.

-	Added burden that is real: the R23 asymmetry must be authored deliberately and must survive later editing, or the correction silently disappears; the role tokens must be legible at the distance a player actually stands; and the eight occurrences must each be capturable under the existing encounter placement at R23 without the Veilbearer's sheet making a station uncapturable.
+	Added authoring burden: the R23 asymmetry must be authored deliberately and must survive later editing, or the correction silently disappears; the role tokens must be readable at the distance a player actually stands; and the eight occurrences must each be capturable under the existing encounter placement at R23 without the Veilbearer's sheet making a station uncapturable.

-	A cheaper authored alternative. Drop the role tokens and let the half-mark carry direction consistently — `·a` always drives — with the third pair as pure redundancy. That removes three strings, the asymmetry and the correction, and makes the chain a two-observation confirmation. Its discovery cost is the whole middle of the chain: there is no wrong rule to hold, no moment where a tidy note fails against a machine, and no reason to visit the third pair except completeness. What survives is the genuinely good part — direction learned by watching rather than reading — and what is lost is the only place where the player is wrong in an interesting way. The proposed version retains the correction step at the cost of additional authoring; the simpler alternative remains available.
+	A cheaper alternative. Drop the role tokens and let the half-mark carry direction consistently — `·a` always drives — with the third pair as pure redundancy. That removes three strings, the asymmetry and the correction, and makes the chain a two-observation confirmation. Its discovery cost is the whole middle of the chain: there is no wrong rule to hold, no moment where a tidy note fails against a machine, and no reason to visit the third pair except completeness. What survives is the genuinely good part — direction learned by watching rather than reading — and what is lost is the only place where the player is wrong in an interesting way.

-	## 8. Coverage and limits
+	## 8. Open questions

-	This is one chain of four at sample depth, not a language specification. It establishes no meaning for `OSH` or any other token, does not say why the visitors marked anything, does not resolve the third `OSH·b` occurrence, and fixes no story as canon. Nothing here shows that the trap is fair, that the correction lands, that the tokens are legible or that any of it is enjoyable; those need later owner-authorised implementation and observation with real players, and none has occurred.
+	- What the third `OSH·b` occurrence at R36 means: repeated pair identity, a class mark, or a different fitting reusing the form. Settling it belongs to the language map.
+	- Whether to keep the role tokens and the R23 correction step, or the cheaper alternative in §7 (`·a` always drives; the third pair as pure redundancy).
+	- The meaning of `OSH` and the other tokens, and why the visitors marked anything.
+	- The five owner questions on the Two Language Discovery Map remain unanswered.
+	- Still to be worked out: every string occurrence across the whole station; the other three chains at this depth; the full cross-register relationship with chain 4; exact fixture geometry and timing; art and audio.
+	- These rules are untested; numbers are proposals.

Commit c3e5f8

Commit `c3e5f8`