Recall Claim Priority / 召回认领优先级线

Recall Claim Priority is a pressure storyline for the moment after a stabilizing success, liability handoff, call default, or reliance unwind has become callable by more than one claimant.

The current mesh already makes the source scar visible. 稳定化责任交接线 names carrier, maturity trigger, claimant, scar, and future effect. 相对方信赖撤回线 names the sunk reliance action. 稳定化债务召回 and 责任追缴违约 make the cost callable.

The remaining gap is queue pressure: a single callable surface can be demanded by sponsor, inspector, fan public, archive desk, editor, witness, artist, route claimant, worker carrier, or broadcast reality at the same time. If the implementation resolves the first claimant and lets every other claimant vanish into generic difficulty, the management game loses its teeth.

Primary playable question

When several claimants call the same stabilization ticket, reliance scar, collateral, public bond, proof object, route asset, handler lane, or production surface, who is satisfied first — and what visible scar is attached to everyone else?

State-triggered entry

Open only from state pressure:

entry_state:
  trigger_kind: state_pressure
  callable_source_present_any:
    - storyteller.card.stabilization_liability_ticket.v1
    - storyteller.event.stabilization_debt_recall.v1
    - storyteller.event.liability_call_default.v1
    - storyteller.card.counterparty_reliance_ledger.v1
  call_rows_min: 2
  rows_share_same_carrier_collateral_or_surface: true
  rows_have_non_equivalent_demands: true
  first_satisfaction_can_change_later_satisfaction: true
  proof_anchor_or_explicit_absence_available: true
  handler_or_explicit_absence_available: true
  future_route_or_reader_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 entry examples:

• sponsor calls a stop-loss escrow while fans call the same pool as oxygen refund;
• inspector remands an archive seal while editor checksum wants the same source copy;
• a public bond is demanded as correction proof while a lawful reader calls it as admissibility anchor;
• a worker carrier needs protection before a claimant can use their testimony as proof;
• a route asset posted as collateral is also needed for rescue, public receipt, or sponsor package;
• a reliance unwind names both the relying counterparty and the displaced reader as callable claimants.

Content pack

Mechanism

• 召回认领优先级机制 defines claim queue rows, shared-surface constraints, priority states, branch families, default, and replay evidence.

Existing card and event surfaces

This storyline intentionally composes existing durable surfaces instead of adding count filler:

• 稳定化责任票据 provides the callable carrier, claimant, maturity trigger, scar, and future route effect.
• 稳定化债务召回 provides the recall cause and claimant call.
• 责任承保账本 provides guarantor, collateral, and call trigger.
• 责任追缴违约 provides failed collateral and caller state.
• 相对方信赖账本 provides sunk reliance action, displaced reader, and selected unwind.
• 认领告知案卷 can pre-shape which claimant enters first.
• 认领撞锁案卷 can consume a route asset when the queue targets custody.
• 失败态裁定案卷 can receive unresolved double-called queues as future failure rows.

Rites consumed or extended

The storyline may be implemented through a dedicated claim-priority rite or through equivalent assignment extensions on:

• 稳定化责任交接 when queue rows are created during handoff;
• 责任承保听证 when guarantor/collateral priority is being set;
• 认领告知电话 when notice order creates first-call advantage;
• 认领撞锁听证 when the same queue consumes or splits a route asset;
• 失败优先听证 when unresolved queue states become official failure rows.

Storyline spine

Beat 1 — One callable surface receives two calls

A prior branch matured a ticket, recalled a debt, defaulted a guarantee, or exposed sunk reliance. The game creates a queue view over the same carrier, collateral, proof, lane, route asset, public bond, fan refund pool, archive copy, edit checksum, or explicit absence.

Beat 2 — Each claimant names a different demanded surface

The queue cannot be generic. Each row names claimant, claim kind, demanded surface, relief if satisfied first, cost if satisfied first, consequence if deferred, hardening if ignored, proof anchor or absence, and handler or absence.

Beat 3 — The player chooses priority or restructure

The player can answer one claimant first, consolidate compatible calls, split tender, post substitute collateral, stay a call with notice, subordinate a claimant with concession, or refuse and risk double-call default.

Beat 4 — Deferred claimants become scars

Rows that are not satisfied first must mutate into stayed, subordinated, hostile, captured, public-only, lawful-only, sponsor-only, contradiction-pending, blocked, or recovery-only states. Deferred claimants do not disappear.

Beat 5 — The future route consumes the queue result

At least one later route, reader, rite, assignment, public receipt, archive copy, sponsor package, route asset, handler lane, worker/witness state, or broadcast reality state reads the selected priority and the deferred scars.

Branch matrix

Branch	Immediate relief	Required cost/scar	Future effect
Sponsor first	stop-loss, cash, slot, or package pressure improves	contract capture, fan/public distrust, lawful suspicion, correction cost	sponsor-only, public audit required, recourse target, recovery-only
Inspector/archive first	lawful use, admissibility, custody clarity, or fraud containment improves	inspection heat, bureau debt, public delay, route quarantine	lawful-only, appeal required, sponsor retaliation, recovery-only
Public/fan first	private capture blocked; oxygen/public receipt legitimacy improves	sponsor pressure, witness exposure, audit heat, public panic	public-only, refund queue, private clean route blocked
Editor/checksum first	slot legibility, continuity, or source coherence improves	edit debt, source ambiguity, archive suspicion, public distrust	contradiction pending, checksum release required, public version costlier
Artist/witness/worker first	consent, witness safety, refusal, or worker trust improves	schedule pressure, sponsor delay, handler burden, lawful cost	unlocked with protection, delayed, hostile claimant possible
Consolidate or split tender	two calls avoid immediate hostility	drift, ambiguity, proof-maintenance burden, correction cost	split required, public/lawful fork, later conversion required
Substitute collateral	original surface survives one call	substitute asset, proof, lane, or public bond becomes exposed	route asset pressure, recovery-only substitute, new claimant queue
Refuse or double-call default	short-term burden may drop	same surface promised twice or hidden claimant hardens	default, hostile, captured, blocked, false priority, recovery-only

No branch may create clean universal closure across sponsor, inspector, archive, editor, fan public, witness, artist, route asset, management, and broadcast reality readers.

Character and faction use

• Orion Breath or sponsor counsel can answer sponsor first, but contract capture and public/fan debt rise.
• Han Yanshuang or Inspector Rhee can answer lawful remand first, but inspection heat and lawful-only pressure rise.
• Yu Lan, fan delegates, or pirate relay can answer public/fan first, but witness exposure and sponsor retaliation rise.
• Baiya, Han Cutroom, or black-box source holders can answer checksum first, but source ambiguity and archive suspicion rise.
• Shen Luo can consolidate or subordinate claimants through language, but manager debt and future capture rise.
• Artists, witnesses, workers, proxies, and route-asset carriers can be protected first only with lane, schedule, handler, or public cost.

Missability and recovery

This storyline is missed when implementation:

• handles only the first claimant after a recall;
• turns a queue into generic pressure;
• lets sponsor, inspector, fan, archive, editor, witness, artist, and route asset calls collapse into the same penalty;
• fails to record the shared constrained surface;
• omits deferred claimant scars;
• consolidates calls without proof anchor or named omitted harm;
• substitutes collateral without naming what was exposed;
• resolves queue priority as clean closure.

Recovery is allowed only through visible scar:

• sponsor buyback with contract capture;
• public refund with witness exposure;
• lawful appeal with bureau favor debt;
• checksum release with edit debt;
• route asset rescue with custody pressure;
• worker/witness protection with handler burden;
• split public/lawful record with drift;
• recovery-only route after double-call default.

Replay/session evidence shape

storyline_id: storyteller.storyline.recall_claim_priority.v1
session_id: lens-recall-claim-priority-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  callable_source_present: true
  source_surface: stabilization_liability_ticket | stabilization_debt_recall | liability_call_default | counterparty_reliance_ledger | equivalent
  call_rows_min: 2
  rows_share_same_carrier_collateral_or_surface: true
  no_fixed_turn_trigger: true
source:
  source_id: <ticket, recall, call-default, or reliance row>
  carrier_or_collateral: <shared surface>
  scar_before: <scar>
claim_rows:
  - claimant: sponsor
    claim_kind: <kind>
    demanded_surface: <surface>
    consequence_if_deferred: <scar>
  - claimant: fan_public | inspector | archive | editor | witness | route_claimant | equivalent
    claim_kind: <kind>
    demanded_surface: <surface>
    consequence_if_deferred: <scar>
branch_result:
  selected_priority: sponsor_first | inspector_archive_first | public_fan_first | editor_checksum_first | artist_witness_worker_first | consolidate | split_tender | substitute_collateral | refuse_or_double_call
  first_satisfied_claimant: <claimant>
  queue_state_after: <state>
  deferred_claimant_states:
    - claimant: <claimant>
      state_after: stayed | subordinated | hostile | captured | public_only | lawful_only | sponsor_only | contradiction_pending | blocked | recovery_only
  downstream_surface_mutated: <surface>
  future_route_effect: <effect>
  counter_deltas:
    relief: []
    cost: []
assertions:
  - entry_is_state_pressure
  - at_least_two_call_rows_visible
  - shared_surface_visible
  - rows_have_non_equivalent_demands
  - first_satisfaction_changes_later_satisfaction
  - deferred_claimants_persist_as_scars
  - success_has_cost
  - downstream_surface_mutates
  - no_clean_universal_closure
  - no_fixed_turn_day_week_raw_count_dashboard_or_lens_health_trigger

Non-goals

• Not a fixed timing aftermath.
• Not a raw count expansion.
• Not a generic legal or finance queue.
• Not an ending-only fork.
• Not a replacement for stabilization handoff, counterparty reliance, claimant briefing, claimant collision, failure arbitration, underwriting, or route custody.
• Not valid if only one claimant is present.
• Not valid unless priority changes deferred claimant state and a future route or reader consumes the result.