Recall Rebuttal Misbind / 召回反驳错绑定

Recall Rebuttal Misbind is the visible failure or pressure event when a stale instruction recall and a reader rebuttal notice are treated as if they were the same correction.

It should fire, arm, or be recorded when the player fails to arbitrate 反驳召回撞锁案卷, when a branch lies about acknowledgement, or when a future reader consumes an authority row under the wrong correction boundary.

Event trigger

event_id: storyteller.event.recall_rebuttal_misbind.v1
trigger_kind: state_pressure
fires_when_any:
  - recall_filed_as_rebuttal
  - rebuttal_filed_as_recall
  - stale_holder_bound_but_future_reader_unbound
  - future_reader_bound_but_stale_holder_unbound
  - affected_party_hidden_without_explicit_absence
  - holder_absence_hidden_without_explicit_absence
  - acknowledgement_surface_missing
  - sponsor_hush_filed_as_clean_closure
  - split_bind_without_split_reader_table
  - no_future_route_effect_changed
must_not_fire_from:
  - fixed_turn
  - fixed_day_or_week
  - chapter_quota
  - raw_content_count
  - dashboard_state
  - lens_health_state

Required event payload

A valid event instance must name both sides of the misbind:

misbind_payload:
  shared_authority_row: <row id>
  stale_instruction: <instruction id>
  stale_holder_or_absence: <holder or explicit_absence>
  future_reader: <reader id>
  affected_party_or_absence: <party proxy constituency or explicit_absence>
  selected_binding_order_before_failure: recall_first | notice_first | split_bind | freeze_both | public_bridge | sponsor_hush | runner_bridge | default | explicit_absence
  missing_or_false_acknowledgement: <surface or reason>
  actor_who_consumed_wrong_boundary: <actor id>
  harmed_reader_or_recipient: <reader recipient claimant route asset or explicit_absence>
  state_after: stale_instruction_executed_without_answer | row_answered_after_old_execution | wrong_reader_bound | false_notice_authority | split_correction_unacknowledged | sponsor_capture_hardened | route_asset_misbound | recovery_only
  future_route_effect: blocked | costlier | lawful_only | public_only | sponsor_only | split_pending | dual_ack_required | recovery_only | equivalent

The event fails as content if it is only a mood beat, an apology line, or a hidden counter update.

Misbind families

Recall filed as rebuttal

The old instruction is stopped, but the affected party never receives a response boundary. The future reader treats recall as consent or answer.

Expected deltas:

• stale_dispatch_risk -1 or false execution risk falls;
• notice_legitimacy -1, affected_party_hostility +1, or false_authority +1;
• future route requires late rebuttal, public counterline, lawful annex, or recovery-only repair.

Rebuttal filed as recall

The affected party answers, but the old instruction still moves through floor, cutroom, sponsor, ward, runner, or route asset chain.

Expected deltas:

• notice_legitimacy +1 or contradiction legibility improves;
• stale_dispatch_risk +1, schedule_pressure +1, or route_asset_pressure +1;
• future route requires recall stamp, checksum, runner receipt, or quarantine.

Split without table

Different recipients and readers receive different corrections, but implementation fails to record who is bound.

Expected deltas:

• one route surface remains temporarily alive;
• public_confusion +1, proof_burden +1, or source_ambiguity +1;
• future route becomes split-pending or blocked until split reader table exists.

Sponsor hush hardens

A manager or sponsor quiets both correction streams without acknowledgement.

Expected deltas:

• immediate sponsor or slot pressure falls;
• contract_capture +1, public_receipt_distrust +1, or false_notice_risk +1;
• later route requires sponsor unwind or public/lawful bridge.

Carrier loss

A runner, stenographer, pirate relay, witness proxy, or clerk carries synchronized correction but loses one half of the acknowledgement.

Expected deltas:

• one reader or recipient gets bound;
• runner_risk +1, custody_noise +1, stenographer_exposure +1, or relay_custody_risk +1;
• route asset accepts only with recovered tag, checksum, or substitute proof.

Recovery contract

Recovery is allowed only if the scar remains visible. Valid scars include:

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

Non-goals

• Not a generic crisis event.
• Not a punishment for choosing recall or rebuttal.
• Not a duplicate of 过期派发执行.
• Not a duplicate of 反驳通知默认.
• Not valid if no future reader, stale holder, affected party, acknowledgement, or route effect is recorded.