Storyteller Wiki

Stale Dispatch Docket / 过期派发案卷

3 min read

Stale Dispatch Docket / 过期派发案卷

Stale Dispatch Docket is the visible card for a dangerous production seam: a boundary, ruling, transcript, availability state, or rehearsal decision has changed, but an older instruction is already queued in a corridor, call sheet, cutroom mark, sponsor memo, public script, pirate relay, recovery ward order, or route asset handoff.

The card exists to prevent magic synchronization. A correct decision does not automatically update every actor who is about to execute the old version.

Card promise

A valid docket instance must name:

  1. the source decision or boundary that changed;
  2. the stale instruction still in circulation;
  3. the holder or recipient who may execute it;
  4. the stale action that will happen if no recall reaches them;
  5. at least two affected readers or one reader plus explicit absence;
  6. the acknowledgement surface that proves the recall arrived;
  7. the default state if the old instruction executes.

The card opens from state pressure, never from a fixed turn, day, week, chapter quota, raw content count, or lens-health check.

Docket fields

card_id: storyteller.card.stale_dispatch_docket.v1
state: hidden | recall_open | partially_acknowledged | recalled | stale_executed | recovered_with_scar
source_change:
  source_decision_or_boundary: <ruling_boundary_transcript_availability_rehearsal_or_equivalent_id>
  source_state_before: <state>
  source_state_after: <state>
  source_history_preserved: true
stale_instruction:
  instruction_id: <stable 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>
  holder_or_recipient: floor_crew | editor | sponsor | inspector | archive | fan_delegate | ward | runner | pirate_relay | artist_proxy | witness_proxy | explicit_absence
  stale_action_if_executed: <wrong_move_wrong_cut_wrong_body_wrong_quote_wrong_gate_wrong_airing_or_equivalent>
readers:
  - reader_id: <reader-a>
    wants: <acceptance demand>
    harmed_if_stale: true
  - reader_id: <reader-b-or-explicit-absence>
    wants: <acceptance demand or explicit_absence>
    harmed_if_stale: true | false
recall_requirements:
  recall_channel: live_floor_bulletin | lawful_notice | cutroom_patch | sponsor_retraction | public_addendum | runner_relay | quarantine_order | explicit_absence
  acknowledgement_surface: signed_stub | checksum | voice_ack | public_line | docket_stamp | witness_receipt | route_asset_tag | explicit_absence
  handler_or_absence: <handler or explicit_absence>
unworked_default:
  event: storyteller.event.stale_dispatch_execution.v1
  default_actor: <recipient_or_holder>
  default_state: stale_executed | false_execution | wrong_body_moved | wrong_cut_aired | wrong_quote_filed | route_asset_misdelivered | recovery_only

Eligible source changes

Use this card when the source change is already made or selected and the old instruction is still actionable. Valid sources include:

  • a preair rehearsal boundary that supersedes a scratch trace;
  • a transcript redaction posture that supersedes a previous hearing excerpt;
  • an availability-reader or ruling-reader collision result that narrows access;
  • a call-sheet reassignment that changes floor coverage;
  • a claimant briefing or public addendum that changes who may speak;
  • a recovery ward, witness, artist, or route-asset custody boundary that changes who may move a person, proof, or public claim.

Branch memory

The docket must remember partial recall. A branch may recall the live floor but fail to reach cutroom; retract sponsor copy but leave public script stale; send a lawful notice without ward acknowledgement; or seal a route-asset handoff while a runner still carries the old tag.

Clean universal recall is invalid unless it pays cost and records acknowledgement for every affected reader.

Counter and state contract

Every resolved branch should mutate at least one relief, one cost, and one future reader or route effect.

Recommended relief surfaces:

  • stale_dispatch_risk_down
  • false_execution_blocked
  • final_air_integrity_up
  • custody_clarity_up
  • reader_acceptance_scoped

Recommended cost surfaces:

  • schedule_pressure_up
  • handler_burden_up
  • proof_burden_up
  • public_confusion_up
  • sponsor_stop_loss_pressure_up
  • inspection_heat_up
  • edit_debt_up
  • runner_risk_up

Recommended future effects:

  • future_reader_accepts_with_acknowledgement
  • future_reader_requires_addendum
  • route_asset_narrowed
  • route_blocked_until_recall
  • stale_execution_scar_persists
  • recovery_only

Non-goals

  • Not a generic task list.
  • Not a staff-management methodology page.
  • Not a notice-order replacement; first briefing and stale instruction recall are separate pressures.
  • Not a ruling-reader replacement; reader interpretation and physical instruction execution are separate pressures.
  • Not valid if all recipients silently update for free.
  • Not valid if old instructions can execute with no future route, custody, broadcast, or reader consequence.

Graph View

Backlinks