Folded Schedule Afterimage Receipt

This mechanism keeps a folded schedule from becoming invisible capacity or clean closure after the blackout has already entered the board.

folded-schedule creates the scar. Folded Schedule Afterimage Receipt starts later, when a producer-license display, route asset, sponsor desk, public bulletin, lawful annex, archive row, or broadcast-reality reader tries to cite the fold as if the schedule is simply over.

State Contract

folded_schedule_afterimage_state:
  source_folded_slot: <stable folded slot id>
  original_schedule_contract_or_absence: <contract id or explicit_absence>
  black_screen_incident: <incident id>
  occupied_license_slot: <slot id>
  afterimage_reader_or_route: <reader route package proof window or explicit_absence>
  claimed_closure_or_reuse: clean_capacity | closed_failure | public_warning | lawful_record | sponsor_release | route_reopen | blackout_inventory | equivalent
  harmed_or_displaced_reader_or_absence: <reader or explicit_absence>
  selected_afterimage_posture: certify_folded_scar_receipt | release_slot_with_afterimage | convert_to_blackout_recovery | route_afterimage_claimant | quarantine_folded_slot | publicize_folded_cost | false_clean_folded_closure_default
  slot_state_after: scoped_free | occupied_with_afterimage | public_only | lawful_only | sponsor_only | blackout_recovery | quarantined | blocked | recovery_only | equivalent
  blackout_scar_state_after: visible | receipted | converted | claimant_routed | publicized | quarantined | hidden | hardened | equivalent
  future_route_effect: <effect>
  counter_deltas: {}

The row fails if it stores only folded, blackout cleared, slot free, or failure closed.

Entry Rules

entry_state:
  trigger_kind: state_pressure
  source_folded_slot_visible: true
  black_screen_incident_visible: true
  original_schedule_contract_visible_or_explicit_absence: true
  occupied_license_slot_visible: true
  afterimage_reader_consumes_fold_state: true
  harmed_or_displaced_reader_visible_or_explicit_absence: true
  player_can_receipt_release_convert_quarantine_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_blackout_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Branch Contract

Certify Folded Scar Receipt

The fold can be cited only as scarred history. The later reader gains clarity, but the blackout incident and harmed reader remain visible.

Release Slot With Afterimage

The slot can be reopened only with a receipt that preserves the afterimage. The result is scoped-free, not clean-free.

Convert To Blackout Recovery

The fold moves into recovery play. Current pressure may drop, but a recovery route, blackout residue claim, or capacity liability remains.

Route Afterimage Claimant

The harmed or displaced reader receives a route through public notice, lawful annex, sponsor unwind, archive objection, route-asset repair, or default recovery.

Quarantine Folded Slot

Unsafe reuse is blocked until stronger receipt, proof, claimant service, or route recovery exists.

Publicize Folded Cost

The failure is made public before later readers consume it. Public legitimacy can improve, but sponsor, inspection, route, or audience pressure rises.

False Clean Folded Closure Default

If a folded slot is filed as clean capacity or closed failure while hiding incident, reader, or future effect, False Folded Schedule Closure Default fires or arms.

Counter Contract

Every branch must mutate at least three durable surfaces:

• one relief surface: folded_slot_legibility, capacity_reopen_clarity, blackout_recovery_access, or claimant_route_visibility;
• one cost surface: black_screen_pressure, public_receipt_distrust, sponsor_stop_loss_pressure, inspection_heat, archive_debt, route_asset_pressure, or handler_burden;
• one future state: accepted_with_scar, scoped_free, public_only, lawful_only, blackout_recovery, quarantined, blocked, hostile, contradiction_pending, or recovery_only.

Non-Goals

Not the first fold, not a schedule countdown, not a capacity notice service substitute, and not a free slot-release rule. This mechanism observes later afterimage reuse of an already folded schedule.