**Status.** A finite crosswalk over content that already exists: it maps the eight accepted chains and fifteen primary cast scenes onto the actual rooms, controls, objects and observations they consume, and records where those interfaces agree or conflict. It is **not** a campaign map, a scheduler, new content, story truth, language grammar or a validation of anything. No new chain, person, room, mechanism, scene or object is created here. All five owner questions remain unanswered, and only their actual consumers are marked conditional.

**Sources read live.** Brief `4b0a3bcb…`; Two Language Discovery Map `df0f48f5…`; Story and Ending Map `03c9cb8e…`; Cast and Short Rescue Map `61ff0b96…`; Station Room and Module Inventory `7ba1e1ab…`; Encounter and Mechanism Placement Inventory `acbf9d31…`; Player Information and Options `61e0be4a…`; Regional Discovery Map `3acda018…`; Save and Content State `7da78548…`; Death Shift and Rescue Continuity `577236e7…`. The last four cast/room/encounter/save versions are the 514-aligned ones accepted at 518. **Mechanical Interfaces and Opening Quantities is under review and is not used**; cells that genuinely depend on it are marked *(35-dependent)* and left provisional rather than filled with invented quantities.

**Counts.** 8 chains (L1–L4, S1–S4) · 15 primary scenes (Y1–Y3, A1–A3, D1–D3, M1–M3, I1–I3) · **19 deduplicated evidence entries** · 7 mutually exclusive rescue host variants · 5 Story30 personal variants · 2 progression orders. Existing inventories are unchanged: 24 modules / 40 rooms, 10 encounters including 2 setpieces, 13 major mechanisms.

Canonical IDs are reused. **L1–L4** are Two Language Discovery Map's four chains; **S1–S4** are Story and Ending Map's four mystery/personal chains; **Y1–I3** are Cast and Short Rescue Map's fifteen scenes. Where an observation has no ID anywhere, this article names a **local crosswalk key** (`X-…`) and proposes an owner; a key is a handle for something that already exists, never a new object.

| ID | Owning description | Rooms / controls | Evidence consumed |

|---|---|---|---|

| **L1** Which main ends here? | Language29 chain 1 | R14, R15, R16; the two service mains | `E-RUNS`, `E-TAAN` |

| **L2** What is behind the marked wall? | Language29 chain 2 | R04, R15 edge, R17, R26 slab | `E-WALLMARK` |

| **L3** Which end receives? | Language29 chain 3 | R21, R22, R23 one-way fixtures | `E-TRANSFER` |

| **L4** Does the line answer? | Language29 chain 4 | R28–R30 racks and reply niche; R36 iris panel | `E-AB`, `E-REPLY`, `E-ADDRESS` |

| **S1** The berth that remembers | Story30 chain 1 | R01/R02 fasteners and installed Fork; ship berth | `X-BERTH`, `X-MANIFEST`, `E-INSTALLED` |

| **S2** The harmful profile | Story30 chain 2 | R19 comparison bay, R28 regulators, R40 coupling | `X-PROFILE`, `X-TREAT`, `E-REPLY` |

| **S3** The last transfer | Story30 chain 3 | R18 seal, R24/R22 ledger sites; ship table/receiver | `X-WALLLOG`, `X-LEDGER`, `X-SEAL`, `X-CYCLE`, `E-TRANSFER` |

| **S4** What the core contains | Story30 chain 4 | R28–R30 reply, R36 iris, R39 cell, R40 isolation | `E-REPLY`, `E-CELL`, `E-ISOLATION` |

| **Y1** The wall must come | Cast31 | R13 if Yeva-first, else R19 annex; one junction; R12 abort | `X-WALLLOG` |

| **Y2** The dark bench | Cast31; Home28 projects 1/2 | Ship bench, inherited compressor head/housing | — (state, not evidence) |

| **Y3** The profile is not the person | Cast31; Story30 v2 | Ship | `X-PROFILE` |

| **A1** Lock behind me | Cast31 | R13 if Aster-first, else R22 booth; R24 or R12 abort | — |

| **A2** Count only what we have | Cast31; Home28 project 3 | Ship ledger table | `X-LEDGER` |

| **A3** This docking, perhaps | Cast31; Story30 v1 | Ship berth/table | `X-BERTH`, `X-MANIFEST` |

| **D1** Keep the section shut? | Cast31 | R18, R17 approach, R12 abort; hoist control seat | `X-SEAL` |

| **D2** Two leads, one Fork | Cast31; Coming Home, Home28 1/2 | Ship receiver/bench | — |

| **D3** What crossed | Cast31; Story30 v4 | Ship ledger table/receiver | `X-WALLLOG`, `X-LEDGER`, `X-SEAL`, `X-CYCLE` |

| **M1** Clean side | Cast31 | R26 booth, R27 clean abort; rack seal | `E-RACK` |

| **M2** Catch, don't spend | Cast31; Home28 project 4 | Ship material tray/cradle | — |

| **M3** A machine made this | Cast31; Story30 v3 | Ship tray/evidence shelf | `X-PROFILE` |

| **I1** My pace | Cast31 | R05 bay, R06 braced alcove; approach plate | — |

| **I2** Two actual passes | Cast31; Home28 project 5 | Ship gait rail | — |

| **I3** Ask before treatment | Cast31; Story30 v5 | Ship | `X-TREAT` |

**Host variants (7), stated so no cell reads as a free reuse.** R13 hosts Y1 **or** A1, never both; the loser takes R19 pressure annex (Yeva) or R22 supply booth (Aster). Abort hosts are the four already counted rooms — R06, R12, R24, R27 — and no scene adds a fifth.

One entry per observation. A shared observation is listed once with its separate linguistic and narrative consumers.

| Key | Host and action | Fact vs interpretation | Current or dated | Cannot prove | Who knows, and how | Consumers | Decision it changes |

|---|---|---|---|---|---|---|---|

| `E-RUNS` | R14/R15: read which main ends, which crosses | Fact: which main terminates. Interpretation: token order means purpose | Dated capture | That the rule generalises beyond these rooms | Player by looking; Yeva names the roads from having worked them | L1 | Which service control to try first |

| `E-TAAN` | R16: bare string over a stair-only vestibule | Fact: string and room type. Interpretation: single-token meaning | Dated capture | That `TAAN` is a damaged run rather than a name | Player only | L1 | Whether the positional reading holds |

| `E-WALLMARK` | R04, R15 edge, R17, R26: matching strings beside panels/slabs | Fact: string, panel state, whether a crawl is continuous | Dated capture; **passability is current-only** | That any marked wall is passable now | Player only | L2 | Spend cutter time on a bypass instead of the jammed door |

| `E-TRANSFER` | R21/R23: operate a one-way pair; R22 receiving fitting | Fact: physical drive/fill direction. Interpretation: which token is source or receiver | Dated capture | That a transfer pair implies a walkable route | Player; Aster's ledger names dates, not direction | L3, S3 | Predict a direction, investigate a continuation |

| `E-AB` | R14, R15, R21, R22, R23: five pulled/intact A/B contrasts | Fact: plate state beside a physical change | Dated capture | Whether A means completed, requested or foretold | Player only | L4 | Do the named work, defer with a B plate, or ignore |

| `E-ADDRESS` | R14, R15, R23 workstations: token from that fitting in the first slot | Fact: token recurrence. Interpretation: address slot | Dated capture | That the register has one grammar | Player only | L4 | Which fitting an utterance concerns |

| `E-REPLY` | R28–R30: R1–R4 chronology and the reply protocol | Fact: the line responds to a named act | Response is **current**; the chronology is dated | That a responder is a person | Player only; no survivor reads either script | L4, S2, S4 | Whether the line can be answered at all |

| `E-CELL` | R39: deep evidence cell behind the opened iris | Fact: what is physically there | Dated capture | Which account of the core is right | Player only | S4 | Which reading of the core survives |

| `E-ISOLATION` | R40: coupling live tell; re-seat, leave or postpone | Fact: coupling live or dark | **Current only** — a tell, not a record | That re-seating made any ward safe | Player at the room | S2, S4 | Re-seat, leave coupled, or postpone |

| `E-INSTALLED` | R02 and elsewhere: an installed part's known location | Fact: it is installed at a named room | Fact stays current; the **route** goes historical | That a current route to it exists | Player | S1 | Reclaim now or accept the trip later |

| `E-RACK` | R26: purge the local rack or seal it in place | Fact: contents consumed or preserved | Current state | That preserved contents will be reachable later | Player; Mara knows her own rack | M1 | Purge or preserve |

| `X-WALLLOG` *(proposed owner: Cast31 Y1; alias "the wall log")* | R13/R19: photograph the ward pressure log in exposed world time | Fact: dated fittings and readings. Interpretation: why they stopped | Dated capture | Who moved anyone, or why | Yeva measured it herself; the player only if captured | Y1, D3, S3 | Capture under pressure, or cross now |

| `X-BERTH` *(proposed owner: Story30 S1; alias "berth trace")* | Ship berth: commit one diagnostic capture | Fact: the trace exists and reads a certain way | Dated capture | Why revival happens | Player; Aster once shown | A3, S1 | Show it, or keep her wider theory intact |

| `X-MANIFEST` *(proposed owner: Save/global04; alias "post-death comparison")* | Ship: compare manifest and world state across one death | Fact: what returned and what did not | Current, per generation | That the station rewound | Player | A3, S1 | Treat departure and installation as different commitments |

| `X-LEDGER` *(proposed owner: Cast31 A2; alias "Aster's ledger")* | Ship table: register a dated entry with provenance | Fact: dated movements | Dated; **never present contents** | What is in a room now, or a route | Aster brought it; the player reads only registered material | A2, D3, S3 | Which records to align |

| `X-SEAL` *(proposed owner: Cast31 D1/D3; alias "Dorn's seal account")* | R18 seal, then his account aboard | His testimony, attributed — not a system fact | Dated testimony | That nobody crossed | Dorn only, from being there | D1, D3, S3 | Use the side route or commit the direct opening |

| `X-CYCLE` *(proposed owner: Cast31 D3; alias "destination pressure-cycle records")* | R18/R24 destination fittings: capture cycle records | Fact: a cycle occurred | Dated capture | Who or what was moved | Player | D3, S3 | Confront the late-transfer record |

| `X-PROFILE` *(proposed owner: Story30 S2; alias "culture/profile comparison")* | R19: committed active/bypass or post-isolation capture | Fact: the observed result. Interpretation: cause | Dated capture | That all revival corrupts | Player; Yeva, Dorn and Mara only if shown | Y3, M3, S2 | Target one human-configured line, or admit cause unknown |

| `X-TREAT` *(proposed owner: Story30 S2/v5; alias "treatment preview")* | Recorded access benefit, hostile correction cue, purge evidence | Fact: benefit and hazard as observed | Current state; the record is dated | That treatment is safe | Player; Ivo only if shown before the act | I3, S2 | Accept, refuse, defer or purge |

**One observation, two kinds of consumer.** `E-TRANSFER` feeds L3 as a linguistic role distinction and S3 as evidence about a movement; `E-REPLY` feeds L4 as register evidence and S2/S4 as evidence about what the line is; `X-PROFILE` feeds S2 as causal evidence and Y3/M3 as something a person reacts to. Each is captured once and consumed several times — no duplicate capture is implied anywhere.

| Boundary | Required prior fact | Local action or observation | What commits | Affected scene or choice | Death or interruption | Current-only recheck |

|---|---|---|---|---|---|---|

| Capture a dated record | Be at the host, in world time | Frame and commit one still | One record with place, life and limit | Every chain consuming it | Interrupted before commit yields nothing | None — a record stays valid as a dated fact |

| Retain an inference | A capture exists | Player writes a note | The note, never graded | L1–L4 readings | Nothing lost; notes survive death | None |

| **Inform a survivor** | The record exists **and that person is aboard and present** | Show it to them, deliberately | Their attributed response | Y3, A3, D3, M3, I3 | Deferring changes nothing unseen | Their knowledge does not update by proximity |

| Answer the line | `E-REPLY` understood enough to act | Do the named work at R28–R30 or R36 | The response observed | L4, S4 | Unfinished stage lost, completed stages persist | The response is current; re-observe it |

| Re-seat isolation | Reach R40 | World-time mechanical work | Coupling state changes | S2, S4 | Completed work persists | Ward consequence requires a **direct revisit**; no remote verdict |

| Latch a seam | Compatible adjacent faces now | Hand-cycle at the seam | A persistent join | Objective 12 | Join survives death | Adjacency is current-only; the join is not |

| Prepare a crossing | Route walked **this life**; abort room stocked; air at the full-attempt return mark; retreat armed | Hand over air; survivor confirms flow | Prepared | Y1, A1, D1, M1, I1 | A shift returns the state to Waiting with supplies spent | Every element must be rechecked after a shift |

| Send | The same person aboard **and the ship airlock closed** before the lethal boundary | Physical arrival | Sent | Home scenes unlock | Death before closure: world outcome per the conditional safeguard, **astronaut knowledge stays unconfirmed** | Proof needs local observation at the refuge |

**Three separations this crosswalk insists on.** *Retaining an inference is not informing a survivor* — a player may hold a correct reading for hours while every person aboard still knows nothing, and no scene fires on the inference alone. *A control responding is not proof of identity or history* — `E-REPLY` shows that something answers, never who or what. *Physical network completion is not an ending theory* — joining every room is a walkable fact under objective 12; what the core contains is S4, and neither settles the other. The full transaction, storage and display rules are not restated here; see the accepted continuity, Save and Content State, and Player Information and Options.

**Trace A — Yeva-first.** Objective 1 gives the R-3 bearing. `E-INSTALLED` records the Fork at R02 the moment it is installed, and the first death makes the route to it historical while the fact stays current — this is S1's opening evidence before any story reading exists. A later short current geometry at objective 4 enables **Y1** at R13: the player captures `X-WALLLOG` in exposed world time or crosses immediately. After Sent, **Y2** shows the bench *setup incomplete*, because Dorn has not serviced the inherited head — a state, not a refusal. Objectives 5 and 7 proceed with no survivor testimony at all: `E-RUNS`, `E-TAAN`, `E-AB` and `E-TRANSFER` are player-only. Yeva's road names remain attributed help, never translation. **D1** later needs its own walked side route; **D2** completes the receiver, and only then can a demonstrated cycle exist. Aster enters when objective 7's booth has a verified short route, bringing `X-LEDGER` for **A2**.

**Trace B — Aster-first.** **A1** occupies R13 and **A2** gives a first-return comparison with no other project visible. After an ordinary death, **A3** puts `X-BERTH` beside `X-MANIFEST`: with both she retracts "every arrival" and keeps "this docking may"; with one she keeps the wider theory. Yeva later occupies the objective-6 pressure annex — **never R13** — so **Y1**'s host moves while its evidence and choice do not. Every physical language path is identical in both orders, because L1–L4 consume no testimony.

**Contrary case 1 — retained evidence, changed access.** The player holds `E-WALLMARK` from R17 and dies. The record keeps its place and life; the route to R17 is historical. The mark's *meaning* is unaffected, but whether that wall is passable **now** is a current-only fact requiring a fresh visit. Nothing in the ledger promises the room is reachable this generation.

**Contrary case 2 — wrong interpretation, concrete correction.** From two `E-TRANSFER` pairs the player reads the recurring token as *source* and predicts a continuation. The corrective third pair at R23 shows the same token at a receiving end. The correction is physical and self-administered: no interface says "wrong", the earlier note keeps its original wording in revision history, and L3's decision — which continuation to investigate — changes on the player's own reading.

**Contrary case 3 — absent versus uninformed participant.** `X-PROFILE` is committed. If Dorn was never rescued, **Y3** has no Dorn variant and nothing is lost invisibly. If Dorn is aboard but was never shown the comparison, he is **present and uninformed** — a different state, and the scene must not let his knowledge update by proximity. The crosswalk treats these as two distinct rows, because collapsing them would make sharing meaningless.

**Contrary case 4 — apparent versus deeper ending, with the departure branch open.** Objective 10's assemblies can make departure readiness true with no language, survivor or core answer — an *apparent* ending path. The deeper transaction at R40 is separate and does not require it. **The departure branch is unresolved and stays that way here:** the in-world irreversibility (leaving the field ends revival and closes station exploration in this continuity) is distinct from the unanswered save policy, and this article selects neither. Completing objective 12 is a physical fact that neither triggers nor blocks either.

| Finding | Smallest remedy | Source, hash and owning paragraph | Writer transfer needed? |

|---|---|---|---|

| **Numbering collision.** Story30's personal variants 1–5 do not correspond to chains S1–S4: v1→S1, v2→S2, v3→S2, v4→S3, v5→S2. A reader can easily take "variant 3" for chain 3. | Label them "personal variant N (chain S*x*)" in one line | Story30 `03c9cb8e…`, the five-variant list; Cast31 `61ff0b96…` scene rows | Yes if edited — otherwise **a link to this crosswalk suffices** |

| **No cast scene allocates to S4.** The four chains receive 1/3/1/**0** variants. S4's human positions exist in Story30 prose but no numbered scene owns them. | Record the gap; do **not** invent a sixteenth scene | Story30 chain 4; Cast31 15-scene ledger | No — this is a reported coverage gap for owner/PM decision |

| **Story30 v2's open question is already answered.** It says "one shared scene must still be assigned to both arcs explicitly"; Cast31 assigns Y3 with Yeva primary and Dorn as participant-if-present. | One cross-link | Story30 v2 line; Cast31 Y3 row | No — a link suffices |

| **L2's four hosts, two tags.** Room32 tags R04 and R17 with "chain L2" but not the R15 edge or the R26 slab, though L2 uses all four. | Add the tag to two room rows, or accept the chain article as the authority | Room32 `7ba1e1ab…` R15 and R26 rows | Yes if tagged — low value; a link suffices |

| **Seven observations had no ID anywhere.** `X-WALLLOG`, `X-BERTH`, `X-MANIFEST`, `X-LEDGER`, `X-SEAL`, `X-CYCLE`, `X-PROFILE`, `X-TREAT`. | Adopt these keys, or assign the proposed owners' own IDs | This article; proposed owners named per row | Only if the owners want their own IDs |

| **Quantities left provisional.** Air margins, capacity figures and any launch rule behind a crossing. | Fill after Mechanical35 is dispositioned | *(35-dependent)* | No |

**Where a link is enough:** every cross-article reference above except the two tagging cases. Nothing in this crosswalk requires a parent edit to be correct, because it changes no rule — it records what the existing articles already say and where they disagree.

**Complete for what was assigned:** all 8 chains and all 15 primary scenes are mapped, both progression orders are traced, and the evidence ledger is deduplicated across them. **Not covered, and not claimed:** the full occurrence/branch/failure variants of each chain, exhaustive permutations of order and participation, any glyph or string catalogue, and the exact behaviour of anything owned by Mechanical35. Ten encounters, two setpieces and thirteen mechanisms are referenced only through their owning rooms; this article adds none.

Nothing here establishes that the chains are discoverable, that the corrections land, or that any scene is affecting. Those need later owner-authorised implementation and observation, and none has occurred.