False-Service Claimant Escalation / 误服裁定认领升级机制

False-Service Claimant Escalation is the mechanism that turns a claimant-facing 执行负荷违约 into a playable row rather than a prose-only penalty.

It sits between 裁定执行负荷机制, 认领人现场接待机制, and 压力认领人转化链机制. The source ruling remains history. The false service becomes a claimant row with gate, proof, demanded control, and future-reader consequences.

Design problem

Ruling Enforcement Load already prevents a valid ruling from becoming a universal key. Its default event can name claimant_queue_first, pirate_receipt_first, artist_boundary_break, floor_overrun_first, management_false_clean, or sponsor_compression_first as narrators.

The remaining gap is downstream executability: when one of those narrators is claimant-facing, the game must not stop at “a claimant is angry.” It must create a row that can be received, converted, exposed, quarantined, suppressed, missed, or hardened.

State-triggered entry

Open this mechanism only when all are true:

entry_state:
  trigger_kind: state_pressure
  source_default_event: storyteller.event.enforcement_load_default.v1
  default_narrator_is_claimant_facing: true
  source_ruling_or_row_preserved: true
  missing_or_false_load_row_named: true
  attempted_future_reader_present: true
  demanded_control_or_explicit_absence_present: true
  future_route_effect_if_unanswered_present: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true

If the default narrator is management, sponsor, archive, inspector, pirate, artist, claimant, or floor-facing but no concrete claimant can be named, the mechanism records named_claimant_or_absence: explicit_absence and still requires a future route effect.

Core objects

• 误服裁定认领行 stores source ruling, missing load row, attempted reader, claimant family, named claimant or explicit absence, demanded control, proof or absence, gate or absence, and future route effect.
• 误服裁定认领升级 resolves the row through public receipt, bounded conversion, false-service exposure, boundary quarantine, sponsor countercopy, suppression, or hardening.
• 误服裁定认领硬化 fires or arms when the row is hidden, underfilled, wrong-gated, suppressed, or answered without durable cost.

Claimant-facing default narrators

Default narrator	Escalated claimant row	Primary danger
claimant_queue_first	omitted claimant, fan public, archive clerk, inspector proxy, public witness	row becomes hostile or public-only before lawful service
pirate_receipt_first	pirate relay, public historian, fan queue, unofficial proof carrier	official route becomes public-only or counterbroadcast-ready
artist_boundary_break	artist, voice/body carrier, witness, refusal holder	boundary-gated or recovery-only route
floor_overrun_first	floor carrier, audience gate, oxygen floor, crew witness	live floor or proof carrier refuses future service
management_false_clean	omitted claimant hidden by metric report	false-clean report becomes future claimant leverage
sponsor_compression_first	sponsor counterparty or public claimant omitted by private relief	sponsor-only route, appeal-required reader, public distrust

State machine

states:
  - false_service_row_expected
  - false_service_row_created
  - received_at_floor
  - public_receipt_created
  - converted_bounded
  - counterclaim_exposed
  - boundary_quarantined
  - sponsor_countercopy_recorded
  - suppressed_without_receipt
  - missed_claimant
  - hostile_claimant
  - false_first_claimant
  - recovery_only_claimant
  - coalition_seed

The source ruling is never erased. A branch changes how the false-served row and future route can use that source.

Branch contract

Every branch must mutate at least three surfaces:

• one relief surface;
• one cost surface;
• one claimant, target, future reader, or route surface.

Primary surfaces:

surfaces:
  - false_service_exposed
  - false_service_claimant_rows_open
  - claimant_row_received
  - claimant_conversion_window
  - claimant_hostility
  - claimant_missed
  - false_first_claimant
  - public_receipt_legitimacy
  - public_receipt_distrust
  - fan_oxygen_resentment
  - sponsor_stop_loss_pressure
  - contract_capture
  - inspection_heat
  - bureau_favor_debt
  - archive_debt
  - proof_chain_integrity
  - artist_refusal_respected
  - witness_exposure
  - crew_refusal_risk
  - floor_lane_load
  - handler_burden
  - future_route_acceptance
  - route_recovery_cost
  - producer_license_pressure
  - management_pressure
  - coalition_seed_pressure

Integration rules

• With 裁定执行负荷线, this mechanism is required only after an enforcement default names a claimant-facing narrator.
• With 认领人现场接待线, the row must expose a gate or explicit gate absence before it can be received.
• With 压力认领人转化链, the row may become a recruitable, bounded, appeased, hostile, missed, mandate-held, or coalition-seed claimant.
• With 裁定读者冲突线, the false-service claimant may become an incompatible reader of the same source ruling.
• With 认领撞锁, the row may claim a route asset, proof object, custody copy, or public copy.
• With 经营压缩台, a false clean metric cannot hide the row without creating a management scar or hardening branch.
• With 直播现场班组负荷线, a floor-facing default must name actual floor lane state or explicit absence.

Failure modes

The mechanism fails if any are true:

• enforcement default says a claimant moved first but no card row exists;
• the row has no source ruling or missing load;
• the row has no demanded control;
• the row has no gate or explicit gate absence;
• the row has no future reader effect;
• a sponsor, law, archive, editor, public apology, or management metric clears the row for free;
• missed or suppressed rows do not become durable hostile, false-first, public-only, lawful-only, sponsor-only, coalition, or recovery-only state;
• entry depends on fixed turn, day, week, chapter, dashboard, or raw content count.

Replay evidence shape

mechanic: storyteller.mechanic.false_service_claimant_escalation.v1
session_id: lens-false-service-claimant-escalation-v1-<timestamp>
seed: <deterministic-seed>
source_default:
  event: storyteller.event.enforcement_load_default.v1
  default_narrator: <narrator>
  source_ruling_or_row: <source>
  missing_or_false_load_row: <row>
entry_state:
  trigger_kind: state_pressure
  default_narrator_is_claimant_facing: true
  attempted_future_reader_present: true
  no_fixed_turn_trigger: true
offered:
  card: storyteller.card.false_service_claimant_row.v1
  rite: storyteller.rite.false_service_claimant_escalation.v1
branch_runs:
  constructive_branch:
    selected_response: receive_publicly | convert_bounded | expose_false_service | boundary_quarantine
    row_state_after: <state>
    claimant_state_after: <state>
    future_reader_effect: <effect>
    counter_deltas: {}
  hardening_branch:
    selected_response: sponsor_countercopy | suppress_without_receipt | let_harden
    event_seen_or_armed: storyteller.event.false_service_claimant_hardening.v1
    row_state_after: <state>
    claimant_state_after: <state>
    future_reader_effect: <effect>
    counter_deltas: {}
assertions:
  - source_ruling_preserved
  - default_narrator_claimant_facing_or_absent_recorded
  - false_service_claimant_row_visible
  - gate_or_explicit_absence_visible
  - demanded_control_visible
  - branch_has_relief_cost_future_effect
  - hardening_is_durable
  - no_fixed_turn_trigger
  - no_fixed_day_or_week_trigger

Non-goals

• Not a new verdict.
• Not a time window.
• Not a generic faction backlash system.
• Not a governance or dashboard page.
• Not a replacement for claimant intake or pressure conversion.
• Not valid unless false service becomes concrete claimant state with future route consequences.