Pressure Claimant Hardening Default / 压力认领人硬化默认

Pressure Claimant Hardening Default is the event that resolves when a row on 压力认领人转化案卷 is ignored, hidden, answered without cost, or mishandled until the claimant narrates first.

It is the bridge between an operational default and a durable RPG consequence. The default actor stops being a generic pressure source and becomes missed, hostile, captured, mandate-holding, false-owner, public-only, sponsor-only, lawful-only, editor-only, recovery-only, or a seed for later collision/coalition pressure.

Event promise

A hardening default must answer four questions:

1. Which claimant gained control?
2. Which target changed state?
3. Which future route is now blocked, costlier, captured, hostile, or recovery-only?
4. What recovery or terminal consequence is now visible?

The event fails design review if it only says that the sponsor, inspector, archive, fans, editor, claimant, or route asset is angry.

Fire or arm condition

Fire immediately, or arm for the next relevant route check, when all are true:

1. a pressure claimant row exists on 压力认领人转化案卷;
2. the row has a named claimant, target, leverage, demanded control, and future route effect;
3. the player does not assign a credible handler, proof, boundary, payment, concession, apology, quarantine, or counterclaim;
4. the claimant has enough leverage to narrate, seize, sell, freeze, expose, or refuse the target;
5. no valid branch explicitly delays or converts the row.

This event is state-triggered. It must not fire from fixed turn number, arbitrary day count, or lens-health state.

Hardening branches

Branch A — Missed claimant

The claimant becomes unavailable as a clean recruit or bounded helper because the production failed to answer the window.

event_branch: missed_claimant
claimant_state_after: missed | unavailable | no_longer_clean_recruit
future_route_effect: costlier | alternate_required | recovery_only
recovery_hook: apology | payment | proof_submission | public_receipt | explicit_absence

Branch B — Hostile claimant

The claimant becomes an active hostile route pressure.

event_branch: hostile_claimant
claimant_state_after: hostile | hostile_witness | hostile_auditor | hostile_sponsor | hostile_editor | hostile_public_queue
future_route_effect: hostile | blocked | costlier
counter_deltas_required: true

Branch C — Captured or false owner

The claimant captures the target or hardens as the public owner.

event_branch: captured_or_false_owner
claimant_state_after: captured_owner | false_owner | sponsor_only | lawful_only | editor_only | public_only | archive_only
target_state_after: captured | false_owned | channel_locked | custody_split
future_route_effect: captured | blocked | lawful_conversion_required | public_counterclaim_required

Branch D — Mandate holder

An inspector, archive desk, sponsor office, or lawful claimant gains an enforcement mandate that changes future assignments.

event_branch: mandate_holder
claimant_state_after: mandate_holder | seizure_authority | stop_loss_holder | docket_owner
target_state_after: frozen | seized | sponsor_held | lawful_only | recovery_only
future_route_effect: permit_required | audit_required | sponsor_gate_required | recovery_only

Branch E — Coalition seed

The row does not become a full coalition yet, but it records enough memory to combine later with a second row.

event_branch: coalition_seed
claimant_state_after: coalition_seed
seed_memory: prior_denial | unpaid_debt | exposed_contradiction | custody_loss | public_harm | sponsor_loss | bureau_cost
future_route_effect: watchlisted | costlier | collision_ready

Required payload

event: storyteller.event.pressure_claimant_hardening_default.v1
source_docket: storyteller.card.pressure_claimant_conversion_docket.v1
source_default_event: storyteller.event.unstaffed_crisis_default.v1 | storyteller.event.route_asset_maintenance_default.v1 | equivalent | explicit_absence
row:
  row_id: <row>
  default_actor: <actor family>
  named_claimant: <character/faction/public queue/proof carrier>
  target: <person/proof/asset/slot/copy/route>
  leverage: <leverage>
  demanded_control: <demanded control>
  conversion_window_state_before: offered | narrowing | last_clean_offer | hardening_ready
missing_or_failed_response:
  handler: <handler or explicit_absence>
  proof: <proof or explicit_absence>
  boundary: <boundary or explicit_absence>
  cost: <cost or explicit_absence>
result:
  event_branch: missed_claimant | hostile_claimant | captured_or_false_owner | mandate_holder | coalition_seed
  claimant_state_after: <state>
  target_state_after: <state>
  future_route_effect: <blocked | costlier | hostile | captured | recovery_only | contradiction_pending | watchlisted>
  recovery_hook_or_terminal: <hook or terminal>
  counter_deltas: {}

Counter contract

Every fired branch must mutate at least three counters or durable states.

At least one mutation must be claimant state, one target or route state, and one cost/pressure state.

Typical deltas:

• pressure_claimant_rows_open: -1
• claimant_conversion_window: closed
• claimant_missed: +1 on missed branch
• claimant_hostility: +1 on hostile branch
• claimant_capture: +1 on captured branch
• claimant_mandate_strength: +1 on mandate branch
• coalition_seed_pressure: +1 on coalition seed branch
• future_route_acceptance: blocked/costlier/hostile/captured/recovery-only
• route_asset_custody: captured/split/frozen/recovery-only
• inspection_heat: +1 on inspector/mandate branch
• sponsor_stop_loss_pressure: +1 or -1 depending who captured relief
• contract_capture: +1 on sponsor/custody trade branch
• archive_debt: +1 on archive/seizure branch
• edit_debt: +1 on editor-only branch
• public_receipt_distrust: +1 when public proof is lost
• fan_oxygen_resentment: +1 when fan public is bypassed
• black_screen_pressure: +1 when contradiction/blackout hardens

Recovery rules

Recovery is allowed only if the event records a hook and a scar.

Valid recovery hooks:

• public apology with receipt;
• payment or restitution queue;
• lawful audit or voice token;
• sponsor escrow concession;
• archive counter-receipt;
• editor checksum disclosure;
• safehouse/protection assignment;
• route asset rescue;
• bounded quarantine;
• coalition split after a second row appears.

If no recovery hook is recorded, the event must mark the affected future route as terminally blocked or require a replacement path.

Integration notes

• With 无人派工危机默认, this event converts a missed ticket’s default actor into an RPG row.
• With 路线资产维护违约, this event turns a stale asset default into claimant leverage.
• With 认领撞锁线, two hardening rows can later collide over the same target.
• With 反向同盟锁线, two hardened rows with spend/loss memory can later coordinate.

Non-goals

• Not a random punishment scene.
• Not a fixed countdown.
• Not a generic reputation loss.
• Not valid if no claimant state changes.
• Not valid if no target or future route changes.
• Not valid if recovery is free or implicit.