Recovery Indemnity Shelf / 复原追偿搁架线
Recovery Indemnity Shelf is a pressure storyline for the moment after recovery inventory, sponsor proof, or archive custody has stabilized a crisis but a future claim is still looking for a holder.
The existing mesh already asks strong questions:
- 复原库存分诊线 asks which finite recovery row is spent and who is excluded.
- 赞助后用引证线 asks whether a sponsor object can be cited outside its original scar.
- Route Assets and Custody asks who controls a proof, receipt, worker, voice, archive copy, or route asset.
This storyline adds the next consequence: when that stabilized route is later recalled, sued, protested, audited, or contradicted, who carries recourse?
If that holder is hidden, Storyteller silently lets sponsor, management, archive, ward, or handler absence move liability onto low-rank workers, claimants, public trust, or the producer license. This line makes that offload playable.
Primary playable question
When a recovery shelf opens, does the producer:
- force the sponsor to retain recourse;
- underwrite the claim on the producer license;
- place the source in archive escrow;
- ask public/fan trust to hold a visible shelf;
- protect a worker or claimant from becoming a silent liability holder;
- split recourse between readers;
- quarantine the source;
- or let a default actor shelf the liability first?
Every answer must name protected reader, burdened or excluded reader, holder state after, shelf state after, and future recall reader.
Content pack
Mechanic
- 复原追偿搁架机制 defines source scars, indemnity holders, reader divergence, worker/claimant liability states, counter surfaces, default capture, and replay evidence.
Card
- 复原追偿搁架 records the shelf row, source object, source scar, proposed holder, protected reader, burdened reader, recall trigger, holder state, shelf state, and future route effect.
Rite
- 复原追偿指派 assigns sponsor retention, producer underwriting, archive escrow, public/fan trust, worker protected refusal, split recourse, quarantine, or default.
Event
- 复原追偿默认 fires or arms when recourse is hidden, falsely cleaned, or offloaded to a worker/claimant/archive copy without a visible protected reader and burdened reader.
State-triggered entry
Open the storyline from state pressure only.
entry_state:
trigger_kind: state_pressure
source_object_present: true
source_object_kind: recovery_inventory_row | sponsor_afteruse_citation | archive_custody_proof | claimant_floor_receipt | management_clean_report | equivalent
source_scar_present_or_explicit_absence: true
proposed_or_missing_indemnity_holder_visible: true
protected_reader_present: true
burdened_or_excluded_reader_present_or_explicit_absence: true
future_recall_reader_present: true
worker_or_claimant_liability_possible_or_explicit_absence: true
player_can_assign_split_escrow_refuse_quarantine_or_default: true
no_fixed_turn_trigger: true
no_fixed_day_or_week_trigger: true
no_raw_count_trigger: true
no_dashboard_or_lens_health_trigger: trueThe storyline must not open from fixed turn count, fixed day/week interval, chapter quota, raw content count, dashboard state, lens health, generic sponsor pressure, or generic legal review.
Storyline spine
Beat 1 — A stabilized route leaves a claim behind
A prior recovery allocation, sponsor afteruse citation, archive custody proof, claimant floor receipt, or management clean report has made one route proceed. The source is not blank: it carries a shortfall, omission, injury, false-clean claim, default capture, recovery-only scar, sponsor-only limitation, public-only limitation, lawful-only limitation, or explicit absence.
Beat 2 — A future reader asks who will pay or answer
A later reader can recall the shelf:
- sponsor reader wants stop-loss and release reuse;
- lawful/archive reader wants admissible chain;
- public/fan reader wants receipt, refund, oxygen legitimacy, or counterclaim;
- artist-boundary reader wants body, voice, recovery, or consent protection;
- worker route reader wants testimony safety, wage protection, or carrier survival;
- claimant reader wants the body or receipt not to be settlement inventory;
- management reader wants a closed KPI.
At least two readers must become visible, and they cannot all accept the same clean answer.
Beat 3 — Holder proposal becomes dangerous
The proposed holder may be sponsor, producer license, archive escrow, ward queue, public/fan trust, worker carrier, claimant body, inspector escrow, or explicit absence.
This beat must show holder state before assignment. A worker or claimant holder must name whether they are protected, exposed, captured, hostile, coerced, absent, or scoped.
Beat 4 — Assignment rite chooses the shelf
Run 复原追偿指派. The player chooses sponsor retention, producer underwriting, archive escrow, public/fan trust, worker protected refusal, split recourse, quarantine, or lets default select.
A useful branch may relieve one surface, but it must increase cost elsewhere and create future recall state.
Beat 5 — Future route consumes the shelf
A later route, event, or reader consumes the result:
- sponsor calls the shelf back as sponsor-only proof;
- archive requires checksum or lawful-only review;
- public/fan route demands refund audit or exposes false settlement;
- worker becomes protected witness, hostile witness, or route asset;
- claimant body becomes protected, hostile, or recovery-only;
- management cannot count the shelf as clean closure;
- route becomes costlier, blocked, contradiction-pending, or accepted with cost.
Branch map
| Branch | Immediate relief | Cost/scar | Future state |
|---|---|---|---|
| Sponsor retains recourse | worker/claimant burden blocked | sponsor pressure, contract capture, schedule pressure | sponsor recall or sponsor-only route |
| Producer underwrites | route has named backer | license encumbrance, inspection heat, management pressure | route costlier, accepted with cost |
| Archive escrow | lawful source trace preserved | archive debt, public delay, checksum pressure | lawful-only or checksum-required |
| Public/fan trust | public memory or refund path visible | sponsor pressure, fan resentment, inspection heat | public-only or refund audit |
| Worker protected refusal | worker not silent liability sink | handler burden, payroll leak, inspection exposure | worker testimony or route-asset witness |
| Split recourse | immediate route partly unblocks | source ambiguity, archive debt, hostile reader | split-required or contradiction-pending |
| Quarantine source | unsafe transfer blocked | current route blocks, sponsor/public pressure rises | blocked, recovery-only, or lawful-after-review |
| Default shelving | immediate metric or slot may close | burden hidden and false-clean hardened | worker hostile, claimant hostile, sponsor-only, lawful-only, public-only, blocked, recovery-only |
Character and route hooks
- 交接链跑腿 can become a protected indemnity witness, coerced signer, hostile payroll witness, or route asset when a courier receipt is turned into liability.
- 首接保全员 can become archive escrow witness, sponsor-burdened signer, absent signer, or hostile witness when a first-custody slip is used as indemnity.
- 认领人现场接待线 can consume a shelf when a claimant body or floor receipt is treated as settlement inventory.
- 经营压缩台 can try to count a shelf as closed output; this storyline must expose the still-recallable scar.
Missability and recovery
The storyline is missed when implementation:
- treats liability as abstract money or universal waiver;
- records only
sponsor_paid,archive_safe,worker_signed, orclaimant_released; - hides proposed holder state;
- hides burdened or excluded reader;
- lets a worker, claimant, or archive copy carry recourse silently;
- turns split recourse into universal acceptance;
- produces no future recall reader;
- opens from fixed timing or count.
Recovery is allowed only through visible scar: reopen assignment, unwind sponsor release, protect worker testimony, quarantine archive copy, publish public/fan recall, reassign producer license burden, convert to recovery-only, or accept a costlier route.
Replay evidence expectation
storyline_id: storyteller.storyline.recovery_indemnity_shelf.v1
session_id: lens-recovery-indemnity-shelf-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
trigger_kind: state_pressure
source_object_present: true
source_scar_present_or_explicit_absence: true
proposed_or_missing_indemnity_holder_visible: true
protected_reader_present: true
burdened_or_excluded_reader_present_or_explicit_absence: true
future_recall_reader_present: true
no_fixed_turn_trigger: true
offered:
card: storyteller.card.recovery_indemnity_shelf.v1
rite: storyteller.rite.recovery_indemnity_assignment.v1
branch_runs:
assignment_branch:
selected_branch: sponsor_retains | producer_underwrites | archive_escrow | public_fan_trust | worker_protected_refusal | split_recourse | quarantine_source
source_object: <object>
proposed_holder: <holder>
protected_reader_state_after: <state>
burdened_reader_state_after: <different state>
holder_state_after: <state>
shelf_state_after: <state>
future_route_effect: <effect>
counter_deltas:
relief: []
cost: []
future: []
default_branch:
event_seen_or_armed: storyteller.event.recovery_indemnity_default.v1
default_actor: <actor>
false_clean_claim: <claim>
burdened_or_hidden_reader: <reader>
holder_state_after: <state>
future_route_effect: <effect>
assertions:
- entry_is_state_triggered
- source_scar_visible
- proposed_holder_visible_or_explicit_absence
- protected_and_burdened_readers_visible
- worker_or_claimant_liability_is_not_silent
- holder_state_mutates
- readers_diverge
- success_has_cost
- default_is_durable
- future_recall_reader_consumes_shelf
- no_fixed_turn_triggerNon-goals
- Not raw content-count expansion.
- Not legal governance.
- Not abstract insurance.
- Not sponsor makegood, sponsor afteruse, recovery inventory, or route custody again.
- Not a fixed upkeep phase.
- Not valid unless the shelf changes future playable state.