False Stale Dispatch Afteruse Default

False Stale Dispatch Afteruse Default fires or arms when a later reader treats a partial recall, scoped acknowledgement, stale-execution scar, or recovery-only dispatch row as clean universal service.

It is not the same as Stale Dispatch Execution. The old instruction may already have been recalled or visibly scarred. This event records that its later afteruse exceeded the source scope.

Fire Condition

fire_condition:
  trigger_kind: state_pressure
  source_docket: storyteller.card.stale_dispatch_afteruse_docket.v1 | explicit_absence
  source_recall_row_or_absence: <recall row or explicit_absence>
  future_reader_attempts_afteruse: true
  hidden_or_overbroad_dispatch_scope_present: true
  harmed_or_excluded_reader_hidden_or_unanswered: true
  false_clean_dispatch_afteruse_claimed: true
  no_fixed_turn_trigger: true

The event must not fire because a fixed number of turns passed. It appears when a sponsor gate, lawful reader, archive, public table, cutroom, ward desk, management report, route asset, ending gate, or broadcast reality consumes an old recall row beyond its scope.

Required Payload

false_stale_dispatch_afteruse_default:
  event_id: storyteller.event.false_stale_dispatch_afteruse_default.v1
  source_docket: storyteller.card.stale_dispatch_afteruse_docket.v1 | explicit_absence
  false_clean_dispatch_afteruse: true
  source_recall_row_or_absence: <recall row or explicit_absence>
  hidden_or_overbroad_dispatch_scope: acknowledged_scope | partial_recall | split_recall | runner_only_ack | public_addendum_only | lawful_notice_only | sponsor_retraction_only | cutroom_checksum_required | stale_executed | recovery_only | explicit_absence
  requested_afteruse: route_unlock | sponsor_package | lawful_annex | public_table | archive_release | cutroom_checksum | ward_service | management_report | ending_gate | equivalent
  capturing_reader_or_route: sponsor | lawful_reader | archive | public_table | cutroom | ward | management_report | route_asset | ending | equivalent
  harmed_or_excluded_reader: public_reader | lawful_reader | sponsor | archive | runner | holder | route_asset_holder | witness | ward | explicit_absence
  dispatch_afteruse_state_after: false_clean_afteruse | reader_restricted | bridge_required | capture_unwound | reissue_required | quarantined | captured | recovery_only
  future_reader_effect: acknowledgement_receipt_required | reader_restriction_due | bridge_or_addendum_due | capture_unwind_due | fresh_dispatch_required | checksum_due | blocked | hostile | recovery_only
  counter_deltas_min: 3
  durable_mutation: true

Consequence Families

Universal service claim

The later desk cites the old recall as if it worked for every reader.

Expected result: false_clean_afteruse, future reader acceptance becomes blocked, costlier, or recovery-only.

Reader overread

The first acknowledgement surface captures the row and excludes another reader.

Expected result: reader_restricted or captured, with bridge, addendum, or reader restriction required.

Stale execution laundering

The cutroom, public table, route asset, or management report treats a stale-execution scar as neutral proof.

Expected result: bridge_required, fresh_dispatch_required, checksum_due, or recovery_only, with proof burden, edit debt, or public distrust rising.

Counter Contract

The event must mutate at least three durable surfaces, including one future reader effect:

counter_deltas:
  relief:
    - immediate_pressure_down
    - route_temporarily_unblocked
  cost:
    - false_clean_service_up
    - harmed_reader_hostility_up
    - proof_burden_up
    - public_distrust_up
    - edit_debt_up
    - runner_risk_up
    - sponsor_unwind_cost_up
  future:
    - acknowledgement_receipt_required
    - bridge_or_addendum_due
    - fresh_dispatch_required
    - future_reader_acceptance_blocked
    - recovery_route_required

Recovery Hooks

Recovery requires visible scar:

• reopen Stale Dispatch Afteruse Review;
• attach a lawful annex, public addendum, checksum, route tag, or runner receipt;
• unwind stale-execution or first-reader capture;
• reissue the current dispatch;
• quarantine the afteruse claim;
• route the result through recovery-only play.

Non-Goals

• Not a first stale-dispatch failure.
• Not a fixed-turn timeout.
• Not a clean retcon.
• Not valid unless it names source recall row, overbroad scope, capturing reader, harmed reader, after-state, and future effect.