**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 |

**Intervening revisions, stated rather than hidden.** Six of these moved under the Systems 528 alignment while this article was stopped. Every room, control and object fact cited below was re-verified against the **new** revisions; the R03, R13, R18, R19, R32 and R36 rows this article depends on are unchanged by those edits. Where a Systems edit later changes a cited passage, the finding here is what needs rechecking, not the identity map.

**Not canonical:** every `A-…` evidence key below. **Language29 defines no evidence keys at all**, and neither does any other parent. An earlier draft of this page implied two classes — that `E-…` keys were canonical and only `X-…` keys were invented — and that was wrong: **all of them are locally invented indexing aliases created by this article**, and every one carries a proposed source owner. Nothing here renumbers or renames an established room, scene, chain, module or objective identity, and no parent needs to adopt these keys for its own text to be correct.

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

| **Y3** The profile is not the person | Cast31; Story30 variant 2 | Ship | `A-PROFILE` |

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

| **D3** What crossed | Cast31; Story30 variant 4 | Ship ledger table/receiver | `A-WALLLOG`, `A-LEDGER`, `A-SEALACCOUNT`, `A-CYCLE` |

| **M3** A machine made this | Cast31; Story30 variant 3 | Ship tray/evidence shelf | `A-PROFILE`, `A-ISOLATION` |

| **I3** Ask before treatment | Cast31; Story30 variant 5 | Ship | `A-TREAT` |

**Host variants (7).** R13 hosts Y1 **or** A1, never both; the other person 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 consumers. All keys are local aliases (§0).

| 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 give L2 its broad wall-access reading at 1 and 8 **before** any language work. **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.