Rao Zhun Exclusion Adjuster / 饶准除外批改员线

Rao Zhun Exclusion Adjuster is a character storyline for the claims-desk person who prevents liability cover from turning into universal clean permission.

The current mesh already handles major upstream pressure:

派系责任承保 asks who guarantees an exposure;
稳定化责任交接线 asks who carries a saved version into the next desk;
播出合约回读线 asks whether old contract scope travels;
回叫消费证明线 asks whether relief travels with callback memory.

The remaining playable gap is narrower and important: after a guarantee exists, a later reader can still misread it as blanket cover. This storyline makes the denial boundary visible through Exclusion Adjuster, 除外批单批改机制, 除外批单案卷, 除外批单听证, and 万能承保默认.

Primary playable question

A covered version wants to travel into a future route. Does 饶准 write a narrow rider, expose the exclusion publicly, codify it lawfully, salvage it through edit scope, carve out sponsor cover, carry it internally, become recruitable, get captured, turn hostile, or get missed so a desk files false blanket coverage first?

Every answer keeps one reader legible and makes another reader worse.

Why this is the next useful expansion

Without this character line, workers can satisfy the underwriting and handoff surfaces while still letting cover_posted, accepted_with_callback, accepted_with_scope, lawful_only, sponsor_only, or production_carry behave like universal acceptance later.

饶准 adds the missing RPG pressure:

the person who can read the exclusion can be protected, recruited, retained, captured, suppressed, missed, or made hostile;
covered and excluded claimants must both be named;
sponsor, lawful, public, edit, archive, fan, production, and route-asset readers cannot all accept the same rider cleanly;
failure creates a default narrator instead of hidden debt.

This deepens management play rather than adding raw lens count.

State-triggered entry

Open this storyline only when live state pressure exists:

entry_state:
  trigger_kind: state_pressure
  source_guarantee_or_explicit_absence_present: true
  source_surface_present: true
  covered_version_or_route_promise_present: true
  future_reader_request_present: true
  covered_claim_candidate_present: true
  excluded_claim_candidate_or_explicit_absence_present: true
  adjuster_state_or_explicit_absence_present: true
  default_if_unworked_present: true
  player_can_narrow_challenge_annex_salvage_carveout_hold_recruit_suppress_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Valid source surfaces include liability underwriting, stabilization liability handoff, broadcast contract readback, callback consumption, recovery inventory triage, broadcast reality drift correction, sponsor makegood, public receipt bond, lawful seal, edit reserve, production carry, or route asset custody.

Content pack

Character

Exclusion Adjuster — claim-desk adjuster who can become a narrow route asset or hostile witness.

Mechanic

除外批单批改机制 — defines rider scope, source guarantee, future reader, covered claim, excluded claim, adjuster state, default, counters, and replay evidence.

Card

除外批单案卷 anchors an exact seven-card starter packet. The other six cards name the source guarantee, future reader, covered claim, excluded claim, Rao Zhun person-state, and support/cost. Together they record source scope, claimant split, selected rider posture, default pressure, and future route effect.

Rite

除外批单听证 — assignable management action for narrow rider, public challenge, lawful annex, edit salvage, sponsor carveout, production hold, adjuster route, suppression, or default.

Event

万能承保默认 — fires or arms when a guarantee is consumed as universal cover without rider scope and excluded claimant.

Storyline spine

Beat 1 — Covered version asks to travel

A previous surface produced relief or cover. A route, slot, proof object, public version, annex, callback row, sponsor package, edit patch, or route asset now asks a future reader to accept it.

The game must not ask only whether cover exists. It must ask what claim the cover excludes.

Beat 2 — Docket names covered and excluded claims

Create or update 除外批单案卷.

The docket must name:

source surface;
source guarantee or explicit absence;
covered version;
future reader;
covered claim;
excluded claim or explicit absence;
excluded claimant or explicit absence;
饶准 state or explicit absence;
rider scope before and after;
default if unworked;
future route effect.

The executable packet is exact:

Slot	Required starter 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 must be in hand and assigned to their matching required slots. Generic tags, virtual cards, explicit-absence substitutes, wrong-slot cards, missing hand cards, omitted slots, and a missing branch choice are rejected.

Beat 3 — Adjuster appears as person-state, not flavor

饶准 may enter as visible, protected, retained, recruitable, captured, suppressed, hostile, missed, or explicit absence.

The player must decide whether to spend support on his rider or let a desk file first.

Beat 4 — Hearing prices the rider

Run 除外批单听证.

The player chooses one branch:

choice 0 — narrow_rider;
choice 1 — public_challenge;
choice 2 — lawful_annex;
choice 3 — edit_salvage;
choice 4 — sponsor_carveout;
choice 5 — production_hold;
choice 6 — recruit_or_protect_adjuster;
choice 7 — suppress_or_blanket_default.

Every branch writes a rider scope, 饶准 state or explicit absence, covered reader state, excluded reader state, future route effect, and counter deltas.

Only choice 6 grants route_asset.rao_zhun_exclusion_adjuster. Choice 7 grants no route asset and arms exactly rao_zhun.default_pending, event.blanket_coverage_default.armed, and future_route.rao_zhun_recovery_pending.

Beat 5 — Future route consumes rider state

The line is complete only when at least one future route, proof, route asset, slot, public statement, lawful annex, sponsor package, edit patch, callback row, or recovery path reads the rider.

A clean universal accept state is invalid.

Branch map

Choice and branch	Immediate relief	Cost/scar	Future state
`0 narrow_rider`	selected reader proceeds	excluded claimant hostility/future claim cost	scoped coverage route or rehearing
`1 public_challenge`	false blanket cover drops	sponsor/witness/fan pressure rises	public audit or private route block
`2 lawful_annex`	admissibility and archive clarity improve	inspection heat and bureau debt rise	lawful-only coverage or appeal debt
`3 edit_salvage`	slot legibility improves	edit debt/source ambiguity/fraud cost rises	later source challenge costlier
`4 sponsor_carveout`	sponsor or slot pressure drops	public distrust/fan resentment/capture rises	sponsor-only coverage
`5 production_hold`	route control improves	handler fatigue/lane scar/route pressure rises	production triage armed
`6 recruit_or_protect_adjuster`	coverage scope becomes readable	payroll/support/retaliation pressure rises	sole bounded route-asset unlock
`7 suppress_or_blanket_default`	short-term desk pressure may fall	false blanket cover and denial distrust rise	exact default pending triple

Recruit / miss / hostile branch rules

Recruit 饶准

This is the sole executable route-asset branch and is selected only by choice 6, recruit_or_protect_adjuster. It is valid only when:

recruit_entry:
  adjuster_visible_or_protected: true
  source_guarantee_present_or_explicit_absence: true
  covered_claim_named: true
  excluded_claim_or_explicit_absence_named: true
  future_route_consumes_rider_with_cost: true
  no_clean_universal_coverage: true

Outcome:

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 universalize cover
  - cannot erase excluded claimant challenge
counter_deltas:
  relief: [coverage_scope_readable_up, false_blanket_cover_down]
  cost: [route_asset_pressure_up, sponsor_retaliation_up]
  future: [future_claim_cost_predictable]

Retain 饶准

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. Current durable route-asset evidence must not claim retention when choice 6 actually recruits Rao Zhun.

selected_choice: 0
selected_posture: narrow_rider
rao_zhun_state_after: retained
relief: one_exclusion_rider_written
cost: next_rider_costlier | adjuster_capture_risk_up | handler_burden_up
future: named_claim_readback
standalone_choice_available: false
route_asset_unlock: false

Capture 饶准

Valid when sponsor, management, lawful, archive, editor, or production files his rider first.

rao_zhun_state_after: captured
relief: selected_reader_pressure_down
cost: false_blanket_cover_up | excluded_claimant_hostility_up | public_receipt_distrust_up
future: captured_rider_challenge_armed | route_recovery_surcharge

Suppress 饶准

Valid when choice 7, suppress_or_blanket_default, hides, edits out, intimidates, freezes, or omits his exclusion record.

rao_zhun_state_after: suppressed
relief: immediate_management_pressure_down
cost: blanket_coverage_false_up | claimant_denial_distrust_up | future_claim_cost_up
future: blanket_coverage_default_armed | recovery_only
pending_flags:
  - rao_zhun.default_pending
  - event.blanket_coverage_default.armed
  - future_route.rao_zhun_recovery_pending

Hostile 饶准

Valid as a terminal default outcome when he is forced to sign false universal cover, blamed for denial, or left unprotected after exposure.

rao_zhun_state_after: hostile
cost: coverage_denial_leak_up | inspection_heat_up | sponsor_retaliation_up | route_asset_pressure_up
future: hostile_adjuster_testimony | coverage_rehearing_required | blocked_or_costlier_route

Miss 饶准

Valid when choice 7 lets cover travel without naming rider scope, excluded claim, and adjuster state, then the terminal event records the miss or recovery-only scar.

rao_zhun_state_after: missed | explicit_absence
event_seen_or_armed: event.storyteller.blanket_coverage_default.v1
cost: blanket_coverage_false_up | excluded_claimant_hostility_up | future_claim_cost_up
future: route_blocked_until_rider_review | recovery_only_coverage_route

Four terminal default outcomes

After choice 7, 万能承保默认 exposes exactly four stable terminal options:

Event option	Terminal ownership	Future route
`record_sponsor_blanket_capture`	`captured` with `sponsor_blanket` scope	`sponsor_correction_required`
`record_lawful_exclusion_challenge`	`lawful_challenger` with `lawful_challenge` scope	`lawful_rehearing_required`
`record_editor_scope_correction`	`protected_recovery_witness` with `edit_correction` scope	`scope_correction_required`
`record_hostile_adjuster_recovery_only`	`hostile_missed` with `recovery_only` scope	`recovery_only`

Each option clears rao_zhun.default_pending, event.blanket_coverage_default.armed, and future_route.rao_zhun_recovery_pending. There is no fifth flavor outcome and no terminal clean universal cover.

Counter contract

Every branch must mutate at least three surfaces:

one relief surface;
one cost or excluded-claimant surface;
one future route, slot, proof, route asset, or custody surface.

Primary counters:

coverage_legibility
blanket_coverage_false
exclusion_pressure
excluded_claimant_hostility
claimant_denial_distrust
future_claim_cost
sponsor_stop_loss_pressure
contract_capture
inspection_heat
bureau_favor_debt
public_receipt_legitimacy
public_receipt_distrust
fan_refund_pressure
fan_oxygen_resentment
edit_debt
source_ambiguity
future_fraud_cost
handler_fatigue
lane_scar
black_screen_slots
route_asset_pressure

Integration notes

With 派系责任承保, a posted cover becomes rider input, not blanket closure.
With 稳定化责任交接线, the named carrier can receive rider scope or be denied coverage.
With 播出合约回读线, accepted-with-scope can still exclude the old harmed reader.
With 回叫消费证明线, callback-bearing relief can be covered for one future reader while another remains owed.
With 复原库存分诊线, finite recovery rows can be covered for sponsor makegood while public contrition, ward, archive, or fan oxygen demands remain excluded.
With Route Assets and Custody, 饶准 can become a route asset only as a scoped reader, not as a universal insurance button.

Missability and recovery

The storyline is missed if implementation:

records a guarantee but not rider scope;
records covered claim but not excluded claim or explicit absence;
hides 饶准 state or explicit absence;
lets one sponsor, lawful, public, edit, archive, or production cover satisfy all readers;
opens from fixed turn, day, week, raw count, dashboard state, or lens health;
ends without a future route consuming rider state.

Recovery is allowed only through visible scar:

rider rehearing;
public addendum;
lawful annex;
sponsor carveout unwind;
edit proof release;
fan refund audit;
excluded claimant settlement;
route asset surcharge;
protect/recruit 饶准 after harm;
recovery-only coverage route.

Replay evidence shape

storyline_id: storyteller.storyline.character_rao_zhun_exclusion_adjuster.v1
session_id: lens-storyteller-lens-character-rao-zhun-exclusion-adjuster-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_guarantee_or_explicit_absence_present: true
  source_surface_present: true
  covered_version_or_route_promise_present: true
  future_reader_request_present: true
  covered_claim_candidate_present: true
  excluded_claim_candidate_or_explicit_absence_present: true
  adjuster_state_or_explicit_absence_present: true
  no_fixed_turn_trigger: true
active_objects:
  character: storyteller.character.rao_zhun_exclusion_adjuster.v1
  mechanic: storyteller.mechanic.exclusion_rider_adjustment.v1
  starter_cards:
    - card.storyteller.exclusion_rider_docket.v1
    - card.storyteller.rao_zhun_source_guarantee.v1
    - card.storyteller.rao_zhun_future_reader.v1
    - card.storyteller.rao_zhun_covered_claim.v1
    - card.storyteller.rao_zhun_excluded_claim.v1
    - card.storyteller.rao_zhun_exclusion_adjuster.v1
    - card.storyteller.rao_zhun_support_cost.v1
  rite: rite.storyteller.exclusion_rider_hearing.v1
offered_choices:
  - narrow_rider
  - public_challenge
  - lawful_annex
  - edit_salvage
  - sponsor_carveout
  - production_hold
  - recruit_or_protect_adjuster
  - suppress_or_blanket_default
branch_runs:
  scoped_branch:
    selected_posture: narrow_rider | public_challenge | lawful_annex | edit_salvage | sponsor_carveout | production_hold
    rider_scope_after: <scope>
    rao_zhun_state_after: <state_or_explicit_absence>
    covered_reader_state_after: <state>
    excluded_reader_state_after: <different state or explicit_absence>
    future_route_effect: <effect>
    counter_deltas:
      relief: []
      cost: []
      future: []
  recruit_branch:
    choice: 6
    selected_posture: recruit_or_protect_adjuster
    prerequisites_met: true
    route_asset_unlock: route_asset.rao_zhun_exclusion_adjuster
    future_route_effect: scoped_coverage_route_available
    counter_deltas:
      relief: [coverage_scope_readable_up]
      cost: [route_asset_pressure_up]
      future: [future_claim_cost_predictable]
  default_branch:
    choice: 7
    selected_posture: suppress_or_blanket_default
    pending_flags:
      - rao_zhun.default_pending
      - event.blanket_coverage_default.armed
      - future_route.rao_zhun_recovery_pending
    event_seen_or_armed: event.storyteller.blanket_coverage_default.v1
    terminal_option: record_sponsor_blanket_capture | record_lawful_exclusion_challenge | record_editor_scope_correction | record_hostile_adjuster_recovery_only
    filing_actor: <actor>
    false_blanket_claim: <claim>
    excluded_claimant: <reader or explicit_absence>
    rao_zhun_state_after: captured | lawful_challenger | protected_recovery_witness | hostile_missed
    rider_scope_after: sponsor_blanket | lawful_challenge | edit_correction | recovery_only
    future_route_effect: sponsor_correction_required | lawful_rehearing_required | scope_correction_required | recovery_only
assertions:
  - entry_is_state_pressure
  - source_guarantee_is_not_blanket
  - covered_and_excluded_claims_named_or_explicit_absence
  - adjuster_state_or_explicit_absence_visible
  - branch_outcomes_diverge
  - recruit_miss_hostile_states_are_playable
  - success_has_cost
  - blanket_default_is_durable
  - future_route_consumes_rider_state
  - no_fixed_turn_trigger

The durable replay pair is fixed:

lens/replays/rao-zhun-exclusion-adjuster.recruit.replay.json;
lens/replays/rao-zhun-exclusion-adjuster.hostile-default.replay.json.

The recruit replay must select choice 6. The hostile-default replay must select choice 7, resolve one of the four terminal event options, clear the entire pending triple, and finish without route_asset.rao_zhun_exclusion_adjuster.

Non-goals

Not filler recruitable NPC content.
Not a generic finance story.
Not a new economy layer.
Not a clean mitigation button.
Not a fixed sequence chapter.
Not a replacement for underwriting, handoff, readback, callback, recovery inventory, or drift audit.
Not valid if a guarantee can be consumed later without coverage scope, excluded claimant, adjuster state, and future route effect.

Storyteller Wiki

Explorer

Rao Zhun Exclusion Adjuster / 饶准除外批改员线

Rao Zhun Exclusion Adjuster / 饶准除外批改员线

Primary playable question

Why this is the next useful expansion

State-triggered entry

Content pack

Character

Mechanic

Card

Rite

Event

Storyline spine

Beat 1 — Covered version asks to travel

Beat 2 — Docket names covered and excluded claims

Beat 3 — Adjuster appears as person-state, not flavor

Beat 4 — Hearing prices the rider

Beat 5 — Future route consumes rider state

Branch map

Recruit / miss / hostile branch rules

Recruit 饶准

Retain 饶准

Capture 饶准

Suppress 饶准

Hostile 饶准

Miss 饶准

Four terminal default outcomes

Counter contract

Integration notes

Missability and recovery

Replay evidence shape

Non-goals

Graph View

Table of Contents

Backlinks