Dormant Claim Review / 休眠认领复核

Dormant Claim Review is the assignable rite for deciding what happens when an old row becomes relevant to the current crisis.

The rite is offered only when a prior claim, liability, scar, burden, receipt, custody state, or enforcement order has matured through current state. It gives the player a management/RPG choice: seat the row now, merge it into the live crisis, route it to the proper specialist surface, defer it with collateral, split it between claimants, or suppress it and risk breach.

Fillable slots

A valid use of this rite must require the following inputs or explicit absence values:

required_slots:
  resurfaced_row: <row id from earlier ledger/docket/ticket/scar/burden/route asset>
  source_provenance: <source session id, seed, and source surface>
  current_surface: <current crisis, rite, event, route, or ending candidate>
  why_relevant: <state condition>
  selected_seat: correction_slot | archive_enforcement | stabilization_handoff | ending_scar | handler_burden | production_triage | public_contrition | cutroom_priority | route_asset | equivalent
  claimant_benefited: <claimant>
  claimant_harmed: <claimant>
  carrier_or_explicit_absence: <handler, proof, public, route asset, docket, card, or absence>
  proof_anchor_or_absence: <proof object, receipt, seal, checksum, testimony, or absence>
  capacity_or_collateral: <slot, legal window, edit lane, handler time, public attention, sponsor review, bond, route capacity, or none>
  selected_response: seat_now | merge_current | route_to_specialist | defer_with_collateral | split_claim | suppress_or_ignore

The rite fails if the old row is presented as flavor without source provenance and current relevance.

State-triggered offer rule

Offer this rite when all of the following are true:

1. at least one prior row is unresolved, deferred, disputed, hostile, captured, public-only, lawful-only, sponsor-only, recovery-only, false-owner-risk, or watchlisted;
2. a current surface asks for a claimant, proof, handler, route asset, correction, enforcement, stabilization, ending eligibility, public statement, or cutroom priority that the row can affect;
3. the player has at least two meaningful responses, including one that seats or routes the row and one that defers, suppresses, or pays collateral;
4. the result can mutate at least three counters or durable states.

No fixed turn number, arbitrary day count, or content quota may be the canonical trigger.

Branch families

Branch A — Seat now

The player assigns capacity and carrier so the row enters the current surface.

Expected outcome:

selected_response: seat_now
row_state_after_any: [seated, active, merged]
relief_any: [claim_queue_integrity_up, reality_drift_down, custody_clarity_up, public_receipt_legitimacy_up, ending_clean_laundering_blocked]
cost_any: [capacity_spent, inspection_heat_up, sponsor_pressure_up, edit_debt_up, handler_burden_up, public_exposure_up]

Branch B — Merge into current crisis

The player lets the old row modify the live rite instead of opening a separate specialist surface.

Expected outcome:

selected_response: merge_current
current_surface_mutated: true
row_state_after_any: [merged, costlier, split, public_only, lawful_only, recovery_only]
future_route_effect_any: [unlocked_with_scar, harder, rival_row_watchlisted, clean_success_blocked]

Branch C — Route to specialist

The player sends the row to the correct downstream surface.

Expected outcome:

selected_response: route_to_specialist
specialist_surface_any: [correction_slot, archive_enforcement, stabilization_handoff, ending_scar, handler_burden, production_triage, public_contrition, cutroom_priority]
row_state_after_any: [routed, pending_review, costlier]
route_requirement_visible: true

Branch D — Defer with collateral

The player delays the row, but pays a bond, assigns a carrier, or records explicit collateral.

Expected outcome:

selected_response: defer_with_collateral
row_state_after: deferred_with_collateral
collateral_any: [public_bond, sponsor_escrow, legal_hold, edit_checksum, handler_time, route_asset, fan_refund_pool, production_lane]
future_breach_blocked_until_state_changes: true
cost_visible: true

Branch E — Split claim

The player accepts that one old row now creates two incompatible route surfaces.

Expected outcome:

selected_response: split_claim
row_state_after_any: [split, public_only, lawful_only, sponsor_only]
claimants_min: 2
future_route_effect_any: [split_custody, public_audit_required, lawful_appeal_required, sponsor_capture_risk]

Branch F — Suppress or ignore

The player hides the row, refuses capacity, omits harmed claimant, or treats it as expired.

Expected outcome:

selected_response: suppress_or_ignore
emitted_event: storyteller.event.dormant_claim_breach.v1
row_state_after_any: [breached, hostile, captured, recovery_only, contradiction_pending]
future_route_effect_any: [costlier, blocked, hostile_narration, false_owner_risk_up]

Required assignments

At least two of these assignment categories should be usable across implementation:

• handler: Han Yanshuang, Yu Lan, Shen Luo, Baiya, Inspector Rhee, Han Cutroom, Lin Qiao, Ai Sheng, or equivalent;
• proof: public receipt, archive seal, edit checksum, black-box fragment, fan queue receipt, witness testimony, voice receipt, release stamp, or continuity file;
• capacity: correction slot, edit lane, legal window, public attention, sponsor review, fan oxygen refund, route asset capacity, production lane, or handler time;
• collateral: public bond, sponsor escrow, legal hold, safehouse, payroll protection, route asset, or scarred ending row.

Output payload

rite: storyteller.rite.dormant_claim_review.v1
session_id: lens-dormant-claim-review-v1-<timestamp>
seed: <deterministic-seed>
input_row:
  source_surface: <surface>
  source_session_id: <id>
  source_seed: <seed>
  row_id: <row>
  row_state_before: <state>
current_surface:
  surface_id: <surface>
  why_relevant: <state condition>
assignments:
  selected_seat: <seat>
  carrier_or_absence: <carrier>
  proof_anchor_or_absence: <proof>
  capacity_or_collateral: <capacity>
  claimant_benefited: <claimant>
  claimant_harmed: <claimant>
branch_result:
  selected_response: seat_now | merge_current | route_to_specialist | defer_with_collateral | split_claim | suppress_or_ignore
  row_state_after: <state>
  future_route_effect: <effect>
  counter_deltas: {}

Non-goals

• Not a calendar upkeep rite.
• Not a generic backlog cleanup action.
• Not an automatic queue sorter.
• Not a turn-count resurfacing trigger.
• Not a way to erase old debt cheaply.
• Not satisfied by selecting a row; the selected response must mutate current pressure, old row state, and future route effect.