Exclusion Rider Adjustment / 除外批单批改机制

Exclusion Rider Adjustment is the mechanism for the moment after liability has been underwritten, handed off, carried, or accepted with callback/scope, when a later reader asks whether that cover applies to a specific claim.

The mechanism prevents a posted guarantee from becoming blanket permission. A guarantee can keep a route alive, but it must name what it covers, what it excludes, who can read the rider, and what happens when an excluded claimant calls the gap.

This mechanism is person-facing through Exclusion Adjuster. The broader mechanism can record explicit absence if he is missed, captured, suppressed, or unavailable; Rao Zhun’s current executable character route instead requires his exact person card and records miss/hostility through choice 7 plus the terminal default event.

The top-level system wrapper is 除外批单范围回读线. Rao Zhun’s character route proves the worker state; the scope-readback storyline proves that any future reader consuming cover must see source row, covered and excluded claims, adjuster state or explicit absence, rider scope, and future route effect.

Primary playable question

A covered version wants to travel. Does the player narrow the rider, challenge the exclusion publicly, codify it lawfully, salvage it through edit scope, accept a sponsor carveout, impose a production hold, recruit/protect the adjuster, or suppress him into blanket default?

Every answer must make at least two readers diverge.

Bound runtime profile

The mechanism remains broader than one character, but Rao Zhun’s current executable character route is fixed:

• seven exact source: storyteller starter cards;
• seven exact required slots: docket, source_guarantee, future_reader, covered_claim, excluded_claim, adjuster_state, and support_and_cost;
• eight stable hearing choices in order: narrow_rider, public_challenge, lawful_annex, edit_salvage, sponsor_carveout, production_hold, recruit_or_protect_adjuster, suppress_or_blanket_default;
• only choice 6 grants route_asset.rao_zhun_exclusion_adjuster;
• choice 7 arms rao_zhun.default_pending, event.blanket_coverage_default.armed, and future_route.rao_zhun_recovery_pending;
• exactly four terminal default outcomes clear all three flags.

The exact starter card ids are:

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

The runtime rejects substitutions, tag-only matches, virtual assignments, explicit-absence placeholders, missing cards, wrong-slot assignments, omitted slots, and resolution without a selected choice. Explicit absence remains a possible durable default state, not a substitute starter card.

State contract

Open only from live state pressure:

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
  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:

• 派系责任承保;
• 稳定化责任交接线;
• 播出合约回读线;
• 回叫消费证明线;
• 复原库存分诊线;
• broadcast reality drift correction, sponsor makegood, edit salvage, public receipt bond, lawful seal, production carry, fan oxygen bridge, or route asset custody.

Required state fields

A rider adjustment must record:

rider_state:
  source_surface: <underwriting | handoff | readback | callback | recovery_inventory | drift | equivalent>
  source_row_id: <stable row or explicit_absence>
  source_guarantee_state: <cover_posted | cover_split | cover_absent | cover_called | cover_fraud_flagged | equivalent>
  covered_version: <route promise or proof object>
  future_reader: <reader>
  covered_claim: <claim>
  excluded_claim: <claim or explicit_absence>
  excluded_claimant: <reader or explicit_absence>
  adjuster_state: unseen | visible | protected | recruited | retained | captured | suppressed | hostile | missed | explicit_absence
  rider_scope: none | draft | narrow | public_challenge | lawful_annex | edit_salvage | sponsor_carveout | production_hold | false_blanket
  future_route_effect: <effect>

A valid implementation must treat explicit absence as a state, not as missing data.

Branch families

A — Narrow rider

The player accepts that the guarantee covers one claim and excludes another.

rider_scope_after: narrow
relief_any:
  - selected_future_reader_can_proceed
  - coverage_legibility_up
cost_any:
  - excluded_claimant_hostility_up
  - future_claim_cost_up
future_effect_any:
  - scoped_coverage_route
  - coverage_rehearing_required

B — Public rider challenge

The player uses public receipt, fan oxygen, historian, witness, or pirate relay pressure to name the exclusion.

rider_scope_after: public_challenge
relief_any:
  - public_receipt_legitimacy_up
  - false_blanket_cover_down
cost_any:
  - sponsor_pressure_up
  - witness_exposure_up
  - fan_refund_pressure_up
future_effect_any:
  - private_clean_route_blocked
  - public_audit_required

C — Lawful annex

The player routes the rider through lawful seal, archive escrow, white-glove review, or inspection annex.

rider_scope_after: lawful_annex
relief_any:
  - admissibility_up
  - coverage_legibility_up
  - archive_fraud_down
cost_any:
  - inspection_heat_up
  - bureau_favor_debt_up
  - schedule_pressure_up
future_effect_any:
  - lawful_only_coverage
  - appeal_route_with_rider_debt

D — Edit salvage rider

The player limits cover to a cutroom patch, black-box checksum, edit reserve, or continuity salvage.

rider_scope_after: edit_salvage
relief_any:
  - continuity_hazard_down
  - slot_legibility_up
cost_any:
  - edit_debt_up
  - source_ambiguity_up
  - future_fraud_cost_up
future_effect_any:
  - later_source_challenge_costlier

E — Sponsor carveout

The player accepts sponsor-specific cover or stop-loss language.

rider_scope_after: sponsor_carveout
relief_any:
  - sponsor_stop_loss_pressure_down
  - selected_slot_pressure_down
cost_any:
  - public_receipt_distrust_up
  - fan_oxygen_resentment_up
  - contract_capture_up
future_effect_any:
  - sponsor_only_coverage
  - public_correction_costlier

F — Production hold

The player keeps cover internal through handler time, route asset custody, safe room, producer reserve, or lane scar.

rider_scope_after: production_hold
relief_any:
  - immediate_route_control_up
  - faction_capture_down
cost_any:
  - handler_fatigue_up
  - lane_scar_up
  - black_screen_slots_up
future_effect_any:
  - production_triage_armed
  - costlier_route

G — Adjuster route branch

Choice 6, recruit_or_protect_adjuster, recruits Exclusion Adjuster as the sole bounded route-asset result.

adjuster_state_after: recruited
rider_scope_after: protected_adjuster
route_asset_unlock: route_asset.rao_zhun_exclusion_adjuster
future_effect_any:
  - pre_read_one_named_scoped_dispute
  - route_asset_pressure_up

No other hearing choice may grant or retain the route asset.

H — Blanket coverage default

Choice 7, suppress_or_blanket_default, hides scope, lets a desk file first, or treats the guarantee as universal.

rider_scope_after: false_blanket
adjuster_state_after: hostile_missed
pending_flags:
  - rao_zhun.default_pending
  - event.blanket_coverage_default.armed
  - future_route.rao_zhun_recovery_pending
cost_any:
  - blanket_coverage_false_up
  - excluded_claimant_hostility_up
  - future_claim_cost_up
  - route_asset_pressure_up
future_effect: recovery_only

万能承保默认 then resolves exactly one of:

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

Every terminal option clears all three pending flags.

Their exact terminal state triples are:

Option	Rao Zhun state	Rider scope	Future route
record_sponsor_blanket_capture	captured	sponsor_blanket	sponsor_correction_required
record_lawful_exclusion_challenge	lawful_challenger	lawful_challenge	lawful_rehearing_required
record_editor_scope_correction	protected_recovery_witness	edit_correction	scope_correction_required
record_hostile_adjuster_recovery_only	hostile_missed	recovery_only	recovery_only

Counter contract

Every resolution must mutate at least three surfaces:

• one immediate relief surface;
• one named excluded-claimant or future-cost surface;
• one future route, reader, route asset, proof, slot, or custody state.

Useful counters:

• coverage_legibility
• blanket_coverage_false
• exclusion_pressure
• excluded_claimant_hostility
• 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

Failure and recovery

The mechanism is missed when implementation:

• consumes a guarantee without coverage scope;
• records covered claim but not excluded claim or explicit absence;
• lets sponsor, law, archive, public, edit, or production cover all readers for free;
• hides adjuster state;
• fails to mutate a future route reader;
• opens from fixed timing, raw count, dashboard state, or lens-health state.

Recovery is allowed only with a scar:

• rider rehearing;
• public addendum;
• lawful annex;
• sponsor carveout unwind;
• excluded claimant settlement;
• route asset surcharge;
• edit proof release;
• fan refund audit;
• hostile adjuster testimony;
• recovery-only coverage route.

Non-goals

• Not a global insurance economy.
• Not a new money sink.
• Not a clean mitigation layer.
• Not a replacement for liability underwriting or stabilization handoff.
• Not valid unless coverage scope, excluded claimant, adjuster state or explicit absence, and future route effect are visible.