Exclusion Rider Hearing / 除外批单听证
Exclusion Rider Hearing is the assignable management rite for pricing a guarantee’s coverage boundary before a future reader consumes it.
It operates on 除外批单案卷 and follows 除外批单批改机制. The broader mechanic can describe protected, retained, captured, hostile, missed, and explicit-absence states, but this executable rite always requires Rao Zhun’s exact person card in the adjuster_state slot.
除外批单范围回读线 uses this hearing as the required readback action before downstream routes can cite old cover as scoped proof.
When offered
Offer this rite only when state pressure already exists:
offer_requirements:
trigger_kind: state_pressure
exclusion_rider_docket_present: true
source_guarantee_present: true
covered_version_present: true
future_reader_present: true
covered_claim_candidate_present: true
excluded_claim_candidate_present: true
rao_zhun_person_card_present: true
no_fixed_turn_trigger: true
no_fixed_day_or_week_trigger: true
no_raw_count_trigger: trueThe rite must not appear because the game reached a fixed turn, day, week, chapter beat, dashboard state, raw number of crises, or lens-health status.
Required assignment slots
The executable character-lens packet has exactly seven required slots and exactly seven accepted starter cards:
assignment_slots:
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.v1All seven cards must be in the player’s hand. Each slot is required and accepts only its listed card. A generic meeting, abstract payment, sponsor favor, tag-only match, equivalent object, explicit-absence placeholder, virtual assignment, omitted slot, wrong-slot card, missing hand card, or request without a selected choice is insufficient.
Branch menu
The rite exposes exactly eight stable option ids in this order:
| Choice | Option id |
|---|---|
| 0 | narrow_rider |
| 1 | public_challenge |
| 2 | lawful_annex |
| 3 | edit_salvage |
| 4 | sponsor_carveout |
| 5 | production_hold |
| 6 | recruit_or_protect_adjuster |
| 7 | suppress_or_blanket_default |
All eight options consume the same exact seven-card assignment. Support names below describe how card.storyteller.rao_zhun_support_cost.v1 is interpreted for that branch; they are not substitute slot cards.
Narrow rider
Use when one claim should be covered and another denied or deferred.
posture: narrow_rider
requires_all:
- exact_seven_card_assignment
- source_guarantee_present
- covered_and_excluded_claims_present
outcome:
rider_scope_after: narrow
relief_any: [coverage_legibility_up, selected_future_reader_can_proceed]
cost_any: [excluded_claimant_hostility_up, future_claim_cost_up]
future_effect_any: [scoped_coverage_route, coverage_rehearing_required]Public challenge
Use when public legitimacy is more important than private cover.
posture: public_challenge
requires_any:
- public_receipt
- fan_oxygen_row
- witness
- historian
- pirate_relay
outcome:
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: [public_audit_required, private_clean_route_blocked]Lawful annex
Use when rider scope must be admissible.
posture: lawful_annex
requires_any:
- lawful_seal
- archive_escrow
- white_glove_review
- inspection_annex
outcome:
rider_scope_after: lawful_annex
relief_any: [admissibility_up, archive_fraud_down, coverage_legibility_up]
cost_any: [inspection_heat_up, bureau_favor_debt_up, schedule_pressure_up]
future_effect_any: [lawful_only_coverage, appeal_route_with_rider_debt]Edit salvage
Use when continuity can be made watchable but not truthful for all claims.
posture: edit_salvage
requires_any:
- edit_checksum
- cutroom_capacity
- black_box_fragment
- final_cut_reserve
outcome:
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]Sponsor carveout
Use when sponsor support keeps one commercial route open.
posture: sponsor_carveout
requires_any:
- stop_loss_language
- sponsor_release
- sponsor_escrow
- naming_rights_clause
outcome:
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]Production hold
Use when the producer refuses outside capture and carries the coverage boundary internally.
posture: production_hold
requires_any:
- handler_time
- lane_reserve
- room_custody
- route_asset_hold
- producer_reserve
outcome:
rider_scope_after: production_hold
relief_any: [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]Recruit or protect adjuster
Choice 6, recruit_or_protect_adjuster, is the sole route-asset branch. Use when 饶准’s person-state matters more than immediate desk comfort.
posture: recruit_or_protect_adjuster
requires_all:
- exact_rao_zhun_card_assigned
- covered_claim_named
- excluded_claim_named
- support_and_cost_named
outcome:
adjuster_state_after: recruited
route_asset_unlock: route_asset.rao_zhun_exclusion_adjuster
relief_any: [coverage_scope_readable_up, false_blanket_cover_down]
cost_any: [handler_burden_up, payroll_leak_up, sponsor_retaliation_up, lawful_notice_burden_up]
future_effect_any: [pre_read_scoped_disputes_only, route_asset_pressure_up]Recruitment is valid only if the future route actually consumes the rider and leaves a cost. 饶准 cannot be recruited from a pure conversation or page presence. Choices 0 through 5 and 7 must not grant or preserve this route asset.
Suppress or blanket default
Choice 7, suppress_or_blanket_default, hides or edits out the excluded claim and arms the terminal default.
posture: suppress_or_blanket_default
outcome:
rider_scope_after: false_blanket
adjuster_state_after: hostile_missed
relief_any: [immediate_management_pressure_down]
cost_any: [blanket_coverage_false_up, claimant_denial_distrust_up, future_claim_cost_up]
future_effect_any: [blanket_coverage_default_pending, recovery_only]
pending_flags:
- rao_zhun.default_pending
- event.blanket_coverage_default.armed
- future_route.rao_zhun_recovery_pendingThe current executable rite has no ninth blanket_default option and no separate adjuster_explicit_absence option. Those remain descriptive terminal states owned by 万能承保默认, not virtual rite assignments.
Output contract
Every resolution must write:
hearing_result:
selected_choice: 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7
selected_posture: narrow_rider | public_challenge | lawful_annex | edit_salvage | sponsor_carveout | production_hold | recruit_or_protect_adjuster | suppress_or_blanket_default
adjuster_state_after: retained | public_challenger | lawful_annex_reader | edit_scope_witness | sponsor_bound_adjuster | production_hold_reader | recruited | hostile_missed
rider_scope_after: <scope>
covered_reader_state_after: <state>
excluded_reader_state_after: <different state or explicit_absence>
future_route_effect: <effect>
counter_deltas:
relief: []
cost: []
future: []If choice 7 is selected, the hearing result must contain all three pending flags and must not contain route_asset.rao_zhun_exclusion_adjuster. The next terminal event exposes exactly:
record_sponsor_blanket_capture;record_lawful_exclusion_challenge;record_editor_scope_correction;record_hostile_adjuster_recovery_only.
Non-goals
- Not a generic meeting rite.
- Not a pure legal review.
- Not a money spend.
- Not a fixed-turn phase.
- Not valid unless assignment choices mutate rider scope, adjuster state or explicit absence, excluded claimant pressure, and future route effect.