2026-09-09 11:35:06
Anonymous:
Response to critique 529 / PM 531: ledger completed to 26 entries, room corrections (R03/R18, ledger as carried object), seal fact split from testimony, many-to-many chain mapping, both Regional25 dependency orders, identifier provenance audit, state wording corrections, Mechanical35 endpoints
hold the flood/campaign evidence and state crosswalk.md ..
@@ 1,115 1,168 @@
# Hold The Horde — Campaign Evidence and State Crosswalk
-
**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.
+
**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.
-
**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.
+
**Sources read live for this revision, with full hashes.**
**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.
**Canonical, cited to their owners:** chain IDs L1–L4 (Two Language Discovery Map), S1–S4 (Story and Ending Map), scene IDs Y1–I3 (Cast and Short Rescue Map), room IDs R01–R40 and module IDs M01–M24 (Station Room and Module Inventory), objective numbers 1–12 (Regional Discovery Map).
-
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.
+
**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.
**Scenes carry chain positions many-to-many.** Story30 does not allocate its personal variants exclusively to one chain each, and reading them as 1:1 was an error in the earlier draft:
+
+
| Scene | Story30 variant | Chain positions it carries |
+
|---|---|---|
+
| A3 | 1 | S1 |
+
| Y3 | 2 | S2 |
+
| M3 | 3 | **S2 and S4** — preserving a trace before a live feed is disconnected is evidence stewardship about the profile *and* about the isolation act |
+
| D3 | 4 | S3 |
+
| I3 | 5 | **S2 and S4** — the consent boundary concerns the treatment *and* the core branch that Story30 names in its chain-4 human paragraph |
-
**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.
+
**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.
## 2. Deduplicated evidence and knowledge ledger
-
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.
+
One entry per observation; a shared observation is listed once with its separate consumers. All keys are local aliases (§0).
+
+
| Key | Host and action | Fact vs interpretation | Current or dated | Cannot prove | Who knows, and how | Consumers |
+
|---|---|---|---|---|---|---|
+
| `A-RUNS` | R14/R15: read which main ends, which crosses | Fact: which main terminates. Interpretation: order means purpose | Dated capture | That the rule generalises | Player; **Yeva may name the crew roads** when shown a record | L1 |
+
| `A-TAAN` | R16: bare string over a stair-only vestibule | Fact: string and room type | Dated capture | That it is not a damaged run | Player | L1 |
+
| `A-WALLMARK` | R04, R15 edge, R17, R26 slab: 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; **Dorn may describe crew crawl-mark use** when shown a record | L2 |
+
| `A-TRANSFER` | R21/R23 operate a pair; R22 receiving fitting | Fact: physical drive/fill direction | Dated capture | That a pair implies a walkable route | Player | L3, S3 |
+
| `A-AB` | R14, R15, R21, R22, R23: five pulled/intact contrasts | Fact: plate state beside a physical change | Dated capture | Whether A means completed, requested or foretold | Player | L4 |
+
| `A-ADDRESS` | R14, R15, R23 workstations: fitting token in the first slot | Fact: token recurrence | Dated capture | That the register has one grammar | Player | L4 |
+
| `A-REPLY` | R28–R30 chronology and reply protocol; R36 inlet plate/reply face | Fact: the line responds to a named act | Response **current**; chronology dated | That a responder is a person | Player; no survivor reads either script | L4, S2, S4 |
+
| `A-CORENOTES` | R32: layered human notes calling the core patient, engine, prisoner | Fact: the notes and their layering | Dated | Which account is right; layering is not chronology unless physically evidenced | Player | S4 |
+
| `A-CELL` | R39: deep evidence cell behind the opened iris | Fact: what is physically there | Dated capture | Which reading of the core survives | Player | S4 |
+
| `A-STRIP` | R36: trapped builder-style seal-service strip beneath a later human adapter | Fact: physical layering and a punched value | Dated | Ancient authorship; that remains an inference | Player | S4, chronology |
+
| `A-ISOLATION` | R40: coupling live tell; re-seat, leave or postpone | Fact: coupling live or dark | **Current only** — a tell, not a record | That any ward became safe | Player at the room | S2, S4, M3 |
+
| `A-INSTALLED` | R02 installed Fork; R03 staged fasteners | Fact: installed/completed at a named room | Fact current; the **route** goes historical | That a current route exists | Player | S1 |
+
| `A-RACK` | R26: purge the local rack or seal it in place | Fact: contents consumed or preserved | Current | That preserved contents stay reachable | Player; Mara knows her rack | M1 |
+
| `A-WALLLOG` | R13/R19: photograph the ward pressure log in exposed world time | Fact: dated fittings and readings | Dated capture | Who moved anyone, or why | Yeva measured it; player only if captured | Y1, D3, S3 |
+
| `A-BEDSIDE` | R13: the early restoration record at the patient's bed | Fact: a historical restoration occurred there | Dated | Why revival happens, or that it still works that way | Player | S1 |
+
| `A-WARDLOG` | Early ward logs | Fact: what was recorded before the change | Dated | That revival itself caused anything | Player | S2 |
+
| `A-WARDID` | R13 active ward-machine identifier; R19 matching tissue record; a creature carrying a matching pattern | Fact: the identifier matches across three places | Dated captures | That the machine caused the creature | Player | S2 |
+
| `A-PROFILE` | R19: committed active/bypass or post-isolation capture | Fact: the observed result. Interpretation: cause | Dated capture | That all revival corrupts | Player; Yeva, Dorn, Mara only if shown | Y3, M3, S2 |
+
| `A-CARD` | R19: profile-commissioning card, its transcribed found value and installed profile revision | Fact: the fields as written | Dated | That the transcription is correct or the strip unreplaced | Player | S2, chronology |
+
| `A-BERTH` | Ship / objective 1: berth intake trace, active profile-revision field, observed docking registration | Fact: the trace and its fields | Dated capture | Why revival happens; no calendar conversion | Player; Aster once shown | A3, S1, chronology |
+
| `A-MANIFEST` | 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 |
+
| `A-LEDGER` | Aster's **physical ledger, carried aboard**; register a dated entry at the ship table | Fact: dated movements | Dated; **never present contents** | What is in a room now, or a route | Aster brought it; player reads registered material | A2, D3, S3 |
+
| `A-R18SEAL` | R18: the sealed boundary itself, destination drawer/card, exposed non-reversing ratchet | **Physical fact the player can act on** | Drawer/card dated; boundary state current | Who moved anyone | Player, by being there | D1, D3, S3 |
+
| `A-SEALACCOUNT` | Dorn's account of sealing it | **Attributed testimony, not a system fact** | Dated testimony | That nobody crossed | Dorn, from being there; player only if he says so | D1, D3, S3 |
+
| `A-CYCLE` | R18 destination fittings: capture cycle records | Fact: a cycle occurred | Dated capture | Who or what was moved | Player | D3, S3 |
+
| `A-TREAT` | Recorded access benefit, hostile correction cue, purge evidence | Fact: benefit and hazard as observed | Record dated; treatment state current | That treatment is safe | Player; Ivo only if shown before the act | I3, S2, S4 |
+
+
**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. Each is captured once.
+
+
**The chronology is three records, not a reader.** `A-STRIP`, `A-CARD` and `A-BERTH` share explicit cross-references and together support *old seal state → human profile installation → current docking registration* **for these records only**. The player compares them in the paused journal; nothing declares the chronology true, and no diagnostic reads history.
+
+
**The comparison needs an actual earlier capture.** `A-PROFILE`'s controlled comparison requires a **before** capture that the player actually committed. Two post-isolation results establish only current disconnection. No prior record is generated retroactively to complete a comparison the player did not make.
## 3. Representative state and commit boundaries
-
| Boundary | Required prior fact | Local action or observation | What commits | Affected scene or choice | Death or interruption | Current-only recheck |
+
| 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 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 |
+
| 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 |
+
| Write or revise a note | **None** — notes are not capture-gated | Freeform writing in the pause | The note and its revision history, never graded | L1–L4 readings | Nothing lost | None |
+
| Compare or share a **particular** record | That record was committed | Pin it, or show it to a present person | The comparison, or their attributed response | Y3, A3, D3, M3, I3 | Deferring changes nothing unseen | Their knowledge does not update by proximity |
+
| Answer the line | `A-REPLY` understood enough to act | Named work at R28–R30 or R36 | The response observed | L4, S4 | Unfinished stage lost; completed stages persist | The response is current |
+
| Re-seat isolation | Reach R40 | World-time mechanical work | Coupling state changes | S2, S4 | Completed work persists | Ward consequence needs a **direct revisit** |
| 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 |
+
| 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 |
+
| Send | The same person aboard **and the ship airlock closed** before the lethal boundary | Physical arrival | Sent | Home scenes unlock | World outcome per the conditional safeguard; **astronaut knowledge stays unconfirmed** | Proof needs local observation at the refuge |
+
+
**Three separations this crosswalk insists on.** *Holding an inference is not informing a survivor* — a player may hold a correct reading indefinitely while everyone aboard still knows nothing. This is a distinction, **not an extra gate**: where a scene's own design is to show the evidence, the showing inside that scene is the informing, and no separate prior step is required. *A control responding is not proof of identity or history* — `A-REPLY` shows that something answers, never who. *Physical network completion is not an ending theory* — objective 12 is a walkable fact independent of objective 10, rescue, treatment and any ending; what the core contains is S4, and neither settles the other. Transaction, storage and display rules are not restated here.
+
+
**Optional help is real, and no chain depends on it.** L1–L4 are solvable with no person aboard. Yeva may name the crew roads and Dorn may describe crawl-mark use, each only when shown a record, each attributed with its basis, and neither reads an alien script or knows current topology. Help is not withheld to protect an intended deduction.
-
**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.
+
## 4. The two dependency orders
-
## 4. Two traces and four contrary cases
+
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.
-
**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**.
+
**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.
-
**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.
+
**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.
-
**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.
+
**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.
-
**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.
+
**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.
-
**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.
+
## 5. Four contrary cases
-
**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.
+
**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.
-
## 5. Integration handoff
+
**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.
-
| Finding | Smallest remedy | Source, hash and owning paragraph | Writer transfer needed? |
+
**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.
+
+
**4 — Apparent versus deeper ending, with the departure branch unselected.** Objective 10's assemblies can make readiness true with no language, survivor or core answer. The deeper transaction at R40 is separate and does not require it. **The departure branch is an unselected owner choice, not a settled fact:** Story30 *recommends* an irreversible apparent-credit departure — leaving the field ending revival and closing station exploration in this continuity — against the alternative of keeping readiness as a repair milestone with no departure at all, and the outline treats field-limited revival and irreversible departure as optional assumptions. Save policy is a further open question, not the whole of it. This article selects neither, and objective 12 neither triggers nor blocks either.
| **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 |
+
| 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** |
+
| No scene is *labelled* chain 4. This is a labelling gap, **not** absent human coverage: S4's positions are carried inside the isolation and treatment branches of M3 and I3 | Record the labelling gap; keep fifteen scenes and five variants | Story30 chain-4 human paragraph; Cast31 ledger | **No change; no sixteenth scene** |
+
| Story30 asks that the shared profile scene be assigned to both arcs; Cast31 already does it as Y3 with Dorn participant-if-present | One cross-link | Story30 variant 2; Cast31 Y3 | **Link suffices** |
+
| Room32 tags R04 and R17 "chain L2" but not the R15 edge or R26 slab, though L2 uses all four | Add two tags, or treat Language29 as the authority | Room32 R15 and R26 rows | Optional, low value |
+
| Twenty-six evidence observations have no ID in any parent | Adopt these aliases, or let owners assign their own | This article §0 | Only if owners want IDs |
+
+
**Quantities, no longer wholly open.** Mechanical35 is accepted and supplies the determinate endpoints: **10 C** shared carrying capacity, a **12 O** integral suit tank outside C/A, an ordinary-full canister of **8 O in a 2 C** vessel and a prepared-full of **12 O** in the same vessel, with conserved incremental transfer. What remains authored per route is the **full-attempt return mark** itself — a per-route value, not a missing model.
-
**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.
+
**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.
## Coverage and limits
-
**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.
+
**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.
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.
