Counterparty Reliance Unwind / 相对方信赖撤回线

Counterparty Reliance Unwind is a pressure storyline for the first route after a false-clean authority has induced somebody to act.

A readback can be narrowed. A callback can be reattached. A sponsor citation can be scoped. A recovery shelf can name a holder. But if a counterparty already paid, scheduled, aired, released a copy, moved a witness, accepted custody, waived a claim, promised a route, exposed a worker, or published a receipt, the game now owes a second question: what happens to the reliance action?

This storyline turns that second question into playable management work.

The first runtime producer is concrete. After 座位图批注后用回执线 records its false default, the sponsor recap desk schedules a group-consent recap against the false-clean audience-jury seat map. Recap slot time is already sunk, and the protected caption-access patron reader is displaced. 相对方信赖被发现 opens the unwind rather than allowing the schedule itself to prove consent.

Why this is the next useful expansion

The current mesh already has strong state consumers:

• 播出合约回读线 prevents a prior contract row from becoming universal permission.
• 回叫消费证明线 prevents callback-bearing relief from becoming clean closure.
• 裁定读者冲突线 handles incompatible future readers of the same source.
• 复原追偿搁架线 names who holds future recourse.

The uncovered seam is action already taken in reliance on the false-clean presentation. Without this storyline, the correction lands too cleanly: the old source is narrowed, but the sponsor package, archive copy, public receipt, worker exposure, claimant waiver, or route asset promise that happened in the meantime can vanish into generic pressure.

Primary playable question

When a counterparty has already relied on a false-clean or overbroad source authority, does the producer honor the reliance narrowly, reimburse and unwind it, convert it into scoped license, escrow it, claw it back with notice, publish the debt, quarantine it, or let false reliance harden into route law?

First implemented producer — the false-clean group recap

The implemented chain is:

1. storyteller.event.false_seat_map_annotation_default.v1 records that a physical seat-map annotation was falsely filed as group broadcast consent and arms counterparty_reliance.entry_pending.
2. storyteller.event.counterparty_reliance_discovered.v1 proves the false-clean source, sponsor recap counterparty, already-scheduled recap action, sunk recap slot, protected caption-access patron, Jao Min proof bridge, and Chapter Two reader are all still present.
3. The entry grants storyteller.card.counterparty_reliance_ledger.v1, four common reliance rows, and exactly one matching posture card.
4. storyteller.rite.reliance_unwind_conference.v1 requires twelve exact in-hand assignments and resolves one of the same eight branch families defined below.
5. The constructive reimbursement branch or durable storyteller.event.false_reliance_default.v1 is replayed from turn one, and 召回认领优先级线 can consume the resulting reliance ledger as a callable source.

This is the first producer, not a narrowing of the general mechanic. Later false-clean sources may open the same ledger only if they supply an already-taken action, sunk surface, displaced reader, proof bridge, explicit cost, and downstream reader.

State-triggered entry

Open this storyline only from state pressure:

entry_state:
  trigger_kind: state_pressure
  source_authority_row_present: true
  source_authority_kind: seat_map_annotation_afteruse | broadcast_readback | callback_consumption | sponsor_afteruse | recovery_indemnity | broadcast_signatory | asset_provenance | settlement_aftershock | equivalent
  clean_or_overbroad_claim_present: true
  relying_counterparty_present: true
  reliance_action_already_taken: true
  sunk_surface_visible: true
  harmed_or_displaced_reader_present_or_explicit_absence: true
  future_reader_or_route_effect_possible: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Valid reliance actions include:

• sponsor paid or scheduled a package;
• archive released or accepted a custody copy;
• lawful reader accepted a bridge;
• public delegate published receipt;
• fan table moved oxygen credit;
• claimant row waived or claimed a right;
• worker carrier exposed testimony or signed custody;
• route-asset custodian moved, copied, or promised an asset;
• editor aired a checksum version;
• management filed a clean closure.

Content pack

Mechanic

• 相对方信赖撤回机制 defines the reliance row, state machine, branch contract, default, counter surfaces, and replay evidence.

Card

• 相对方信赖账本 records source authority, clean claim, relying counterparty, reliance action, sunk surface, displaced reader, selected unwind, cost, and future effect.

Rite

• 信赖撤回会 is the assignable management action that resolves the row through honor, reimbursement, scoped license, escrow, clawback, publication, quarantine, or default.

Event

• 相对方信赖被发现 is the source-backed runtime entry from the Seat Map Annotation false default.
• 虚洁净信赖默认 fires or arms when the reliance action is hidden or treated as proof that the old authority was clean.

Storyline spine

Beat 1 — The source was corrected too late

A downstream route discovers that a prior authority was overbroad, callback-bound, reader-scoped, quarantined, or false-clean.

The source row is not erased. The correction remains true.

Beat 2 — Somebody already acted

The game creates or updates 相对方信赖账本.

The ledger must prove:

• the source authority row exists or is explicitly absent;
• the clean or overbroad claim that induced reliance is visible;
• the relying counterparty is named;
• the reliance action already happened;
• the sunk surface is concrete;
• the harmed or displaced reader is named or explicitly absent;
• a future route or reader can consume the outcome.

Beat 3 — The producer chooses an unwind

The player opens 信赖撤回会.

The rite requires handler, proof bridge, support, cost, and future effect. Absence is allowed only when explicit and costly.

Beat 4 — Reliance becomes route state

The chosen branch does not clean the old source. It creates a reliance state:

• honored but limited;
• reimbursed and unwound;
• converted to scoped license;
• escrowed;
• clawed back with notice;
• debt published;
• quarantined;
• false reliance hardened;
• hostile;
• recovery-only.

Beat 5 — A future reader consumes the scar

The storyline is incomplete until a later route, reader, proof package, sponsor release, public receipt, archive copy, route asset, claimant gate, worker testimony, or broadcast-reality check reads the reliance state.

Valid effects:

• route accepted only with reliance cost;
• public-only, lawful-only, sponsor-only, or split-required path;
• proof rehearing or annex required;
• worker or claimant becomes protected, hostile, or recovery-only;
• route asset becomes escrowed, returned, false-owned, blocked, or recovery-only;
• broadcast reality hardens the relied version.

Branch map

Branch	Relief	Cost	Future effect
Honor limited reliance	good-faith counterparty remains usable	reader scope narrows; public, sponsor, archive, or route pressure rises	accepted with reliance cost, public-only, lawful-only, sponsor-only
Reimburse and unwind	false-clean claim drops; custody or proof recovers	money, license encumbrance, route delay, handler burden	accepted with cost, costlier, contradiction pending
Convert to scoped license	current route partly opens	source ambiguity, correction pressure, reader split	public-only, lawful-only, sponsor-only, split-required
Escrow reliance	unsafe citation blocked and source trace preserved	route delay, archive debt, inspection heat	blocked, lawful-only, recovery-only
Clawback with notice	overbroad benefit removed visibly	counterparty hostility, sponsor pressure, public distrust	hostile, contradiction pending, recovery-only
Publish reliance debt	hidden reliance becomes public/lawful/archive memory	public confusion, sponsor pressure, inspection heat	accepted with cost, split-required, contradiction pending
Quarantine reliance	fraud, worker exposure, or false owner risk decreases	current route blocked, recovery cost, counterparty hostility	blocked, recovery-only
False reliance default	immediate pressure may drop	false reliance hardens; displaced reader becomes hostile	false-reliance-hardened, hostile, blocked, recovery-only

No branch may produce clean universal authority across public, lawful, sponsor, archive, worker, claimant, route asset, management, and broadcast-reality readers.

Integration notes

• With 座位图批注后用回执线, the false-default seat-map state is the first runtime producer: sponsor recap scheduling sinks slot time while displacing the protected caption-access patron reader.
• With 召回认领优先级线, storyteller.card.counterparty_reliance_ledger.v1 becomes a callable source after the unwind result, so sponsor and protected-patron claims cannot silently share one constrained recap surface.
• With 播出合约回读线, this storyline starts after readback proves the old row was scoped but a counterparty already relied on the broad version.
• With 回叫消费证明线, it starts after a relief callback resurfaces but another reader already consumed the relief as clean proof.
• With 复原追偿搁架线, it decides what happens to reliance on a supposedly safe holder assignment.
• With 裁定读者冲突线, it handles sunk action after incompatible readers are discovered.
• With 误服裁定认领升级线, it lets the false-served claimant consume reliance by sponsor, management, archive, or public desks.
• With 和解反震账本, it distinguishes aftershock debt from reliance action already taken because of a clean settlement presentation.
• With Route Assets and Custody, the relying action may move, false-own, escrow, return, or poison a route asset.
• With Broadcast Reality, an aired reliance can harden into the version the audience remembers unless the debt is published or quarantined.

Missability and recovery

This storyline is missed when the implementation corrects a false-clean source row without recording who relied on it, what action they took, what surface was sunk, and who was displaced.

Missed states:

• counterparty_reliance_unopened;
• reliance_action_unrecorded;
• sunk_surface_absent;
• displaced_reader_absent;
• false_reliance_hardened;
• counterparty_false_owner;
• worker_silent_carrier;
• claimant_burdened_body;
• route_asset_false_owner;
• recovery_only_reliance.

Recovery requires visible scar:

• late reliance ledger;
• reimbursement with named sunk surface;
• limited reliance license;
• lawful annex or proof rehearing;
• public reliance debt bulletin;
• sponsor unwind;
• route asset return;
• worker protection receipt;
• claimant counterclaim receipt;
• archive quarantine;
• recovery-only route that preserves the false reliance scar.

Replay/session evidence shape

Anticipated durable runtime evidence:

• lens/replays/counterparty-reliance-unwind.reimburse.replay.json;
• lens/replays/counterparty-reliance-unwind.false-default.replay.json.

storyline: storyteller.storyline.counterparty_reliance_unwind.v1
session_id: lens-counterparty-reliance-unwind-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_authority_row_present: true
  clean_or_overbroad_claim_present: true
  relying_counterparty_present: true
  reliance_action_already_taken: true
  sunk_surface_visible: true
  harmed_or_displaced_reader_present_or_explicit_absence: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
offered:
  card: storyteller.card.counterparty_reliance_ledger.v1
  rite: storyteller.rite.reliance_unwind_conference.v1
branch_runs:
  constructive_branch:
    selected_unwind: honor_limited_reliance | reimburse_and_unwind | convert_to_scoped_license | escrow_reliance | clawback_with_notice | publish_reliance_debt | quarantine_reliance
    ledger_state_after: <state>
    relying_counterparty_state_after: <state>
    displaced_reader_state_after: <state>
    future_reader_effect: <effect>
    counter_deltas: {}
  default_branch:
    selected_unwind: false_reliance_default
    event_seen_or_armed: storyteller.event.false_reliance_default.v1
    false_reliance_claim: <claim>
    default_actor: <actor>
    future_reader_effect: <effect>
    counter_deltas: {}
downstream_read:
  reader: public | lawful_reader | sponsor | archive | claimant | worker | route_asset | management | broadcast_reality | equivalent
  consumed_state: <ledger_state_after>
  route_effect_after_read: <effect>
assertions:
  - entry_is_state_triggered
  - source_authority_preserved
  - reliance_action_already_taken_visible
  - sunk_surface_visible
  - displaced_reader_visible_or_explicit_absence
  - branches_diverge
  - every_success_has_cost
  - false_reliance_default_names_actor_and_claim
  - downstream_reader_consumes_reliance_state
  - no_universal_clean_authority
  - no_fixed_turn_trigger
  - no_fixed_day_or_week_trigger

Non-goals

• Not a new verdict.
• Not a generic settlement or liability desk.
• Not a fixed-turn aftermath.
• Not raw count expansion.
• Not a replacement for readback, callback, reader collision, claimant intake, or indemnity shelf.
• Not valid if nobody has already acted in reliance.
• Not valid unless future route acceptance changes.