Stale Dispatch Recall / 过期派发召回线

Stale Dispatch Recall is a pressure-system storyline for the moment after a decision is corrected but before the old instruction stops moving through the building.

The current corpus is strong on deciding boundaries: preair traces can be sealed or leaked, transcripts can be redacted, readers can collide over valid rows, and availability can be scoped. The uncovered seam is operational: the old call sheet, cutroom mark, sponsor copy, ward order, public script, runner note, or route-asset handoff may already be in motion.

This storyline makes the recall itself playable.

Primary playable question

When a newer boundary makes an old instruction dangerous, does the player recall it through live floor, cutroom, law, sponsor, public, runner, split acknowledgement, quarantine, or let the stale instruction execute first?

Every answer must change:

• stale instruction state;
• at least one recipient or reader acknowledgement;
• local execution risk;
• at least one future route, proof, broadcast, public receipt, or route asset reader.

Why this is the next useful expansion

The adjacent green surfaces answer different questions:

• 预播排练污染线 asks whether a draft trace becomes pseudo-real before final broadcast.
• 阮尺删改速记员线 asks what survives in the transcript after a hearing.
• 认领告知顺序线 asks who learns first.
• 裁定读者冲突线 asks how future readers interpret a valid row.
• 可用性读者冲突线 asks whether scoped access is reused too broadly.

The missing test is: after one of those systems changes the truth, can an old local instruction still act?

Bound content pack

This storyline binds:

• 过期派发召回机制;
• 过期派发案卷;
• 过期派发召回;
• 过期派发执行.

Downstream afteruse is handled by Stale Dispatch Afteruse Receipt, which checks whether a later reader can spend a prior recall row, partial acknowledgement, quarantine, or stale-execution scar.

State-triggered entry

Open this storyline when all are true:

entry_state:
  trigger_kind: state_pressure
  source_decision_or_boundary_changed: true
  source_history_preserved: true
  stale_instruction_issued_under_old_state: true
  stale_instruction_still_actionable: true
  holder_or_recipient_present_or_explicit_absence: true
  future_reader_or_route_can_be_affected: true
  player_can_recall_or_record_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true

Valid source families include:

• corrected preair boundary after a rehearsal trace;
• transcript redaction after a hearing excerpt was already copied;
• availability or ruling reader collision after old access was queued;
• call-sheet reassignment after floor instructions were printed;
• sponsor retraction after preview wording circulated;
• recovery ward, witness, artist, or route-asset custody order after an old handoff started.

Storyline spine

Beat 1 — Truth changes after instructions leave the desk

The player resolves or narrows a source state. The old instruction still exists as a local object: a call sheet, cutroom mark, sponsor copy, public script, ward order, runner note, pirate packet, proof handoff, or route-asset tag.

The player receives 过期派发案卷.

Beat 2 — The holder can execute the stale version

The docket names who can still act: live floor, editor, sponsor, inspector, archive, fan delegate, ward, runner, pirate relay, artist proxy, witness proxy, production absence, or explicit absence.

At least one future reader must care whether the old or new instruction executed.

Beat 3 — The player assigns recall

The player opens 过期派发召回.

The rite must assign:

• source decision or boundary;
• stale instruction;
• holder or explicit absence;
• recall channel;
• handler or explicit absence;
• acknowledgement surface or explicit absence;
• reader to protect;
• reader left stale or explicit absence;
• accepted cost;
• future route or reader effect.

Beat 4 — Acknowledgement changes future play

A recalled instruction must not simply disappear. The future reader checks the acknowledgement surface: signed stub, checksum, voice acknowledgement, public line, docket stamp, witness receipt, route asset tag, or explicit absence.

Valid future effects include:

• route accepts only with acknowledgement;
• public route requires addendum;
• lawful route requires bridge;
• stale cut requires checksum;
• route asset is narrowed;
• old holder becomes hostile or exposed;
• route remains recovery-only.

Beat 5 — Stale execution becomes visible

If the holder is hidden, acknowledgement is blank, one reader cites the old instruction, or the player accepts stale execution, 过期派发执行 fires or is armed.

The event must name the stale instruction, executor, capturing reader, harmed reader or claimant, execution kind, state after, and future route effect.

Branch map

Branch	Relief	Cost	Future route effect
Live-floor bulletin	wrong local execution risk falls	crew load, schedule pressure, public confusion rise	accepts only with floor acknowledgement
Cutroom patch	final-air integrity improves	edit debt, source ambiguity, proof burden rise	stale cut rejected or checksum required
Lawful notice	admissibility or custody clarity improves	inspection heat, bureau debt, public delay rise	public addendum or lawful bridge required
Sponsor retraction	false private promise falls	sponsor retaliation, contract capture, public distrust rise	public route costlier or sponsor-only scar
Public addendum	public legitimacy improves	panic, witness exposure, sponsor heat rise	lawful bridge required
Runner relay	misdelivery risk falls	runner risk, payroll leak, favor debt, custody noise rise	route asset accepts with tag only
Split recall	selected reader can proceed	source ambiguity, handler burden, future correction cost rise	split reader table or route narrowed
Quarantine	false execution blocked	route delay, missed pressure, sponsor pressure rise	route blocked until recall
Stale default	immediate assignment burden may fall	false execution, hostility, public confusion, heat rise	route captured, blocked, costlier, or recovery-only

Character and faction hooks

• Shen Luo can retract sponsor copy, but public distrust or contract capture rises.
• 韩砚霜 can serve lawful notice, but bureau debt or inspection heat rises.
• Baiya can patch cutroom marks, but edit debt and source ambiguity rise.
• 郁蓝 can make public addendum credible, but witness exposure and sponsor pressure rise.
• 交接链跑腿 Storyline can carry a corridor recall, but runner risk and custody noise rise.

Counter contract

Every branch must mutate at least three counters or durable states. At least one must be relief, one cost, and one future-route or reader effect.

Primary surfaces:

• stale_dispatch_risk
• false_execution
• final_air_integrity
• custody_clarity
• reader_acceptance_scoped
• schedule_pressure
• handler_burden
• proof_burden
• public_confusion
• sponsor_stop_loss_pressure
• contract_capture
• inspection_heat
• edit_debt
• source_ambiguity
• runner_risk
• crew_load
• route_asset_pressure
• future_route_acceptance

Missability and recovery

This storyline is missed when implementation:

• silently updates all recipients after a state change;
• records only the new boundary and deletes the old instruction;
• lacks holder or recipient state;
• has no acknowledgement surface;
• treats notify all as free;
• allows stale execution with no route, custody, broadcast, or reader consequence;
• triggers from fixed turn, day, week, chapter, raw count, or dashboard health.

Recovery is allowed only with scar:

• public addendum remains required;
• lawful bridge remains required;
• checksum remains required;
• route asset becomes narrowed or recovery-only;
• holder becomes hostile, exposed, absent, or expensive;
• future recall requires stronger acknowledgement.

Replay/session evidence shape

storyline_id: storyteller.storyline.stale_dispatch_recall.v1
session_id: lens-stale-dispatch-recall-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_decision_or_boundary_changed: true
  source_history_preserved: true
  stale_instruction_issued_under_old_state: true
  stale_instruction_still_actionable: true
  holder_or_recipient_present_or_explicit_absence: true
  future_reader_or_route_can_be_affected: true
  no_fixed_turn_trigger: true
source:
  source_decision_or_boundary: <id>
  source_state_before: <state>
  source_state_after: <state>
  stale_instruction: <instruction id>
  holder_or_recipient: <holder>
offered:
  card: storyteller.card.stale_dispatch_docket.v1
  rite: storyteller.rite.stale_dispatch_recall.v1
branch_runs:
  recall_branch:
    selected_recall_channel: live_floor_bulletin | lawful_notice | cutroom_patch | sponsor_retraction | public_addendum | runner_relay | split_recall | quarantine_order
    acknowledgement_surface_or_explicit_absence: <surface>
    reader_to_protect: <reader>
    reader_left_stale_or_explicit_absence: <reader or explicit_absence>
    state_after: <state>
    future_route_effect: <effect>
    counter_deltas:
      relief: []
      cost: []
      future: []
  stale_default:
    event_seen_or_armed: storyteller.event.stale_dispatch_execution.v1
    executed_by: <holder>
    capturing_reader: <reader>
    harmed_reader_or_claimant: <reader or claimant>
    state_after: stale_executed | false_execution | captured_by_old_instruction | route_asset_misdelivered | recovery_only
    future_route_effect: <effect>
assertions:
  - entry_is_state_triggered
  - source_history_preserved
  - old_instruction_visible
  - holder_or_explicit_absence_visible
  - acknowledgement_surface_visible
  - recall_branch_has_relief_cost_and_future_effect
  - stale_default_is_durable
  - recovery_keeps_scar
  - no_fixed_turn_trigger
  - no_fixed_day_or_week_trigger

Non-goals

• Not a governance page.
• Not a raw count expansion.
• Not a fixed maintenance phase.
• Not a generic project-management checklist.
• Not a replacement for first-notice, reader-collision, availability, or enforcement-load content.
• Not valid if recipients silently learn the updated truth for free.