Pei Huan Sponsor-Inheritance Counsel / 裴环冠名遗产漏口律师线

This storyline repairs two linked source promises:

1. Rite 14 offered a Yu Lan-readable leak, but Rite 15 accepted only the sponsor-return flag, so the leak branch had no continuation.
2. card-storyteller-pei-huan promised a Rite 14 encounter, recruitment, and miss state, but no runtime object produced any of them.

The focused question is:

When the sponsor-inheritance report is closed, does Pei Huan remain as a bounded counsel who can explain its leak, or is she visibly retained elsewhere before the white-glove audit reads the result?

Beat 1 — Materialize the encounter

Rite 14 keeps its existing conditions, ID, two slot IDs, and historical option indices. A successful resolution now gains:

• actual card-storyteller-pei-huan;
• storyteller.card.pei_huan_sponsor_inheritance_review.v1;
• storyteller_peihuan_first_encounter;
• the common storyteller_sponsor_inheritance_path_selected handoff.

No selected option or out-of-hand assignment may resolve the encounter.

Beat 2A — Company return and visible miss

Historical option index 0 still sets storyteller_ledger_returned_to_sponsors. It also selects sponsor_inheritance.route.company_return, arms the retainer notice, and marks Pei Huan pending.

The priority event then:

• removes the actual character card;
• gains storyteller.card.pei_huan_company_retainer_notice.v1;
• sets storyteller_peihuan_contract_signed_elsewhere;
• writes pei_huan.state.missed_company_retainer;
• adds recovery cost without creating the route asset.

The notice is not a hidden recruitment path. It preserves only an explicit future recovery obligation.

Beat 2B — Yu Lan-readable leak and recruitment

Historical option index 1 still sets storyteller_yulan_keeps_ledger_leak. It additionally:

• selects sponsor_inheritance.route.yulan_readable_leak;
• retains actual Pei Huan;
• sets pei_huan.state.recruited_scoped_leak_counsel;
• creates route_asset.pei_huan_sponsor_inheritance_counsel;
• moves contract trust, sponsor debt, legal-body hazard, and public accountability.

The asset can read this one sponsor-inheritance handoff. It cannot decide ownership, consent, truth, or universal contract validity.

Beat 3 — Both branches enter Rite 15

Rite 15 now requires the common selected-path flag, a resolved Pei Huan disposition, and the physical review record. The old branch-exclusive requirement on storyteller_ledger_returned_to_sponsors is removed.

The two upstream paths therefore converge without becoming identical:

Upstream state	Rite 15 eligible	Pei Huan retained	Miss notice retained
company return + retainer notice	yes	no	yes
Yu Lan-readable leak + recruitment	yes	yes	no

Both Rite 15 choices set storyteller_white_glove_audit_inherits_sponsor_inheritance_path and preserve the upstream route and terminal character state.

Four reachable combinations

The runtime oracle crosses two Rite 14 dispositions with both Rite 15 audit postures:

1. company return → scoped audit format;
2. company return → show Yu Lan the audit seal;
3. readable leak → scoped audit format;
4. readable leak → show Yu Lan the audit seal.

The recruit and miss extremes also have focused Game CLI replay evidence.

Non-goals

• No transfer of memory, breath, mourning, archive, or platform ownership.
• No universal legal-body or contract authority.
• No automatic recruitment after the company-retainer notice.
• No turn-number, dashboard, or lens-health trigger.
• No rewriting of Rite 14’s existing option meanings or indices.