Rebuttal Recall Collision / 反驳召回撞锁线

Rebuttal Recall Collision is a pressure-system storyline for the moment two legitimate correction streams collide.

A newer boundary may require 过期派发召回线 because an old instruction is still moving through the building. The same boundary may also require 读者反驳通知线 because a later reader wants to cite the row as authority before the affected party can answer.

The current corpus already tests those two situations independently. The uncovered seam is their collision: stopping an old instruction is not the same as giving a future reader an answerable authority row, and giving an answer is not the same as stopping the old instruction.

Primary playable question

When recall and rebuttal compete over the same authority row, who gets bound first: the stale holder, the affected party, the future reader, the public, the lawful body, the sponsor desk, the runner chain, or nobody cleanly?

Every answer must preserve both pressures and change:

• stale instruction state;
• rebuttal or affected-party state;
• bound and unbound recipients/readers;
• acknowledgement surface;
• future route, proof, broadcast, public receipt, custody, or route asset effect.

Why this is the next useful expansion

Recent green surfaces made two adjacent seams executable:

• 读者反驳通知线 makes future-reader citation answerable.
• 过期派发召回线 prevents old instructions from silently synchronizing.
• 预播排练污染线 creates draft traces that can later be cited or recalled.
• 阮尺删改速记员线 makes transcript survival and carrier exposure playable.
• 交接链跑腿 Storyline makes low-rank handoff and receipt movement playable.

The missing test is not another notice, another recall, or a bigger content count. It is the collision where a correction can be true for one actor and false for another because acknowledgements did not bind the same surface.

Bound content pack

This storyline binds:

• 反驳召回撞锁机制;
• 反驳召回撞锁案卷;
• 反驳召回仲裁;
• 召回反驳错绑定.

State-triggered entry

Open this storyline when all are true:

entry_state:
  trigger_kind: state_pressure
  shared_authority_row_present: true
  stale_instruction_still_actionable: true
  future_reader_wants_to_consume_authority: true
  affected_party_or_explicit_absence_present: true
  stale_holder_or_explicit_absence_present: true
  recall_boundary_unresolved_or_partial: true
  rebuttal_boundary_unresolved_or_partial: true
  future_route_can_change_by_binding_order: true
  player_can_assign_arbitration_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Valid shared authority sources include transcript rows, rehearsal traces, dispatch lines, custody copies, sponsor copies, public receipts, ward orders, fan queue receipts, pirate packets, archive dockets, and route asset tags.

Storyline spine

Beat 1 — A shared authority row splits into two correction needs

A boundary, row, proof object, or route asset is updated or cited. One side requires recall because an old instruction is already actionable. Another side requires rebuttal because a future reader will use the row as proof, receipt, lawful fact, route unlock, closure, or broadcast reality anchor.

The player receives 反驳召回撞锁案卷.

Beat 2 — Recipients and readers are not the same actors

The stale holder may be floor crew, cutroom, sponsor, archive, inspector, ward, runner, fan delegate, pirate relay, or explicit absence. The future reader may be archive, inspector, sponsor, editor, fan public, pirate relay, route asset, broadcast reality, lawful body, management, or equivalent.

The affected party may be reachable, protected, recovering, hostile, proxy-only, captured, missing, or explicitly absent.

Beat 3 — The player assigns binding order

The player opens 反驳召回仲裁.

The rite assigns shared authority row, stale docket or absence, rebuttal ledger or absence, arbitrator, stale holder, affected party, carrier, binding order, acknowledgement surface, reader to bind, recipient to bind, unbound surfaces, and accepted cost.

Beat 4 — Binding creates partial truth

A successful branch never says all corrected. It says which actors are bound and which remain unbound.

Valid future effects include:

• future reader accepts only with dual acknowledgement;
• route requires late rebuttal;
• route requires recall stamp;
• split reader table required;
• lawful freeze until arbitration;
• sponsor unwind required;
• route asset narrowed;
• recovery-only.

Beat 5 — Misbinding becomes visible

If recall is filed as rebuttal, rebuttal is filed as recall, acknowledgement is absent, sponsor hush is filed as clean closure, or split binding lacks a table, 召回反驳错绑定 fires or is armed.

The event must change future play and cannot be mood text.

Branch map

Branch	Relief	Cost	Future route effect
Recall first	stale execution risk falls	no-notice debt or affected-party hostility rises	late rebuttal, annex, or counterline required
Notice first	answerability improves	stale execution or schedule risk rises	recall stamp or checksum required
Split bind	scoped route remains playable	proof burden, handler burden, source ambiguity rise	split reader table required
Freeze both	false execution and false authority risk fall	inspection heat, schedule delay, sponsor pressure rise	route blocked until arbitration or dual acknowledgement
Public bridge	public legitimacy and anti-capture improve	sponsor heat, witness exposure, contradiction pressure rise	public accepts; lawful bridge still required
Sponsor hush	immediate slot or sponsor pressure falls	contract capture, false notice, public distrust rise	sponsor unwind or public/lawful repair required
Runner bridge	paired acknowledgement becomes possible	runner risk, payroll leak, custody noise, stenographer exposure rise	route asset accepts only with tag/checksum
Misbound default	short-term burden may fall	false authority, stale execution, hostility, public confusion rise	blocked, hostile, sponsor-only, lawful-only, or recovery-only

Character and faction hooks

• 韩砚霜 can freeze both sides through lawful or archive authority, but inspection heat and bureau debt rise.
• Shen Luo can sequence sponsor-facing recall and silence, but contract capture and false notice risk rise.
• 郁蓝 can carry public bridge, but witness exposure and sponsor pressure rise.
• Baiya can provide checksum bridge, but edit debt and source ambiguity rise.
• Redaction Stenographer can carry transcript rebuttal with exposure cost.
• 交接链跑腿 Storyline can run paired acknowledgement through corridor custody, but runner risk, payroll leak, and custody noise rise.
• 海盗频段童声 can relay public bridge when lawful readers are captured, but pirate relay custody risk rises.

Counter contract

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

Primary surfaces:

• correction_authority_conflict
• stale_dispatch_risk
• notice_legitimacy
• false_authority
• false_execution
• future_reader_acceptance
• affected_party_hostility
• proof_burden
• handler_burden
• schedule_pressure
• public_confusion
• sponsor_stop_loss_pressure
• contract_capture
• inspection_heat
• edit_debt
• runner_risk
• route_asset_pressure
• recovery_scar

Missability and recovery

This storyline is missed when implementation:

• lets recall automatically satisfy rebuttal;
• lets rebuttal automatically stop old instructions;
• treats a future reader and stale recipient as the same actor without evidence;
• records no bound or unbound surfaces;
• records no acknowledgement surface;
• allows sponsor hush as clean closure;
• lets split binding proceed without a split reader table;
• leaves future route acceptance identical across branch orders;
• triggers from fixed turn, fixed day/week, raw count, dashboard state, or lens health.

Recovery is allowed only with scar:

• late rebuttal;
• late recall stamp;
• dual acknowledgement;
• split reader table;
• lawful-only route;
• public-only route;
• sponsor unwind;
• route asset narrowed;
• substitute proof;
• recovery-only route.

Replay evidence shape

storyline_id: storyteller.storyline.rebuttal_recall_collision.v1
session_id: lens-rebuttal-recall-collision-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  shared_authority_row_present: true
  stale_instruction_still_actionable: true
  future_reader_wants_to_consume_authority: true
  affected_party_or_explicit_absence_present: true
  stale_holder_or_explicit_absence_present: true
  recall_boundary_unresolved_or_partial: true
  rebuttal_boundary_unresolved_or_partial: true
  no_fixed_turn_trigger: true
active_objects:
  collision_docket: storyteller.card.rebuttal_recall_collision_docket.v1
  stale_docket: storyteller.card.stale_dispatch_docket.v1 | equivalent | explicit_absence
  rebuttal_ledger: storyteller.card.reader_rebuttal_notice_ledger.v1 | equivalent | explicit_absence
offered:
  rite: storyteller.rite.rebuttal_recall_arbitration.v1
branch_runs:
  recall_first:
    selected_binding_order: recall_first
    bound_recipients: []
    bound_readers: []
    unbound_or_explicit_absence: []
    future_route_effect: late_rebuttal_required
    counter_deltas:
      relief: []
      cost: []
      future: []
  notice_first:
    selected_binding_order: notice_first
    future_route_effect: recall_stamp_required
  split_bind:
    selected_binding_order: split_bind
    future_route_effect: split_reader_table_required
  freeze_both:
    selected_binding_order: freeze_both
    future_route_effect: blocked_until_dual_acknowledgement
  misbound_default:
    event_seen_or_armed: storyteller.event.recall_rebuttal_misbind.v1
    future_route_effect: blocked | costlier | lawful_only | public_only | sponsor_only | split_pending | dual_ack_required | recovery_only
assertions:
  - entry_is_state_triggered
  - shared_authority_row_visible
  - recall_and_rebuttal_sides_are_separate
  - binding_order_is_assignable
  - bound_and_unbound_actors_are_recorded
  - acknowledgement_surface_is_per_actor
  - branch_order_changes_future_acceptance
  - misbind_default_is_durable
  - recovery_keeps_scar
  - no_fixed_turn_day_week_raw_count_dashboard_or_lens_health_trigger

Non-goals

• Not a governance checklist.
• Not filler escalation.
• Not a turn-number continuation.
• Not a replacement for Stale Dispatch Recall or Reader Rebuttal Notice.
• Not valid if every correction reaches every actor for free.
• Not valid if no future reader or stale recipient changes because of binding order.