**Status.** A finite index 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.

| Source | SHA-256 | Bytes |

| Mechanical Interfaces and Opening Quantities | `2e604fc2f31cf044237ae622658a110f34f2d40f4793f9f1bba455ef6c21697e` | 44,079 |

The index uses the source revisions above. A later change to a cited observation or state boundary requires checking its consumers; a new revision alone does not rename the underlying room, person or object.

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

**Established identities:** scene IDs Y1–I3 belong to Cast and Short Rescue Map; R01–R40 and M01–M24 to Station Room and Module Inventory; objective numbers 1–12 to Regional Discovery Map. **L1–L4 and S1–S4 are index labels here for the four numbered chains in Two Language Discovery Map and Story and Ending Map respectively.** Those parents do not literally define these prefixed IDs. Room32 already uses L2 as shorthand for the second language chain; this index preserves that reference without inventing a parent-owned ID register.

**Evidence aliases:** every `A-…` key below is a locally created index handle for observations in the cited source descriptions. The source-owner table below names those descriptions and the player decisions they inform. A handle can group the readings needed for one comparison; it is not a new object or a promise that the game captures a whole sequence in one action. No established identity is renumbered, and parents need not adopt these aliases.

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

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

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

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

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

| `A-WARDLOG` | R13 early ward records: read injuries and restoration before the later correction pattern | Fact: what was recorded before the change | Dated | That revival itself caused anything | Player | S2 |

| `A-R18SEAL` | R18: the sealed boundary itself, separate from the cycle evidence below | **Physical fact the player can act on** | Boundary state current | Who moved anyone | Player, by being there | D1, D3, S3 |

| `A-CYCLE` | R18 fixed destination drawer/card and exposed non-reversing ratchet: inspect and capture the cycle evidence | Fact: a cycle occurred | Dated capture | Who or what was moved | Player | D3, S3 |

**One observation, several kinds of consumer.** `A-TRANSFER` feeds L3 as a role distinction and S3 as movement evidence; `A-REPLY` feeds L4 as register evidence and S2/S4 as evidence about what the line is; `A-PROFILE` feeds S2 causally and Y3/M3 as something a person reacts to. Shared observations are reused; distinct stages still require their own actual captures.

**Each comparison needs its actual observations.** The initial side-by-side active-profile/bypass test needs both committed outcomes; it has no additional earlier-capture prerequisite. Comparing behavior **before and after isolation** does require a before-capture the player actually made. Two post-isolation results establish only current disconnection. No prior record is generated retroactively.

| Boundary | Required prior fact | Local action | What commits | Affected 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 consuming chain | Interrupted before commit yields nothing | None; a dated fact stays valid |

| Prepare a crossing | Route walked this life; abort room stocked; retreat armed; handed-over canister at the route's authored full-attempt return mark | Hand over air; survivor confirms flow | Prepared | Y1, A1, D1, M1, I1 | **A shift invalidates the route check and returns the state to Waiting. It does not spend anything:** only gas actually breathed or transferred and material actually consumed are spent, and committed supplies stay at their actual locations as instances | Every element rechecked after a shift |

These are Regional25's two viable orders. The arrows are **dependency priorities, not corridors**; current access can interleave eligible objectives, and either order can defer R-3 until its short geometry exists.

**Build-and-ship first — 1 → 2 → 3 → 4 → 8 → 6 → 10, then 5 → 7 → 9 → 11 → 12.** Objective 1 supplies `A-INSTALLED` at R02/R03 and `A-BERTH`; the first death makes routes historical while those facts stay current, which is S1's whole opening. Objectives 2, 3, 4 and 8 earn movement, impact and positional parts and expose the physical wall/panel/slab differences used by L2 at 1 and 8, before systematic language comparison. Seeing those differences does not automatically grant their interpretation. **Objective 6 completes without language**, from gauges and the long access, so `A-R18SEAL`, `A-CYCLE` and D1 are available before L2's shortcut is understood; 10 then exposes the conditional apparent-departure preparation. Only afterwards do 5, 7 and 9 supply `A-RUNS`, `A-TAAN`, `A-TRANSFER`, `A-AB`, `A-ADDRESS` and `A-REPLY`, which **reinterpret evidence already stored** rather than unlocking it. Objective 11 asks for the same physical pressure-equalisation action it always asks for; the language routes make it predictable, never optional. Objective 12 depends on authored placement and a selected joining rule — not on 10, rescue, treatment or an ending.

**Language-and-network first — 1 → 5 → 7 → 3 → 6 → 9 → 4 → 8 → 11 → 2 → 10 → 12.** Riskier observation comes early: 5 and 7 give L1/L3 before most parts exist, and tested predictions shorten 6 and 9. Objective 4 arrives late, so R-3 and its rescue wait for a current short geometry — and **no chain stalls**, because 5, 7, 9 and 11 never require a survivor. Objective 11's iris is reached before the ship assemblies are complete; the physical action is identical. `A-STRIP` is therefore available early here and late in the other order, which changes when the three-record chronology can be assembled but not what it supports.

**What differs, and what does not.** No chain changes hands and no evidence changes meaning between the orders; what changes is *when* a record becomes available to compare and how much reinterpretation happens after the fact. Rescues and survivor help are optional in both.

**Yeva-first versus Aster-first is a compact subcase, not a substitute for either order.** It selects which person occupies R13 and which takes the R19 annex or R22 booth, and therefore which follow-up scene appears early. It sits inside either dependency order and changes no objective sequence, no evidence and no chain.

**1 — Retained evidence, changed access.** `A-WALLMARK` from R17 survives death with its place and life; the route to R17 is historical. The mark's meaning is unaffected, but whether that wall is passable **now** is current-only and needs a fresh visit.

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

**3 — Absent versus uninformed participant.** `A-PROFILE` is committed. If Dorn was never rescued, Y3 has no Dorn variant and nothing is lost invisibly. If Dorn is aboard but has not been shown the comparison, he is **present and uninformed** — a different state, and his knowledge does not update by proximity.

| Story30's personal variants are not chain-indexed: v1→S1, v2→S2, v3→S2+S4, v4→S3, v5→S2+S4 | Read them as scene variants, not chain numbers; link here | Story30 five-variant list; Cast31 scene rows | **Link suffices** |

**Nothing here requires a parent edit to be correct**, because this article changes no rule; it records what the existing pages say and where they disagree. Two optional tags are the only parent changes named, and no tagging cascade is proposed to spread these aliases.

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