Guarantee Recourse Cascade / 担保追偿级联

Guarantee Recourse Cascade is the pressure storyline for the moment after a guarantee has already done its job or failed loudly. The player survived the first liability call, but the payer now owns a recovery right that can reshape faction posture, route assets, public receipts, facility access, and production lanes.

This storyline is the next layer after 派系责任承保. Underwriting makes future harm callable. Recourse makes the call’s aftermath collectible.

Primary playable question

After a sponsor, inspector, public, editor, archive, producer, or split guarantor pays, calls, rejects, or converts a guarantee, who gets to recover from the show — and which route, asset, room, receipt, or claimant becomes scarred by that recovery?

Every branch must show:

• who paid or gained recovery rights;
• who is treated as debtor;
• what target can be collected;
• whose claim is barred or subordinated;
• what immediate pressure improves;
• what future route, asset, room, public receipt, or faction posture becomes worse.

Why this is the next useful expansion

The current green surface is strong at first-order pressure and immediate aftermath: drift audit, faction commitment, public contrition, witness reprisal, settlement aftershock, production triage, facility lockdown, and liability underwriting.

The uncovered gap is post-guarantee recourse. A guarantee can now be called or paid, but the corpus has not yet forced the payer’s recovery right to become a branchy, replay-visible surface. Without this, sponsor/inspector/public/editor guarantees can still feel like one-scene mitigation instead of future route ownership.

This storyline binds:

• 担保追偿优先级机制;
• 担保追偿案卷;
• 追偿优先级听证;
• 追偿扫场违约.

State-triggered entry

Open this storyline when all of the following are true:

1. a previous or current branch created an underwritten exposure, collateral call, public rejection, surety call, sponsor sweep, edit reserve exhaustion, production self-insurance overdraw, split cover, or route-asset collateral scar;
2. a payer, caller, guarantor, or public beneficiary can plausibly recover from a debtor;
3. at least one concrete recourse target exists or is explicitly absent: sponsor escrow, legal seal, public receipt, fan oxygen pool, edit capacity, proof object, route asset, facility room, schedule lane, handler time, or faction favor;
4. at least two claimants would rank the recovery differently;
5. the target can still affect route availability, asset custody, public legitimacy, facility access, production triage, faction posture, or broadcast reality;
6. the exposure has not reached terminal discharge, final ending lock, or irreversible clean disappearance.

This entry is driven by live liability and recovery state. It has no fixed numbered trigger.

Storyline spine

Beat 1 — Recovery right is noticed

A paid or called guarantee produces or updates 担保追偿案卷.

The row must name payer, debtor, target, priority claim, enforcement surface, barred claimant, handler, and future route effect.

Beat 2 — Claimants rank the same target differently

At least two surfaces want the recovery ordered differently.

Examples:

• sponsor wants first claim on a public correction route, while fan public demands restitution first;
• inspector claims legal-seal priority, while editor needs checksum custody before proof is admissible;
• production wants to substitute a schedule lane to protect a route asset, while the sponsor wants the asset seized;
• public receipt can block private collection, but doing so exposes a witness chain;
• a facility room can be locked for collection, but that lock prevents another rescue.

Beat 3 — Priority hearing assigns target or substitute

The player opens 追偿优先级听证 and selects priority proof, handler, recovery target, barred claimant, and optional substitute collateral.

No branch can succeed by paying abstract money only. A visible target must be satisfied, subordinated, traded, barred, converted to public restitution, or swept by default.

Beat 4 — Relief creates ownership pressure

The chosen branch may lower payer hostility, clarify custody, restore public legitimacy, preserve a route asset, or prevent a sweep. It must also raise a future cost: contract capture, inspection heat, public audit, witness exposure, edit debt, handler fatigue, facility access pressure, route asset pressure, claimant hostility, or black-screen risk.

Beat 5 — Sweep, recovery, or scar persists

If priority is missing, unhandled, hidden, or impossible, 追偿扫场违约 fires or is recorded.

If the priority hearing succeeds, the scar still persists: target spent, substitute scarred, claimant barred, public restitution exposed, asset recovery-only, room locked, or route costlier.

Branch model

Branch A — Honor payer priority

The player lets sponsor, inspector, editor, archive, or another payer collect first.

Expected outcomes:

recourse_state_after: satisfied | swept
relief: payer_hostility_down | immediate_default_down | sponsor_stop_loss_pressure_down | custody_clarity_up
cost: barred_claimant_hostility_up | route_asset_pressure_up | public_receipt_distrust_up | contract_capture_up
future_route_effect: target_route_costlier | barred_claim_recovery_only

Branch B — Public/fan restitution priority

The player subordinates private recovery behind public receipt, fan oxygen, Yu Lan, witness oath, or pirate relay proof.

Expected outcomes:

recourse_state_after: subordinate | converted_to_public_restitution
relief: public_receipt_legitimacy_up | fan_oxygen_balance_up | audience_stability_up
cost: sponsor_pressure_up | inspection_heat_up | witness_exposure_up | oxygen_liability_up
future_route_effect: public_audit_unlocked_with_risk

Branch C — Substitute collateral to protect target

The player trades in schedule lane, edit reserve, handler time, legal seal, sponsor escrow, fan pool, facility favor, or a less critical route asset.

Expected outcomes:

recourse_state_after: assigned | traded
relief: original_target_protected | route_control_up | claimant_collision_down
cost: substitute_target_scarred | lane_scar_up | edit_debt_up | handler_fatigue_up | future_correction_cost_up
future_route_effect: substitute_route_costlier

Branch D — Contest false or excessive priority

The player challenges the payer’s recovery order with archive proof, checksum, public receipt, witness oath, facility access log, or rival claimant row.

Expected outcomes:

recourse_state_after: priority_contested | barred
relief: false_priority_blocked | private_capture_down | route_asset_pressure_down
cost: litigation_heat_up | coalition_pressure_up | schedule_pressure_up | source_ambiguity_up
future_route_effect: appeal_or_counterclaim_required

Branch E — Facility or route-asset sweep

The payer uses access control to collect from a room, route asset, proof object, service corridor, archive counter, stage threshold, or handler.

Expected outcomes:

recourse_state_after: swept
asset_state_after: seized | captured | poisoned | posted_as_collateral | recovery_only
room_state_after: claimed | sealed | watched | locked_recovery_only | none
cost: route_asset_pressure_up | facility_access_pressure_up | runner_risk_up | claimant_hostility_up
future_route_effect: blocked | captured | hostile | costlier | recovery_only

Branch F — Miss, hide, or default

The player lacks docket, target, handler, priority proof, room access, or substitute collateral; hides the row; or treats guarantee payment as finished.

Expected outcomes:

recourse_state_after: defaulted | recovery_only
emitted_event: storyteller.event.recourse_sweep_default.v1
cost: route_asset_pressure_up | facility_access_pressure_up | claimant_hostility_up | black_screen_slots_up
future_route_effect: blocked | captured | hostile | costlier | recovery_only

Core states and counters

Primary states:

• recourse_state
• recourse_priority
• recourse_target_state
• barred_claimant_posture
• public_restitution_state
• substitute_collateral_state
• facility_collection_lock
• route_asset_recovery_state
• future_route_effect

Primary counters:

• payer_hostility
• contract_capture
• sponsor_stop_loss_pressure
• inspection_heat
• bureau_favor_debt
• public_receipt_legitimacy
• public_receipt_distrust
• fan_oxygen_balance
• fan_oxygen_resentment
• oxygen_liability
• witness_exposure
• edit_debt
• source_ambiguity
• future_fraud_cost
• lane_scar
• handler_fatigue
• facility_access_pressure
• route_asset_pressure
• claimant_hostility
• coalition_pressure
• black_screen_slots

Every branch must record at least three deltas, with both relief and future cost visible.

Integration notes

• With 派系责任承保, this storyline begins after a collateral call, cover hold, cover failure, or release with scar.
• With 派系承诺账本, recovery rights consume finite faction commitments and can create coalition pressure.
• With 制作分诊台, substitute collateral can arm unstaffed tickets and lane scars.
• With 设施通行封控线, recourse may require room control, corridor access, or route-asset movement.
• With 公开悔过账本, public wording can subordinate private collection or convert recovery into restitution.
• With 和解反震账本, a settlement that paid relief can still produce recovery rights.
• With Route Assets and Custody, any route asset posted, substituted, or swept becomes scarred, captured, poisoned, or recovery-only.

Missability and recovery

This storyline is missable when the player treats a paid guarantee as final, lets a payer collect quietly, fails to record barred claimant, spends substitute collateral without a scar, allows a facility lock without route consequence, or ignores public restitution pressure.

Recovery is allowed only with a scar:

• public restitution after private sweep;
• lawful appeal after archive surety priority;
• sponsor concession after contract capture;
• checksum release after edit sweep;
• production reprioritization after lane overdraw;
• facility reroute after room lock;
• route-asset rescue after seizure or recovery-only mark.

Replay/session evidence shape

storyline: storyteller.storyline.guarantee_recourse_cascade.v1
session_id: lens-guarantee-recourse-cascade-v1-<timestamp>
seed: <deterministic-seed>
source_guarantee:
  source_session_id: <session that created or called guarantee>
  source_seed: <seed>
  exposure_id: <liability exposure id>
  guarantor: <guarantor>
  collateral_state_after: called | paid | rejected | overdrawn | released_with_scar | split | fraud_flagged
entry_state:
  recourse_row_before:
    recourse_id: <id>
    payer: <payer>
    principal_debtor: <debtor>
    recourse_target: <target>
    priority_claim: <priority>
    barred_claimant: <claimant>
offered:
  card: card.guarantee_recourse_docket
  rite: storyteller.rite.recourse_priority_hearing.v1
branch_runs:
  honor_payer_priority:
    outcome: satisfied_or_swept_with_barred_claimant
  public_restitution_priority:
    outcome: private_recourse_subordinated_with_public_audit
  miss_or_default:
    emitted_event: storyteller.event.recourse_sweep_default.v1
    outcome: recovery_only_or_swept_target
assertions:
  - entry_is_state_driven
  - recourse_row_records_payer_debtor_target_priority_and_barred_claimant
  - branches_have_non_equivalent_relief_and_cost
  - sweep_or_satisfaction_mutates_route_asset_room_receipt_lane_or_faction_posture
  - no_fixed_turn_trigger

Non-goals

• Not a generic accounts-receivable screen.
• Not a fixed collection phase.
• Not raw economy balancing.
• Not a free cleanup after underwriting.
• Not governance content.
• Not satisfied by another liability row; recourse must create new route, asset, public, room, lane, or faction consequences.