Exclusion Rider Scope Readback / 除外批单范围回读线

Exclusion Rider Scope Readback is the system-facing storyline for the moment a posted guarantee, liability handoff, callback relief, contract readback, sponsor cover, lawful seal, edit reserve, or production carry is about to be consumed by a future reader.

Rao Zhun Exclusion Adjuster proves the human route: the adjuster can be visible, protected, recruited, captured, suppressed, hostile, missed, or explicitly absent. This storyline owns the broader non-character surface. It must still work when 饶准 is unavailable, when another desk writes first, or when implementation needs to prove coverage scope without treating a person-state as the whole mechanism.

Gap diagnosis

The corpus already has a strong Exclusion Rider Adjustment mechanic, a docket, an assignable hearing, a blanket-coverage default, and Rao Zhun’s character storyline. The missing layer is the top-level readback surface between those pieces and downstream play.

Without this wrapper, a future reader can cite cover_posted, lawful_only, sponsor_only, accepted_with_scope, accepted_with_callback, production_hold, or route_asset_held as if the old rider were clean universal permission. The readback must force implementation to show which claim is covered, which claim or claimant is excluded or explicitly absent, who is trying to consume the rider, and what scar travels forward.

Primary playable question

When a future route asks to consume a guarantee, does the producer read back a narrow rider, publish a public challenge, attach a lawful annex, use edit salvage, accept sponsor carveout, carry production-only cover, record adjuster absence, or let blanket coverage default?

Every branch must name:

• source surface and source row;
• covered version or route promise;
• future reader requesting consumption;
• covered claim;
• excluded claim and excluded claimant, or explicit absence;
• adjuster state or explicit absence;
• support proof or explicit absence;
• selected scope posture;
• rider scope after;
• future route or reader effect.

State-triggered entry

Open this storyline only from live coverage-scope pressure:

entry_state_required:
  trigger_kind: state_pressure
  source_guarantee_or_explicit_absence_present: true
  source_surface_present: true
  source_row_preserved_or_explicit_absence: 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
  rider_scope_visible_or_explicit_absence: true
  adjuster_state_or_explicit_absence_present: true
  default_if_unworked_present: true
  player_can_readback_scope_or_record_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, broadcast reality drift correction, sponsor makegood, public receipt bond, lawful annex, edit reserve, production carry, route asset custody, fan oxygen bridge, or explicit absence where a source guarantee was expected.

Bound content pack

• Exclusion Rider Adjustment defines the source guarantee, coverage scope, adjuster state, branch families, counters, and default.
• Exclusion Rider Docket records the source row, covered version, future reader, covered claim, excluded claim or explicit absence, rider scope, support, default, and future route effect.
• Exclusion Rider Hearing resolves narrow, public, lawful, edit, sponsor, production, adjuster/absence, suppression, and default postures.
• Blanket Coverage Default fires or arms when a desk files the guarantee as universal cover.
• Rao Zhun Exclusion Adjuster remains the character route, not the whole system contract.

Storyline spine

Beat 1 - Future reader asks to consume old cover

A downstream route, proof object, slot, public statement, lawful annex, sponsor package, edit patch, fan oxygen bridge, callback row, recovery route, or route asset asks whether old cover can travel.

The game must not ask only whether a guarantee exists. It must ask which claim the guarantee excludes.

Beat 2 - Docket separates source, scope, and future consumption

Create or refresh Exclusion Rider Docket.

The docket must keep these locks separate:

scope_readback_locks:
  source_lock:
    source_surface: <underwriting | handoff | readback | callback | recovery_inventory | lawful_annex | sponsor_cover | production_hold | equivalent>
    source_row_id: <stable row or explicit_absence>
    source_guarantee_state: cover_posted | cover_split | cover_absent | cover_called | cover_fraud_flagged | equivalent
  consumption_lock:
    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>
  support_lock:
    adjuster_state: unseen | visible | protected | recruited | retained | captured | suppressed | hostile | missed | explicit_absence
    proof_or_support: <public_receipt | lawful_seal | edit_checksum | sponsor_contract | handler_time | route_asset | explicit_absence>
  posture_lock:
    selected_scope_posture: narrow_rider | public_challenge | lawful_annex | edit_salvage | sponsor_carveout | production_hold | adjuster_explicit_absence | suppress_rider | blanket_default
    rider_scope_after: narrow | public_challenge | lawful_annex | edit_salvage | sponsor_carveout | production_hold | false_blanket | recovery_only
  future_lock:
    future_reader_or_route: <reader or route>
    future_route_effect: scoped | public_only | lawful_only | sponsor_only | production_only | costlier | blocked | hostile | captured | recovery_only | rehearing_required

The row fails if it stores only covered: true, guarantee exists, lawful seal, sponsor paid, handled, or adjuster present.

Beat 3 - Scope readback prices the branch

Run Exclusion Rider Hearing before the future reader can cite the old guarantee as clean proof.

Valid readback postures:

• narrow_rider
• public_challenge
• lawful_annex
• edit_salvage
• sponsor_carveout
• production_hold
• adjuster_explicit_absence
• suppress_rider
• blanket_default

Each posture must include relief, cost, and future effect. No branch may make sponsor, lawful, public, edit, production, fan, archive, and route-asset readers all accept the same rider cleanly.

Beat 4 - Future play consumes scoped coverage

At least one later route, proof object, slot, public statement, lawful annex, sponsor package, edit patch, callback row, recovery route, or route asset must consume rider_scope_after and future_route_effect.

If future play cites the guarantee while the excluded claim, excluded claimant, adjuster state or explicit absence, support proof, rider scope, or future effect is hidden, Blanket Coverage Default fires or remains armed.

Branch matrix

Branch	Immediate relief	Cost/scar	Future state
Narrow rider	selected reader proceeds with legible cover	excluded claimant hostility or future claim cost rises	scoped coverage route or rehearing
Public challenge	false blanket cover drops	sponsor, witness, fan, or public pressure rises	public audit or private-clean route block
Lawful annex	admissibility and archive clarity improve	inspection heat, bureau debt, or schedule pressure rises	lawful-only coverage or appeal debt
Edit salvage	continuity or slot legibility improves	edit debt, source ambiguity, or future fraud cost rises	later source challenge costlier
Sponsor carveout	sponsor stop-loss or selected slot pressure drops	public distrust, fan resentment, or capture pressure rises	sponsor-only coverage or public correction cost
Production hold	immediate route control improves	handler fatigue, lane scar, or blackout pressure rises	production-only cover or triage armed
Adjuster explicit absence	the system can proceed without inventing person-state	rider confidence and recovery options narrow	scoped absence scar or mandatory rehearing
Suppress rider	short-term desk pressure drops	false blanket cover and denial distrust rise	default armed, hostile, or recovery-only
Blanket default	no durable relief	denied reader owns the false-blanket scar	blocked, costlier, captured, hostile, or recovery-only

Missability and recovery

This storyline is missed when a future reader consumes a guarantee without an exclusion rider docket or explicit absence record.

Missed states include:

• scope_readback_absent;
• source_row_hidden;
• covered_claim_only;
• excluded_claim_hidden;
• excluded_claimant_hidden;
• adjuster_state_hidden;
• support_proof_missing;
• future_reader_consumed_unscoped;
• blanket_coverage_default_armed;
• recovery_only_coverage.

Recovery must preserve the scar: run a rider rehearing, publish a public addendum, attach lawful annex, unwind sponsor carveout, release edit proof, settle or name the excluded claimant, protect or recruit the adjuster after harm, or convert the route to public-only, lawful-only, sponsor-only, production-only, blocked, hostile, or recovery-only use.

Non-goals

• Not a duplicate of Rao Zhun’s recruitable character route.
• Not first-order liability underwriting.
• Not a generic legal review.
• Not a money receipt.
• Not a clean mitigation layer.
• Not valid unless source row, covered and excluded claims, future reader, scope posture, support or explicit absence, and future effect are visible.