Stale Dispatch Afteruse Docket

Stale Dispatch Afteruse Docket records a later attempt to spend a prior recall, partial recall, quarantine, or stale-execution scar as proof, service, public truth, lawful authority, route asset support, management cleanliness, or ending eligibility.

The docket is not another stale-dispatch docket. It assumes a source recall row already exists or is explicitly absent. It records what later reader wants to do with that row and who would be harmed if the source scope is overread.

Required Row

stale_dispatch_afteruse_docket:
  card_id: storyteller.card.stale_dispatch_afteruse_docket.v1
  trigger_kind: state_pressure
  source_recall_row: <recall row or explicit_absence>
  source_stale_instruction: <instruction id or explicit_absence>
  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 | false_stale_dispatch_afteruse_default
  dispatch_afteruse_state_after: scope_certified | reader_restricted | bridge_attached | capture_unwound | reissue_required | afteruse_quarantined | false_clean_afteruse | captured_by_reader | recovery_only
  future_reader_or_route_effect: accepted_with_acknowledgement | split_required | bridge_or_addendum_required | capture_unwind_due | fresh_dispatch_required | checksum_due | blocked | hostile | costlier | recovery_only
  counter_deltas: required

Required Separations

The row is invalid if it collapses any of these:

• source recall row;
• source stale instruction;
• instruction state before afteruse;
• acknowledgement or execution surface;
• requested afteruse;
• future reader or route;
• harmed or excluded reader;
• proof bridge or explicit absence;
• selected posture;
• after-state;
• future reader or route effect.

Valid Row Examples

• A public addendum recall is later cited by a lawful annex; the docket requires lawful proof or reader restriction before lawful use.
• A runner-only acknowledgement is later used by a route asset; the docket requires a runner receipt or fresh dispatch.
• A stale-execution scar is later cited by management as proof that the old instruction completed cleanly; the docket requires unwind or quarantine.
• A cutroom checksum requirement is later treated as public truth; the docket requires checksum readback and names the excluded public reader.

Non-Goals

• Not a generic action log.
• Not a replacement for Stale Dispatch Docket.
• Not valid unless a later reader or route is visible.