Breach-Ward Three-Route Transfer / 裂缝病区三路转运线

The breach-ward route map has always named three exits: public rescue, the white-glove garage, and the fan oxygen corridor. The playable transfer previously exposed only public accountability and generic internal containment. This storyline makes the promised third route real and records who receives the ward evidence before the unauthorized memorial appears.

This is a custody-routing storyline, not a medical diagnosis or a memorial licence. It answers one narrow question: after the ward transfer, whose chain can produce the ledger for the next reader?

Beat 1 — Carry a real ward ledger

storyteller-rite-ward-12-three-route-transfer remains state-driven and requires card-storyteller-breach-ward-ledger. The ledger proves that a treatment and handoff record exists. It does not prove identity, personhood, diagnosis, consent, voice ownership, archive ownership, or memorial authority.

The two existing assignment slots remain stable so older ward and Ai Sheng paths do not change shape. The sponsor/permit side and inspector side must both be represented by in-hand cards before a route choice resolves.

Beat 2 — Choose exactly one route

Option index	Stable option ID	Evidence owner after transfer	Immediate relief	Accepted cost
0	public_rescue_accountability	public_medical_record	ward evidence remains replayable	continuity and exposure pressure rise
1	white_glove_garage_containment	white_glove_audit	internal transfer lowers continuity hazard	audience testimony debt rises
2	fan_oxygen_corridor_mutual_aid	fan_mutual_aid	oxygen pressure falls and a public witness route opens	unofficial custody gains a traceable gap

Options 0 and 1 retain their historical indices and flags. Option 2 is the missing fan-oxygen route named by the source description and route-map card.

Every branch must set:

• the common storyteller_ward_transfer_route_selected flag;
• exactly one ward_transfer.route.* flag;
• exactly one ward_transfer.evidence_owner.* flag;
• at least three route-specific counter movements;
• complete_storyteller-rite-ward-12-three-route-transfer;
• the physical card-storyteller-ward-route-map in hand.

Beat 3 — Preserve the route map

裂缝病区绕行路线图 is gained only after the transfer. It records the selected route, evidence owner, assigned funder/permit side, assigned auditor, ledger presence, relief, cost, future reader, and route state after.

The map is not a clean receipt. Public rescue is exposed, white-glove custody is indebted, and fan mutual aid is unofficial. A later reader must see the selected route and its cost rather than treating all three as generic completion.

Beat 4 — Enter the unauthorized memorial

storyteller-event-25-unauthorized-memorial now requires:

• completed Ward 12 transfer;
• storyteller_ward_transfer_route_selected;
• the in-hand route map;
• its existing double-archive and live-consent gates.

Both memorial choices still open Ai Sheng’s named child-voice trace without deciding her final disposition. Suppressing or circulating the memorial adds storyteller_memorial_inherits_ward_transfer_route; it must not clear or replace the selected route/owner flags.

Six reachable combinations

The observable matrix is three transfer routes crossed with two memorial postures:

1. public rescue → suppress memorial;
2. public rescue → circulate memorial;
3. white-glove garage → suppress memorial;
4. white-glove garage → circulate memorial;
5. fan oxygen corridor → suppress memorial;
6. fan oxygen corridor → circulate memorial.

All six retain the route-specific pressure established before Ai Sheng appears. Event 25 remains a child-voice encounter and timing handoff; it does not use the route map to grant voice, archive, memorial, consent, or medical authority.

The new fan-corridor branch also has a fresh durable Game CLI replay at lens/replays/breach-ward-three-route-transfer.fan-oxygen-corridor.replay.json; the complete six-combination matrix is exercised by lens/storyteller-breach-ward-three-route-transfer.runtime.test.ts.

Observable surface

Breach-Ward Three-Route Transfer Lens checks three-route reachability, one-route/one-owner exclusivity, historical option compatibility, route-specific counter pressure, physical route-map handoff, and both unauthorized-memorial postures for every route.