Unserved Capacity Notice / 未送达容量告知

Unserved Capacity Notice is the default event for a finite broadcast capacity row that is treated as cleared, converted, borrowed, folded, or settled before the excluded claimant receives service or explicit absence is recorded.

It turns a hidden service failure into durable route state.

Fires or arms when

• a 播出容量责任账本 row has an excluded or harmed reader but no 容量告知送达案卷 row;
• a capacity row is filed as scoped_free, sponsor_captured, public_only, lawful_only, borrowed_forward, or blackout_folded without service proof or explicit absence;
• sponsor, lawful, public, archive, editor, route asset, or management desk service is asserted by implication;
• a borrowed-forward row lacks a served future claimant;
• blackout fold hides the claimant injured by the fold;
• split capacity is filed as universal notice;
• the notice carrier is captured, absent, or suppressed without cost;
• proof of service is missing without explicit absence;
• future route effect is missing.

Payload

unserved_capacity_notice_event:
  event: storyteller.event.unserved_capacity_notice.v1
  source_capacity_row:
    ledger_id: storyteller.card.broadcast_capacity_liability_ledger.v1
    capacity_row_id: <capacity row or explicit_absence>
    capacity_surface: <surface>
    capacity_state_before: <state or explicit_absence>
    attempted_capacity_state_after: <state>
    source_authority_or_absence: <authority or explicit_absence>
  service_failure:
    failure_kind: unserved | false_served | wrong_first_claimant | carrier_captured | omitted_claimant_hidden | proof_absent | split_notice_filed_universal | blackout_fold_hid_reader | clean_reuse_without_service | equivalent
    served_claimant_or_absence: <claimant or explicit_absence>
    omitted_or_deferred_claimant: <claimant or explicit_absence>
    harmed_reader: <reader or explicit_absence>
    notice_carrier_or_absence: <carrier or explicit_absence>
    proof_of_service_or_absence: <proof or explicit_absence>
    default_actor: sponsor | inspector | archive | editor | fan_public | route_claimant | blackout_system | management | handler_absence | equivalent
  false_claim:
    false_service_claim: capacity_served | sponsor_ack_clean | lawful_notice_clean | public_notice_clean | split_notice_universal | blackout_fold_clean | borrowed_forward_clean | route_asset_released | metric_clean | equivalent
  state_after:
    notice_state_after: unserved | false_served | hostile | captured | blocked | recovery_only | contradiction_pending
    capacity_state_after: defaulted | sponsor_only | public_only | lawful_only | blackout_folded | route_asset_captured | borrowed_forward_default_ready | blocked | recovery_only | contradiction_pending
    future_route_effect: blocked | hostile | costlier | public_audit_required | lawful_annex_required | sponsor_unwind_required | service_rehearing_required | recovery_only | contradiction_pending
  counter_deltas:
    relief: []
    cost: []
    future: []

Consequence contract

A valid default must mutate at least three surfaces:

• claimant or harmed reader state;
• capacity state;
• future route effect;
• plus one pressure cost such as inspection heat, sponsor capture, public distrust, fan oxygen resentment, route asset pressure, management pressure, blackout pressure, or handler burden.

The default fails if it only displays warning text, reduces money, or increments generic risk.

Recovery hooks

Recovery is allowed, but the scar remains visible:

• late lawful annex;
• late public or fan notice;
• sponsor unwind;
• route asset release hearing;
• service rehearing with carrier protection;
• blackout scar addendum;
• recovery-only branch.

A recovery branch cannot retroactively make the original capacity row universally served.