Stale Dispatch Execution / 过期派发执行

Stale Dispatch Execution is the default event for an old instruction executing after a newer boundary, ruling, redaction posture, availability state, rehearsal decision, or custody order should have superseded it.

The event is not a generic mishap. It must name the stale instruction, the actor who executed it, the reader who captured the wrong version, the harmed reader, and the route or broadcast consequence.

Event trigger

Arm or fire this event when any are true:

trigger:
  stale_dispatch_docket_present: true
  source_state_changed: true
  stale_instruction_still_actionable: true
  recall_not_acknowledged_or_explicitly_absent: true
  holder_executes_or_cites_old_instruction: true
  future_reader_or_route_affected: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true

Common triggers include: old call sheet executed, stale cut aired, sponsor preview cited as current promise, public script read after lawful narrowing, ward order moves the wrong body, runner delivers old proof tag, pirate relay broadcasts an old packet, or route asset is handed off under superseded custody.

Payload contract

event: storyteller.event.stale_dispatch_execution.v1
source_decision_or_boundary: <source id>
source_state_after: <state>
stale_instruction:
  instruction_id: <id>
  instruction_kind: call_sheet | cutroom_mark | sponsor_copy | public_script | ward_order | corridor_runner_note | pirate_relay_packet | proof_handoff | route_asset_handoff | equivalent
  issued_under_state: <old state>
  now_conflicts_with_state: <new state>
executed_by: floor_crew | editor | sponsor | inspector | archive | fan_delegate | ward | runner | pirate_relay | artist_proxy | witness_proxy | production_absence | equivalent
capturing_reader: public | lawful | sponsor | editor | ward | floor | fan_delegate | archive | route_asset | producer_license | pirate_relay | equivalent
harmed_reader_or_claimant: <reader claimant or explicit_absence>
execution_kind: wrong_body_moved | wrong_cut_aired | wrong_quote_filed | wrong_gate_opened | wrong_proof_delivered | wrong_public_promise | wrong_route_asset_handoff | equivalent
state_before: recall_open | partially_acknowledged | hidden | underfilled | equivalent
state_after: stale_executed | false_execution | captured_by_old_instruction | route_asset_misdelivered | recovered_with_scar | recovery_only
future_route_effect: blocked | captured | costlier | public_addendum_required | lawful_bridge_required | checksum_required | quarantine_required | recovery_only

The event fails as content if it only says confusion rose, reputation fell, or a memo was missed.

Branch outcomes

Stale execution hardens

The old instruction becomes the first thing a reader can cite.

Expected deltas:

relief_any:
  - immediate_assignment_burden_down
cost_any:
  - stale_dispatch_risk_up
  - harmed_reader_hostility_up
  - public_confusion_up
  - inspection_heat_up
  - route_asset_pressure_up
future_effect_any:
  - captured_by_old_instruction
  - route_blocked_until_recall
  - recovery_only

Stale execution is corrected with scar

The player later proves the old instruction was stale.

Expected deltas:

relief_any:
  - false_execution_contained
  - reader_table_scoped
  - route_asset_recovered
cost_any:
  - proof_burden_up
  - public_addendum_required
  - handler_burden_up
  - future_raw_proof_cost_up
future_effect_any:
  - accepts_with_acknowledgement_only
  - route_narrowed
  - scar_persists

Wrong recipient becomes hostile

The recipient executed the old order and now has exposure, liability, or leverage.

Expected deltas:

relief_any:
  - old_instruction_source_visible
cost_any:
  - recipient_hostility_up
  - witness_exposure_up
  - sponsor_retaliation_up
  - runner_risk_up
future_effect_any:
  - hostile_reader_armed
  - substitute_required
  - route_costlier

Recovery scars

Repair may not erase the event. At least one scar remains:

• public addendum required;
• lawful bridge required;
• checksum required;
• route asset narrowed;
• stale holder becomes hostile, exposed, or absent;
• future recall requires acknowledgement surface;
• recovery-only label persists;
• schedule, proof, handler, runner, or crew load remains consumed.

Non-goals

• Not random operational failure.
• Not a punishment for all communication mistakes.
• Not a flavor-only confusion event.
• Not a fixed-phase upkeep event.
• Not valid unless a source state changed and an old instruction materially affects a future reader, route, custody chain, or broadcast reality.