Dormant Claim Resurfacing / 休眠认领复燃机制

Dormant Claim Resurfacing is the mechanism that turns old unresolved rows back into playable pressure when later state makes them relevant.

The current Storyteller mesh can already create many durable rows: correction slots, stabilization tickets, archive enforcement orders, ending scars, handler burdens, public receipts, cutroom debts, witness payroll risk, and route-asset custody states. The missing mechanic is not another verdict. It is the stateful resurfacing layer that prevents those rows from being forgotten, while also preventing every old row from firing as noise.

Mechanic promise

When a previous row can materially affect a current crisis, the game must either:

• seat it in the current surface;
• merge it into the live rite or event;
• route it to a named specialist surface;
• defer it with collateral;
• split it between incompatible claimants;
• retire it with a scar;
• or breach it visibly through 休眠认领破口.

The mechanism fails if old rows silently expire, if rows resurface only because a turn number arrived, or if all dormant rows are dumped into the offer set without selection pressure.

Core objects

Queue card

到期认领队列 stores eligible dormant rows with source provenance, claimant accounting, maturity condition, valid seats, and future risk.

Review rite

休眠认领复核 lets the player choose how a matured row enters, redirects, delays, splits, or breaches the current surface.

Breach event

休眠认领破口 fires when the row becomes relevant but is omitted, over-deferred, sent to the wrong seat, or falsely marked clean.

State machine

claim_state:
  dormant:
    effect: row exists but no current surface needs it
  watchlisted:
    effect: future state condition is named
  matured:
    effect: current surface can be affected by row
  offered:
    effect: player can choose response
  seated:
    effect: current surface now reads the row
  merged:
    effect: current rite/event changes branch outcomes
  routed:
    effect: named specialist surface must handle it
  deferred_with_collateral:
    effect: delay is allowed because cost/carrier exists
  split:
    effect: incompatible claimants remain simultaneously valid
  suppressed:
    effect: omission becomes default-ready
  breached:
    effect: breach event mutates future state
  retired_with_scar:
    effect: row closes but leaves claimant, scar, or route restriction

A valid row transition must preserve source provenance and claimant accounting.

Entry rule

Open the mechanism when all of the following are true:

1. a previous row exists from a ledger, docket, ticket, scar, receipt, burden, proof object, or route asset;
2. the row is not cleanly resolved: it is dormant, watchlisted, deferred, disputed, hostile, captured, recovery-only, public-only, lawful-only, sponsor-only, false-owner-risk, or equivalent;
3. the current surface asks for something the row can affect: claimant, proof, carrier, correction, enforcement, stabilization, ending eligibility, handler assignment, public statement, edit lane, route asset, or production capacity;
4. at least two responses are possible;
5. the outcome can mutate current pressure and future route effect.

No canonical trigger may depend on fixed turn count, arbitrary day count, raw content count, or dashboard health.

Selection pressure

The implementation should not offer every dormant row at once. A resurfacing pass must select rows by state relevance:

selection_relevance:
  proof_match: row names proof requested by current surface
  claimant_match: row names claimant harmed or benefited by current surface
  carrier_match: row names handler, proxy, route asset, public bond, legal hold, edit lane, or production lane requested now
  route_effect_match: row can block, alter, or unlock current route
  contradiction_match: row can contradict clean closure, lawful-only closure, public-only closure, or sponsor-safe closure
  breach_risk_match: row has false-owner, hostile, captured, recovery-only, or deferred-without-collateral state

A row that lacks these matches remains dormant or watchlisted; it should not become filler.

Branch families

Seat current surface

A matured row enters the current rite, event, or route.

Required mutation:

• current branch gains claimant/proof/cost specificity;
• the row becomes seated or merged;
• at least three counters or durable states change.

Route to specialist

A row is admitted but sent to the surface that can resolve it.

Possible specialist sinks:

• 更正档期竞拍线;
• 归档执行案卷;
• 稳定化责任交接线;
• 结局伤痕账本线;
• 处理人负荷账本;
• 制作分诊台.

Required mutation:

• row state becomes routed or pending review;
• target sink and required inputs are named;
• current surface becomes delayed, costlier, narrowed, or scarred.

Defer with collateral

The player postpones the row by assigning a carrier, bond, escrow, legal hold, edit checksum, route asset, fan refund pool, handler time, or production lane.

Required mutation:

• row becomes deferred_with_collateral;
• collateral becomes callable;
• current crisis receives relief or containment;
• future route cost rises.

Split claim

The old row now belongs to more than one claimant.

Required mutation:

• at least two claimants remain valid;
• row becomes split, public-only, lawful-only, sponsor-only, or equivalent;
• later clean closure is blocked unless the split is resolved or carried as scar.

Suppress or false-clean

The player hides the row or closes it without proof, carrier, harmed claimant, or scar.

Required mutation:

• 休眠认领破口 fires or becomes default-ready;
• future route effect becomes hostile, captured, recovery-only, costlier, contradiction-pending, false-owner-risk, or blocked.

Retire with scar

The player closes a row honestly by preserving its cost.

Required mutation:

• row becomes retired_with_scar;
• claimant benefited and harmed remain recorded;
• a scar, restriction, future cost, public-only/lawful-only state, or route asset custody change remains.

Counter contract

Every resolved resurfacing branch must change at least three counters or durable states. At least one must represent current relief and one must represent future cost.

Suggested states:

• dormant_claim_pressure
• claim_queue_integrity
• resurfacing_debt
• future_correction_cost
• future_enforcement_cost
• future_stabilization_cost
• ending_clean_laundering_blocked
• handler_refusal_pressure
• route_asset_custody
• public_receipt_legitimacy
• public_receipt_distrust
• sponsor_stop_loss_pressure
• inspection_heat
• archive_debt
• edit_debt
• black_screen_pressure
• false_owner_risk
• production_lane_scar

Cross-system bridges

• With 更正档期竞拍线, a dormant row can demand the correction slot or become counterbroadcast-ready.
• With 稳定化责任交接线, an old ticket can recall its carrier or collateral.
• With 归档执行案卷, an unserved order can mature when the obligated party appears in another surface.
• With 结局伤痕账本线, a scar can resurface before terminal resolution and block clean laundering.
• With 处理人负荷账本, handler overuse can resurface as explicit refusal, capture, or required recovery.
• With Route Assets and Custody, captured, hostile, missed, sacrificed, or false-owner route assets can mature when later proof or carrier state depends on them.
• With Matured Claim Retirement Afteruse Receipt, a retired_with_scar, deferred_with_collateral, split, or recovery-only row can be cited later only through named afteruse scope, claimant accounting, bridge, and future effect.

Replay/session evidence shape

mechanic: storyteller.mechanic.dormant_claim_resurfacing.v1
session_id: lens-dormant-claim-resurfacing-v1-<timestamp>
seed: <deterministic-seed>
source_rows:
  - source_surface: <prior surface>
    source_session_id: <prior session>
    source_seed: <prior seed>
    row_id: <stable row>
    row_state_before: dormant | watchlisted | deferred | disputed | hostile | captured | recovery_only | public_only | lawful_only | sponsor_only | false_owner_risk
current_surface:
  surface_id: <current crisis or route>
  requested_resource_any: [claimant, proof, carrier, correction, enforcement, stabilization, ending, handler, public_statement, edit_lane, route_asset, production_capacity]
selection:
  selected_row_id: <row>
  selection_reason: proof_match | claimant_match | carrier_match | route_effect_match | contradiction_match | breach_risk_match
  unselected_rows_state_after: <dormant/watchlisted/deferred_with_collateral/default_ready>
review:
  offered_card: storyteller.card.matured_claim_queue.v1
  offered_rite: storyteller.rite.dormant_claim_review.v1
branch_result:
  selected_response: seat_now | merge_current | route_to_specialist | defer_with_collateral | split_claim | suppress_or_ignore | retire_with_scar
  emitted_event: storyteller.event.dormant_claim_breach.v1 | none_if_valid
  row_state_after: <state>
  future_route_effect: <effect>
  counter_deltas: {}
assertions:
  state_triggered_entry: true
  provenance_preserved: true
  selected_row_matters_to_current_surface: true
  no_fixed_turn_trigger: true

Non-goals

• Not a governance or dashboard process.
• Not a raw long-campaign progress meter.
• Not a fixed callback timer.
• Not a generic event backlog.
• Not a content-count expansion.
• Not a way to clean every old debt at once.
• Not satisfied by page existence; replay must show source row, selection reason, review choice, branch result, counter deltas, and future route effect.