Dormant Claim Resurfacing / 休眠认领复燃线

Dormant Claim Resurfacing is a long-campaign pressure storyline for the moment when an old unresolved row becomes relevant to a new crisis.

The player has already created many durable consequences: a correction row delayed for sponsor safety, a stabilization ticket carried by a proxy, an archive order served late, an ending scar marked recovery-only, a handler burden hidden under production pressure, a public receipt split between lawful and fan routes, or a route asset captured by the wrong claimant.

This storyline asks: when the later crisis touches that old row, do you seat it, merge it, route it, defer it with collateral, split it honestly, retire it with scar, or suppress it until it breaches?

Why this is the next useful expansion

The current mesh is strong at creating local ledgers. Recent systems produce durable rows for correction, cutroom priority, handler burden, stabilization liability, ending scar, archive enforcement, witness payroll, proxy posture, public contrition, and route custody.

The highest-value gap is now resurfacing discipline. Without a shared resurfacing line, old rows can either disappear between sessions or flood the player as undifferentiated backlog. Both outcomes hurt the product:

• disappearance makes consequences fake;
• backlog flood makes long campaigns noisy;
• fixed turn callbacks violate Storyteller’s state-driven design;
• local workers may keep inventing new ledgers instead of bringing old rows back into play.

This storyline turns old consequences into state-triggered, selectable, replay-visible pressure.

Primary playable question

A later crisis now needs a proof, carrier, claimant, correction slot, enforcement action, stabilization carrier, handler, edit lane, or ending posture that an old row can affect. Which old row is allowed to resurface, where is it seated, and what becomes harder because it was not cleanly resolved earlier?

Every branch must name:

• the source row and source session;
• the current surface that made it relevant;
• the selected seat or specialist route;
• benefited and harmed claimants;
• carrier or explicit absence;
• proof anchor or explicit absence;
• current relief;
• future cost.

Content pack

Mechanic

• 休眠认领复燃机制 — defines row state, maturity conditions, selection pressure, branch families, and replay evidence.

Card

• 到期认领队列 — durable card that stores rows eligible to resurface without becoming a generic task list.

Rite

• 休眠认领复核 — assignable rite for seating, merging, routing, deferring, splitting, suppressing, or retiring a matured row.

Event

• 休眠认领破口 — breach event when a relevant row is omitted, wrongly seated, falsely quieted, or allowed to be narrated by a rival.

State-triggered entry

Open this storyline when all of the following are true:

1. a previous branch created a durable row in a card, docket, ticket, ledger, scar, proof object, or route asset;
2. the row is unresolved or scarred rather than cleanly complete;
3. the current crisis requests a resource the row can materially affect;
4. at least two responses are available;
5. the row can change current pressure and future route effect;
6. source provenance can be preserved.

The storyline must not open because of a fixed turn number, arbitrary day interval, raw content count, or lens health status.

Storyline spine

Beat 1 — A local ledger leaves a dormant row

A previous system creates a row that is neither active nor gone.

Examples:

• a correction slot row is delayed after sponsor countercopy;
• a stabilization liability ticket is underwritten but not called;
• an archive enforcement order is appealed and not executed;
• an ending scar is marked public-only or recovery-only;
• a handler burden makes a future assignment costlier;
• a route asset is captured, protected, false-owner, missed, or hostile;
• a public receipt is split between lawful proof and fan testimony.

The row enters 到期认领队列 as dormant or watchlisted.

Beat 2 — A later surface makes the row matter

A current crisis asks for something the old row controls or contradicts.

Examples:

• 更正档期竞拍线 asks for a proof anchor and the old row says the proof was captured;
• 归档执行案卷 needs a carrier and the old row says the carrier became hostile;
• 稳定化责任交接线 asks for a harmed claimant and the old row names the omitted party;
• 结局伤痕账本线 asks for clean closure and the old row blocks clean laundering;
• 处理人负荷账本 asks for a handler and the old row says the handler is refusing, captured, or recovered with scar;
• 制作分诊台 asks what live pressure should occupy limited production capacity.

The row becomes matured.

Beat 3 — The player reviews the matured row

The player runs 休眠认领复核. The rite requires source row, source session, current surface, current relevance, selected seat, carrier or absence, proof anchor or absence, finite capacity or collateral, benefited claimant, harmed claimant, and selected response.

The review must be a choice. A single automatic popup does not satisfy the storyline.

Beat 4 — The row is seated, routed, deferred, split, retired, or breached

The branch determines how the old consequence returns to play.

Valid outcomes:

• seat now;
• merge into current crisis;
• route to specialist;
• defer with collateral;
• split claim;
• retire with scar;
• suppress and breach.

Each outcome must mutate at least three counters or durable states.

Beat 5 — Future play inherits the resurfaced cost

The row state after review changes later content:

• a correction becomes public-only, lawful-only, counterbroadcast-ready, or costlier;
• enforcement gains a carrier, loses a carrier, or hardens a wrong owner;
• stabilization becomes callable, underwritten, proxy-carried, or recovery-only;
• ending eligibility blocks clean laundering or splits canon;
• handler assignment becomes costlier, hostile, absent, or scarred but available;
• route asset custody becomes protected, captured, hostile, false-owner, sacrificed, or route_asset with explicit cost.

Branch map

Branch A — Seat now

The player spends capacity and names a carrier so the row directly affects the current surface.

Expected outcomes:

selected_response: seat_now
row_state_after_any: [seated, active, merged]
relief_any: [custody_clarity_up, reality_drift_down, public_receipt_legitimacy_up, clean_laundering_blocked, handler_assignment_truthful]
cost_any: [capacity_spent, sponsor_pressure_up, inspection_heat_up, edit_debt_up, handler_burden_up, public_exposure_up]
future_route_effect_any: [unlocked_with_scar, costlier, public_only, lawful_only, recovery_only]

Branch B — Merge into current crisis

The player lets the old row reshape the live branch instead of opening a separate surface.

Expected outcomes:

selected_response: merge_current
current_surface_mutated: true
row_state_after_any: [merged, split, costlier, recovery_only]
branch_change_any: [new_required_proof, harmed_claimant_added, rival_row_watchlisted, clean_success_blocked, carrier_absence_visible]

Branch C — Route to specialist surface

The player acknowledges the row but redirects it to the right system.

Expected outcomes:

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, watchlisted]
current_surface_effect_any: [delayed, narrowed, costlier, partial_success, explicit_absence]

Branch D — Defer with collateral

The player delays the row and pays a visible cost.

Expected outcomes:

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]
relief_any: [immediate_pressure_contained, current_surface_not_blocked]
cost_any: [collateral_callable, future_route_cost_up, claimant_resentment_up]

Branch E — Split claim

The player admits that one old row now supports incompatible truths.

Expected outcomes:

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, ending_costlier]

Branch F — Retire with scar

The player closes the row honestly and preserves its consequence.

Expected outcomes:

selected_response: retire_with_scar
row_state_after: retired_with_scar
claimant_accounting_preserved: true
future_route_effect_any: [scar_preserved, future_cost_retained, route_restriction_retained, clean_laundering_blocked]

If a future reader later cites the retired row as clean closure, route that use through Matured Claim Retirement Afteruse Receipt. The retirement state, source row, scar, harmed claimant, proof or collateral bridge, afteruse reader, and future effect must travel with the claim.

Branch G — Suppress or ignore

The player hides the row, omits harmed claimant, refuses capacity, or calls it clean without proof.

Expected outcomes:

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, black_screen_pressure_up]

Character and faction hooks

• Yu Lan can seat public witness rows, but exposure and sponsor retaliation rise.
• Shen Luo can defer with sponsor collateral, but contract capture and public distrust rise.
• Han Yanshuang can route rows to lawful review, but bureau favor debt and inspection heat rise.
• Baiya can merge a row into edit continuity, but edit debt and source ambiguity rise.
• Inspector Rhee Archive can harden admissibility, but archive visibility and seizure pressure rise.
• Han Cutroom can seat or delay edit-lane claims, but cutroom exhaustion and final-cut debt rise.
• Low-rank route assets from Route Assets and Custody can become carriers, hostile witnesses, captured proof, or collateral.

Missability and recovery

This storyline is missable when the implementation:

• forgets a source row across sessions;
• marks old rows resolved without scar, claimant, or route restriction;
• offers all dormant rows at once without relevance selection;
• triggers resurfacing from fixed turn count;
• lets a current surface use proof, handler, or route asset that an old row marked captured, hostile, absent, or false-owner;
• hides the harmed claimant.

Recovery is allowed only with visible cost:

• reopen through public correction;
• lawful appeal;
• sponsor escrow call;
• edit checksum release;
• handler recovery with scar;
• route asset rescue or sacrifice;
• fan refund or public bond;
• production triage lane scar;
• ending scar audit.

Replay/session evidence shape

storyline: storyteller.storyline.dormant_claim_resurfacing.v1
session_id: lens-dormant-claim-resurfacing-v1-<timestamp>
seed: <deterministic-seed>
source_inventory:
  rows_considered:
    - source_surface: <prior surface>
      source_session_id: <prior session>
      source_seed: <prior seed>
      row_id: <stable row>
      row_state_before: <state>
current_surface:
  surface_id: <current surface>
  requested_resource_any: [claimant, proof, carrier, correction, enforcement, stabilization, ending, handler, public_statement, edit_lane, route_asset, production_capacity]
selection:
  selected_row_id: <row>
  reason: proof_match | claimant_match | carrier_match | route_effect_match | contradiction_match | breach_risk_match
  unselected_rows_after: <dormant/watchlisted/deferred_with_collateral/default_ready>
review:
  card: storyteller.card.matured_claim_queue.v1
  rite: storyteller.rite.dormant_claim_review.v1
  selected_response: seat_now | merge_current | route_to_specialist | defer_with_collateral | split_claim | retire_with_scar | suppress_or_ignore
outcome:
  emitted_event: storyteller.event.dormant_claim_breach.v1 | none_if_valid
  row_state_after: <state>
  current_surface_effect: <effect>
  future_route_effect: <effect>
  counter_deltas: {}
assertions:
  - source_provenance_preserved
  - state_triggered_entry
  - selected_row_relevant_to_current_surface
  - branch_outcomes_diverge
  - no_fixed_turn_trigger
  - future_route_effect_mutates

Non-goals

• Not a dashboard/replay governance page.
• Not raw campaign-length scoring.
• Not a fixed callback calendar.
• Not a generic task queue.
• Not a replacement for correction slot, stabilization liability, archive enforcement, ending scar, handler burden, or route custody.
• Not filler escalation.
• Not satisfied by page existence; replay must show source row, selection reason, review choice, branch mutation, and future effect.