Replay-Resume Collision Docket / 复盘接手冲突案卷

Replay-Resume Collision Docket is the board card for a resumed active hand that contains, hides, or rewrites a branch already stored in a 复盘导出匣.

It exists because a replay capsule and a resume packet can both be valid in isolation while giving different answers to the current route: the capsule may be scoped, sealed, traded, exposed, quarantined, refused, misattributed, or recovery-only, while the packet row may claim balanced readiness, sponsor safety, lawful priority, public warning, editor checksum, hidden default, or clean absence.

Required fields

card_id: storyteller.card.replay_resume_collision_docket.v1
collision_id: <stable id>
trigger_kind: state_pressure
source:
  source_session_id_or_handoff: <session id handoff tray archive tray producer station or explicit_absence>
  source_branch_id: <branch id>
  route_asset_or_absence: <asset or explicit_absence>
  future_reader_or_route: <reader route rite desk claimant or explicit_absence>
replay_side:
  replay_capsule_id: storyteller.card.replay_export_capsule.v1
  capsule_state_before: scoped | sealed | lawful_only | traded | sponsor_only | exposed | public_only | quarantined | recovery_only | blocked | misattributed | captured | false_clean | equivalent
  capsule_custodian_or_absence: <custodian or explicit_absence>
  capsule_counter_branch_or_absence: <branch or explicit_absence>
  capsule_future_reader_effect: <effect>
resume_side:
  resume_packet_id: storyteller.card.resume_packet_docket.v1
  packet_row_id_or_absence: <row id or explicit_absence>
  packet_state_before: balanced_packet | claimant_priority_packet | sponsor_safe_packet | inspector_first_packet | fan_public_warning_packet | editor_checksum_packet | quarantined_packet | hidden_row_default | clean_absent | equivalent
  packet_owner_or_absence: <owner or explicit_absence>
  row_visible_in_packet: true | false
  omission_register_or_absence: <register or explicit_absence>
collision:
  collision_kind: capsule_scoped_packet_clean | capsule_sealed_packet_public | capsule_traded_packet_balanced | capsule_exposed_packet_sponsor_safe | capsule_quarantined_packet_ready | capsule_refused_packet_required | capsule_misattributed_packet_hidden | capsule_recovery_only_packet_fresh | capsule_reader_scope_missing_from_packet | resume_omission_hides_capsule_counter_branch | equivalent
  beneficiary_if_unreconciled: sponsor | inspector | archive | editor | fan_public | management | producer | route_claimant | blackout_system | explicit_absence
  harmed_reader_or_claimant: <reader claimant or explicit_absence>
first_action_choices:
  - merge_with_scar
  - split_packet_and_capsule
  - privilege_capsule_scope
  - privilege_packet_visibility
  - quarantine_collision
  - assign_counter_reader
  - accept_collision_default

Design use

Use this card only when both surfaces matter to future play. If the capsule is not consumed by the resumed route, or the packet row is not about the same branch/asset/reader, no collision docket is needed.

Valid states after reconciliation

• merged_with_scar — the packet shows the capsule state and the capsule names the packet row.
• split_required — the route must read packet and capsule separately.
• capsule_privileged — replay scope controls future use; packet omissions are watchlisted.
• packet_privileged — active-hand visibility controls immediate play; capsule use is narrowed or delayed.
• collision_quarantined — neither surface can be cited cleanly until bridge proof is assigned.
• counter_reader_assigned — a harmed reader receives an explicit rebuttal or appeal path.
• collision_defaulted — 匣行冲突默认 hardens.

Failure cases

This card fails if:

• the resumed packet treats a scoped capsule as clean active-hand readiness;
• a sealed capsule becomes public proof through packet priority;
• a traded or sponsor-only capsule appears as balanced packet truth;
• an exposed public capsule is hidden by sponsor-safe packet posture;
• a quarantined or recovery-only capsule is loaded as fresh;
• a hidden resume row erases the capsule counter-branch;
• future route use never reads the collision state;
• entry is based on fixed turn, fixed day/week, raw replay count, raw row count, dashboard state, or lens-health state.

Non-goals

• Not a save-file merge screen.
• Not replay UI.
• Not raw active-hand cleanup.
• Not a new global registry.
• Not valid unless the collision creates branch choice, cost, and future route effect.