饶准 / Exclusion Adjuster

饶准 is the claim-desk adjuster who writes the small exclusion rider after a liability surface has supposedly been covered.

His playable progression lives in 饶准除外批改员线 and is observed by 饶准除外批改员 Lens.

He does not decide whether the original crisis happened. He does not replace 派系责任承保 or 稳定化责任交接线. His power is narrower: when a guarantee, handoff, callback, or readback branch says a future reader may proceed, he can ask which claim is actually covered and which claimant is silently excluded.

That makes him valuable exactly where implementation can become shallow. A sponsor escrow, lawful seal, callback acceptance, public receipt, or edit reserve should not become blanket coverage. 饶准 turns that hidden denial into a playable character state through 除外批单批改机制, 除外批单案卷, 除外批单听证, and 万能承保默认.

Play purpose

饶准 makes post-underwriting coverage personal and contestable.

When a covered version asks to travel into a later route, he can:

• draft a narrow rider that keeps one route open while naming an excluded claimant;
• challenge a fake blanket guarantee before it becomes clean universal permission;
• convert sponsor cover, lawful surety, public bond, edit reserve, or production carry into scoped coverage;
• become a narrow recruitable route asset for future rider-reading disputes;
• be captured by sponsor or management as a false-clean adjuster;
• become hostile if coerced, scapegoated, or forced to deny a named claimant without record.

Card identity

character_card:
  id: storyteller.character.rao_zhun_exclusion_adjuster.v1
  runtime_card_id: card.storyteller.rao_zhun_exclusion_adjuster.v1
  canon_name: 饶准
  title: Exclusion Adjuster / 除外批改员
  role: claim_desk_exclusion_rider_adjuster
  primary_storyline: storyteller.storyline.character_rao_zhun_exclusion_adjuster.v1
  primary_mechanic: storyteller.mechanic.exclusion_rider_adjustment.v1
  primary_card: storyteller.card.exclusion_rider_docket.v1
  primary_rite: storyteller.rite.exclusion_rider_hearing.v1
  primary_default: storyteller.event.blanket_coverage_default.v1
  runtime_rite_id: rite.storyteller.exclusion_rider_hearing.v1
  runtime_default_event_id: event.storyteller.blanket_coverage_default.v1
  primary_pressure:
    - liability_underwriting
    - stabilization_liability_handoff
    - broadcast_contract_readback
    - callback_consumption
    - sponsor_stop_loss
    - route_asset_custody
  recruitable: true
  missable: true
  hostile: true

Exact executable packet

Rao Zhun’s current character-lens runtime uses seven exact starter cards and seven exact required slots:

Slot	Runtime card
docket	card.storyteller.exclusion_rider_docket.v1
source_guarantee	card.storyteller.rao_zhun_source_guarantee.v1
future_reader	card.storyteller.rao_zhun_future_reader.v1
covered_claim	card.storyteller.rao_zhun_covered_claim.v1
excluded_claim	card.storyteller.rao_zhun_excluded_claim.v1
adjuster_state	card.storyteller.rao_zhun_exclusion_adjuster.v1
support_and_cost	card.storyteller.rao_zhun_support_cost.v1

All seven cards must be in hand and assigned to the matching slots. Rao Zhun cannot be replaced by an abstract adjuster-state tag, another person card, explicit absence, or a virtual assignment in this executable packet.

除外批单听证 has exactly eight stable choices. Only choice 6, recruit_or_protect_adjuster, recruits him and grants route_asset.rao_zhun_exclusion_adjuster. Choice 7, suppress_or_blanket_default, grants no route asset and arms:

• rao_zhun.default_pending;
• event.blanket_coverage_default.armed;
• future_route.rao_zhun_recovery_pending.

Suggested tags:

• exclusion_rider
• coverage_scope
• claims_adjuster
• liability_underwriting
• false_blanket_cover
• excluded_claimant
• route_asset
• recruitable
• missable
• hostile

Suggested stats:

• coverage_legibility: low when he is absent, medium after a named rider, high only as a scoped route asset;
• capture_risk: high under Orion Breath or Shen Luo pressure;
• lawful_nerve: medium with Han Yanshuang cover, low without handler support;
• public_tolerance: low if the rider hides a fan, witness, artist, or public receipt claimant;
• route_memory: high for covered and excluded claim pairs, low for emotional intent.

Entry hooks

饶准 appears from state pressure only.

Valid hooks:

1. a stabilized, scoped, callback-bearing, underwritten, or carried version asks to travel into a future route;
2. a guarantee exists or is explicitly absent;
3. at least two claimants disagree about whether the guarantee covers them;
4. a sponsor, lawful reader, archive desk, public table, editor, route asset, fan oxygen table, witness, or producer desk can benefit from a narrow rider;
5. his state is unseen, visible, protected, recruited, retained, captured, suppressed, hostile, missed, or explicit absence.

He must not appear from fixed turn count, fixed day/week timing, chapter quota, raw content count, dashboard state, or lens-health state.

Disposition states

Visible adjuster

饶准 is visible when the game can name covered claim, excluded claim, rider reader, source guarantee, and default if no rider is written.

Observable deltas:

• coverage_legibility may rise;
• excluded_claimant_hostility usually rises;
• blanket_coverage_false falls only if the excluded claim is named;
• at least two reader states must diverge.

Protected adjuster

The player protects him before sponsor, law, production, archive, public, or editor pressure consumes his draft.

rao_zhun_state_after: protected
relief_any:
  - coverage_legibility_up
  - false_blanket_cover_down
  - rider_draft_available
cost_any:
  - handler_burden_up
  - sponsor_pressure_up
  - inspection_heat_up
  - excluded_claimant_hostility_up
future_effect_any:
  - recruit_window_open
  - scoped_coverage_route_available

Recruited state

饶准 can be recruited only through choice 6, recruit_or_protect_adjuster, after a rider has named both covered and excluded claims and the future route consumes the rider with visible cost. No other hearing choice may grant or retain his route asset.

rao_zhun_state_after: recruited
route_asset_unlock: route_asset.rao_zhun_exclusion_adjuster
limits:
  - can pre-read one future coverage dispute only when source guarantee and claimant split are visible
  - cannot make sponsor, lawful, public, edit, or production cover universal
  - cannot remove the excluded claimant's future challenge
relief_any:
  - coverage_scope_readable_up
  - false_blanket_cover_down
  - future_claim_cost_predictable
cost_any:
  - route_asset_pressure_up
  - payroll_leak_up
  - sponsor_retaliation_up
  - lawful_notice_burden_up

Retained branch

retained is the exact Rao Zhun state written by choice 0, narrow_rider; it is not a separate ninth choice and grants no route asset. Durable evidence must not relabel choice 6 as retention.

selected_choice: 0
selected_posture: narrow_rider
rao_zhun_state_after: retained
relief_any:
  - one_exclusion_rider_written
  - current_route_stays_open_with_scope
cost_any:
  - next_rider_costlier
  - adjuster_capture_risk_up
  - future_claimant_hearing_required
future_effect: named_claim_readback
standalone_choice_available: false
route_asset_unlock: false

Captured branch

Sponsor, producer, inspector, archive, or editor pressure makes his rider serve one institution first.

rao_zhun_state_after: captured
relief_any:
  - selected_reader_pressure_down
cost_any:
  - false_blanket_cover_up
  - excluded_claimant_hostility_up
  - public_receipt_distrust_up
future_effect_any:
  - captured_rider_challenge_armed
  - route_recovery_surcharge

Suppressed branch

Choice 7, suppress_or_blanket_default, hides, edits out, intimidates, freezes, or omits his exclusion record to keep the covered version moving.

rao_zhun_state_after: suppressed
relief_any:
  - immediate_management_pressure_down
  - sponsor_or_lawful_reader_may_accept_short_term
cost_any:
  - blanket_coverage_false_up
  - claimant_denial_distrust_up
  - future_claim_cost_up
future_effect_any:
  - blanket_coverage_default_armed
  - recovery_only
pending_flags:
  - rao_zhun.default_pending
  - event.blanket_coverage_default.armed
  - future_route.rao_zhun_recovery_pending

Hostile state

He becomes hostile through a terminal 万能承保默认 outcome if forced to sign a false universal rider, scapegoated for a denial, or handed to one claimant as proof that all claimants were covered.

rao_zhun_state_after: hostile
cost_any:
  - coverage_denial_leak_up
  - inspection_heat_up
  - sponsor_retaliation_up
  - route_asset_pressure_up
future_effect_any:
  - hostile_adjuster_testimony
  - coverage_rehearing_required
  - blocked_or_costlier_route

Missed state

If a guarantee is consumed without naming coverage scope and excluded claimant, 饶准 is missed or explicitly absent.

rao_zhun_state_after: missed | explicit_absence
emitted_or_armed_event: event.storyteller.blanket_coverage_default.v1
cost_any:
  - blanket_coverage_false_up
  - excluded_claimant_hostility_up
  - future_claim_cost_up
future_effect_any:
  - route_blocked_until_rider_review
  - recovery_only_coverage_route

Terminal default ownership

After choice 7, the default event exposes exactly four stable outcomes:

• record_sponsor_blanket_capture;
• record_lawful_exclusion_challenge;
• record_editor_scope_correction;
• record_hostile_adjuster_recovery_only.

Each clears all three pending flags. Their exact runtime states are captured, lawful_challenger, protected_recovery_witness, and hostile_missed; their exact rider scopes are sponsor_blanket, lawful_challenge, edit_correction, and recovery_only. None may create a clean universal rider or leave route_asset.rao_zhun_exclusion_adjuster active.

Claimants he can split

A valid use of 饶准 should make at least two readers disagree:

• sponsor wants commercial cover without public refund admission;
• lawful reader wants admissible annex without sponsor carve-out;
• public table wants the excluded claim named before private cover travels;
• editor wants salvage cover for a patch without source liability;
• archive wants rider escrowed before proof travels;
• fan oxygen table wants refund eligibility preserved;
• route claimant wants the rider attached to a route asset;
• production wants temporary cover without admitting future denial.

No branch may make all readers cleanly accept the same blanket guarantee.

Costs and boundaries

饶准 is never a free insurance button. Using him should cost at least one of:

• handler time;
• lawful notice burden;
• sponsor retaliation;
• public distrust;
• excluded claimant hostility;
• route asset pressure;
• archive rider escrow;
• edit debt;
• fan refund pressure;
• future claim hearing;
• payroll leak;
• hostile testimony risk.

He cannot underwrite exposure, serve maturity notice, resolve callback debt, or erase a liability ticket. He only makes the covered/excluded boundary playable.

Non-goals

• Not a generic finance NPC.
• Not a new global economy layer.
• Not a clean mitigation vendor.
• Not a fixed-turn character beat.
• Not valid if his state does not change rider scope, excluded claimant, reader table, route asset pressure, and future route effect.