Blanket Coverage Default / 万能承保默认

Blanket Coverage Default is the failure/default event for 除外批单批改机制.

It is the durable failure surface for 除外批单范围回读线 when a future reader consumes a guarantee without source scope, excluded claimant, support proof or explicit absence, and future route effect.

It fires or arms when a guarantee, rider, callback, readback, cover, handoff, public bond, lawful seal, sponsor escrow, edit reserve, or production carry is consumed as if it covered every reader.

Event promise

The event must name who filed the false blanket cover, which claim was treated as covered, which claim or claimant was excluded, and how the future route mutates.

It is not enough to say that liability increased. The player must see which denied reader now owns the default.

Trigger conditions

The executable event triggers only after choice 7, suppress_or_blanket_default, has armed all three pending flags:

trigger_state:
  trigger_kind: state_pressure
  rao_zhun.default_pending: true
  event.blanket_coverage_default.armed: true
  future_route.rao_zhun_recovery_pending: true
  event_resolved.event.storyteller.blanket_coverage_default.v1: false

Removing or falsifying any one pending flag makes the event ineligible. The event is not a random generic liability event and cannot be satisfied by a lone armed marker.

Required event payload

wiki_id: storyteller.event.blanket_coverage_default.v1
event_id: storyteller.event.blanket_coverage_default.v1
game_id: event.storyteller.blanket_coverage_default.v1
source_surface: <underwriting | handoff | readback | callback | recovery_inventory | drift | equivalent>
source_row_id: <stable row or explicit_absence>
filing_actor: sponsor | lawful_reader | archive | public_table | editor | production | route_claimant | management | explicit_absence | equivalent
false_blanket_claim: <claim treated as universal>
covered_reader: <reader>
excluded_claim: <claim or explicit_absence>
excluded_claimant: <reader or explicit_absence>
adjuster_state: captured | suppressed | hostile | missed | explicit_absence | equivalent
reason_defaulted: rider_missing | scope_hidden | excluded_claim_hidden | adjuster_unavailable | sponsor_filed_first | lawful_filed_first | production_suppressed | edit_salvaged_as_truth | equivalent
future_route_effect: blocked | hostile | captured | costlier | public_only | lawful_only | sponsor_only | recovery_only | rider_rehearing_required | equivalent
counter_deltas:
  blanket_coverage_false: +1
  excluded_claimant_hostility: +1
  future_claim_cost: +1

Additional deltas should reflect the filing actor, such as sponsor pressure falling while public distrust rises, lawful clarity rising while bureau debt rises, or edit continuity improving while source ambiguity rises.

Default narrators

The event should assign one narrator that now owns the omission:

• sponsor_denial_narrator: sponsor files commercial cover and denies public/fan scope;
• lawful_denial_narrator: lawful annex accepts one claim and excludes public/sponsor/fan claim;
• archive_escrow_narrator: archive accepts proof but hides future reader exclusion;
• editor_salvage_narrator: cutroom cover becomes truth while source liability is denied;
• production_hold_narrator: producer keeps route moving and leaves claimant outside the hold;
• public_counter_narrator: public table exposes the false blanket cover;
• hostile_adjuster_narrator: 饶准 or equivalent adjuster testifies that the rider was forced or erased;
• excluded_claimant_narrator: the denied reader reopens the claim.

Four terminal outcomes

The executable event exposes exactly four stable option ids. Every option clears:

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

Every option also records a terminal Rao Zhun state, rider scope, excluded reader, future route, relief/cost split, and durable counter movement.

record_sponsor_blanket_capture

Sponsor owns the false blanket filing. Immediate commercial pressure may fall, but Rao Zhun becomes captured, the excluded claimant remains callable, and the route requires sponsor correction.

option_id: record_sponsor_blanket_capture
outcome_flag: rao_zhun.default_outcome.sponsor_blanket_capture
filing_actor: sponsor
rao_zhun_state_after: captured
rider_scope_after: sponsor_blanket
future_route_effect: sponsor_correction_required

record_lawful_exclusion_challenge

The lawful or archive reader preserves the exclusion as a challenge instead of universalizing the guarantee. Admissibility or legibility may improve, but inspection debt, appeal pressure, and excluded-claimant hostility remain.

option_id: record_lawful_exclusion_challenge
outcome_flag: rao_zhun.default_outcome.lawful_exclusion_challenge
filing_actor: lawful_reader | archive
rao_zhun_state_after: lawful_challenger
rider_scope_after: lawful_challenge
future_route_effect: lawful_rehearing_required

record_editor_scope_correction

The editor publishes a scoped correction. Continuity may recover, but source ambiguity, edit debt, correction cost, and later challenge remain visible. This option does not convert edit salvage into universal cover.

option_id: record_editor_scope_correction
outcome_flag: rao_zhun.default_outcome.editor_scope_correction
filing_actor: editor
rao_zhun_state_after: protected_recovery_witness
rider_scope_after: edit_correction
future_route_effect: scope_correction_required

record_hostile_adjuster_recovery_only

Rao Zhun owns the forced or erased rider as hostile testimony, or the route records him as missed and recovery-only. The route asset is absent and future play is blocked, hostile, or recovery-only until a scar-bearing rider review.

option_id: record_hostile_adjuster_recovery_only
outcome_flag: rao_zhun.default_outcome.hostile_adjuster_recovery_only
filing_actor: hostile_adjuster | management | explicit_absence
rao_zhun_state_after: hostile_missed
rider_scope_after: recovery_only
future_route_effect: recovery_only

All four options also set event_resolved.event.storyteller.blanket_coverage_default.v1. No fifth flavor option, missing choice, implicit acknowledgement, or clean universal repair satisfies this event.

Recovery hooks

Recovery from this event is allowed only through a visible scar:

• run a rider rehearing;
• publish a public addendum;
• create a lawful annex;
• unwind sponsor carveout;
• pay fan refund audit;
• release edit proof;
• protect or recruit the adjuster after harm;
• settle or name the excluded claimant;
• convert the route to recovery-only.

Non-goals

• Not a generic lawsuit event.
• Not a flavor backlash.
• Not a fixed upkeep timer.
• Not a clean penalty payment.
• Not valid unless it names filing actor, false blanket claim, excluded claim/claimant or explicit absence, adjuster state, and future route effect.