Stale Dispatch Afteruse Receipt

Stale Dispatch Afteruse Receipt makes a completed recall row reusable only through named afteruse scope.

The mechanism exists when a prior stale-dispatch result is still true but a later reader wants to spend it in a different context. A public addendum does not automatically satisfy a lawful annex. A runner-only acknowledgement does not automatically satisfy a route asset. A stale-execution scar cannot become clean management proof unless its source row, harmed reader, proof bridge, selected posture, and future route effect remain visible.

Entry Contract

stale_dispatch_afteruse_receipt:
  trigger_kind: state_pressure
  source_recall_row_visible: true
  source_stale_instruction_visible: true
  source_instruction_state_visible: true
  acknowledgement_or_execution_surface_visible: true
  requested_afteruse_visible: true
  future_reader_consumes_dispatch_state: true
  harmed_or_excluded_reader_visible_or_explicit_absence: true
  player_can_certify_restrict_bridge_unwind_reissue_quarantine_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_dispatch_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Afteruse States

stale_dispatch_afteruse_states:
  - unspent_recall
  - afteruse_requested
  - scope_certified
  - reader_restricted
  - bridge_attached
  - stale_capture_unwound
  - current_dispatch_reissued
  - afteruse_quarantined
  - false_clean_afteruse
  - captured_by_reader
  - hostile_reader
  - recovery_only

The implementation fails if a source recall state is collapsed into a generic notified flag.

Branch Contract

Every non-default branch must record:

stale_dispatch_afteruse_resolution:
  source_recall_row: <row id>
  source_stale_instruction: <instruction id>
  source_instruction_state_before_afteruse: acknowledged_scope | partially_acknowledged | split_recall | quarantined_instruction | stale_executed | false_execution_scar | runner_only_ack | public_addendum_only | lawful_notice_only | sponsor_retraction_only | cutroom_checksum_required | recovery_only
  acknowledgement_or_execution_surface: signed_stub | checksum | voice_ack | public_line | lawful_notice | runner_tag | route_asset_tag | stale_execution_scar | explicit_absence
  requested_afteruse: route_unlock | sponsor_package | lawful_annex | public_table | archive_release | cutroom_checksum | ward_service | management_report | ending_gate | equivalent
  future_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
  proof_bridge_or_explicit_absence: acknowledgement_receipt | lawful_annex | public_addendum | checksum | route_asset_tag | runner_receipt | reissue_notice | explicit_absence
  selected_afteruse_posture: certify_acknowledged_scope | restrict_afteruse_reader | attach_bridge_or_addendum | unwind_stale_execution_capture | reissue_current_dispatch | quarantine_dispatch_afteruse
  dispatch_afteruse_state_after: <state>
  relief_any: []
  cost_any: []
  future_effect_any: []

Failure Cases

The mechanism must fail if:

• a partial recall unlocks a later route with no afteruse row;
• a runner-only, public-only, lawful-only, sponsor-only, cutroom-only, or recovery-only recall is accepted by every reader;
• a stale-execution scar is spent without unwind, reissue, checksum, or recovery cost;
• a harmed or excluded reader is hidden;
• a fresh dispatch is implied without a receipt;
• default changes only notification text, reputation, or a generic pressure counter.

Default Contract

The default is False Stale Dispatch Afteruse Default. It must record false-clean dispatch afteruse, source recall row or explicit absence, hidden or overbroad dispatch scope, capturing reader or route, harmed reader, after-state, future reader effect, at least three counter deltas, and durable mutation.