Stale Dispatch Afteruse Review

Stale Dispatch Afteruse Review is the assignable rite for deciding how far a completed recall row may travel after its first operational use.

It resolves one Stale Dispatch Afteruse Docket row. A visible acknowledgement, old runner receipt, public line, lawful notice, or checksum note is insufficient unless the rite also records source instruction state, requested afteruse, harmed reader, proof bridge or absence, posture, cost, and future reader effect.

Required Assignment

assignment_required:
  rite_id: storyteller.rite.stale_dispatch_afteruse_review.v1
  docket: storyteller.card.stale_dispatch_afteruse_docket.v1
  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: <surface or explicit_absence>
  requested_afteruse: <use>
  future_reader_or_route: <reader or route>
  harmed_or_excluded_reader: <reader or explicit_absence>
  proof_bridge_or_explicit_absence: <proof or 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
  accepted_cost_or_explicit_absence: <cost or explicit_absence>

The rite is underfilled if it names only the old recall row or the reader requesting it.

Branches

certify_acknowledged_scope

The player certifies the recall row only for a named afteruse and reader.

dispatch_afteruse_state_after: scope_certified
relief_any: [future_reader_acceptance_up, recall_integrity_up, route_legibility_up]
cost_any: [scope_narrowness_up, handler_burden_up, excluded_reader_notice_due]
future_effect_any:
  [
    accepted_with_acknowledgement,
    acknowledgement_receipt_required,
    changed_facts_require_new_review,
  ]

restrict_afteruse_reader

The player blocks the overbroad reader and preserves the recall row for a narrower surface.

dispatch_afteruse_state_after: reader_restricted
relief_any: [false_clean_afteruse_down, harmed_reader_protected, public_or_lawful_overreach_blocked]
cost_any: [route_delay_up, holder_hostility_up, sponsor_or_archive_pressure_up]
future_effect_any: [split_required, reader_specific_use_only, alternate_route_required]

attach_bridge_or_addendum

The player adds lawful annex, public addendum, checksum, route tag, runner receipt, or reissue notice before afteruse.

dispatch_afteruse_state_after: bridge_attached
relief_any: [lawful_acceptance_up, public_legibility_up, route_or_cutroom_trace_preserved]
cost_any: [proof_burden_up, public_exposure_up, edit_or_runner_risk_up]
future_effect_any: [bridge_or_addendum_required, accepted_with_bridge_cost, checksum_due]

unwind_stale_execution_capture

The player unwinds a first stale executor or first-reader capture before letting another reader cite the row.

dispatch_afteruse_state_after: capture_unwound
relief_any: [private_capture_down, harmed_reader_unblocked, stale_executor_scope_narrowed]
cost_any: [makegood_due, sponsor_pressure_up, handler_debt_up]
future_effect_any: [capture_unwind_due, public_unwind_required, route_costlier]

reissue_current_dispatch

The player creates a fresh instruction instead of stretching the old recall row.

dispatch_afteruse_state_after: reissue_required
relief_any: [current_instruction_visible, stale_row_not_overread, future_reader_gets_current_basis]
cost_any: [schedule_pressure_up, runner_risk_up, receipt_debt_up]
future_effect_any: [fresh_dispatch_required, old_recall_row_scoped, route_requires_reissue_receipt]

quarantine_dispatch_afteruse

The player blocks the afteruse claim until a new receipt, annex, or route recovery surface exists.

dispatch_afteruse_state_after: afteruse_quarantined
relief_any: [false_clean_afteruse_down, recall_integrity_up]
cost_any: [current_route_blocked, schedule_scar_up, claimant_pressure_up]
future_effect_any: [blocked, recovery_only, new_dispatch_required]

false_stale_dispatch_afteruse_default

The review is skipped, underfilled, or lets a future reader consume an overbroad recall state as universal service.

emitted_or_armed_event: storyteller.event.false_stale_dispatch_afteruse_default.v1
dispatch_afteruse_state_after: false_clean_afteruse | captured_by_reader | recovery_only
relief_any: [immediate_pressure_down]
cost_any: [false_clean_service_up, harmed_reader_hostility_up, proof_or_public_debt_up]
future_effect_any:
  [
    blocked,
    hostile,
    costlier,
    acknowledgement_receipt_required,
    bridge_or_addendum_required,
    fresh_dispatch_required,
    recovery_only,
  ]

Completion Contract

Every branch must write relief, cost, dispatch after-state, and future reader effect. The rite fails if the old recall becomes universal service because it existed, because one recipient acknowledged it, or because one reader already accepted it.

Non-Goals

• Not a first stale-dispatch recall.
• Not a generic notice rite.
• Not valid unless the later reader and harmed reader are both visible or explicitly absent.