Replay-Resume Collision / 复盘接手冲突线

Replay-Resume Collision is the pressure storyline for the moment a branch already stored in a replay export capsule re-enters play through a resumed active hand, and the two surfaces disagree.

The replay capsule may say the branch is scoped, sealed, traded, exposed, quarantined, refused, misattributed, or recovery-only. The resume packet may say the same branch is ready, sponsor-safe, lawful-first, public-warning, editor-checksummed, hidden, or cleanly absent. Both can be valid in isolation. The problem begins when a future reader, route, rite, desk, or claimant consumes both as if they were compatible.

This storyline binds the already-existing 复盘接手冲突案卷, 复盘接手对表, and 匣行冲突默认 into a playable management/RPG flow.

Gap diagnosis

复盘导出羁押线 already prevents an exportable replay from becoming a clean proof object. 复盘接手包分诊线 already prevents the resumed hand from hiding live pressure rows.

The uncovered seam is their intersection: a replay capsule and a resume packet can each preserve pressure, yet still launder each other when they name the same source branch differently.

Examples:

• a scoped capsule is rebuilt as clean active-hand readiness;
• a sealed or lawful-only capsule is surfaced by the packet as public proof;
• a traded or sponsor-only capsule appears in a balanced packet;
• an exposed public capsule is hidden under sponsor-safe packet posture;
• a quarantined or recovery-only capsule is loaded as fresh;
• a packet omission erases the capsule counter-branch;
• the future route reads packet readiness while ignoring replay scope.

This line makes that collision explicit before a route uses it.

Primary playable question

When the export record and the resumed hand disagree, does the producer merge the surfaces with a scar, split them for different readers, privilege capsule scope, privilege packet visibility, quarantine the collision, assign a counter-reader, or accept a default that hardens false clean continuity?

A valid answer must name the shared source branch, both surface states, the collision kind, the beneficiary if unreconciled, the harmed reader or claimant, the selected reconciliation posture, and the future route effect.

State-triggered entry

Open this storyline only from live state pressure:

entry_state_required:
  trigger_kind: state_pressure
  replay_capsule_present: true
  resume_packet_present: true
  shared_source_branch_or_route_asset_present: true
  future_reader_or_route_consumes_both_surfaces: true
  capsule_state_visible: true
  packet_row_state_visible_or_explicit_absence: true
  collision_kind_visible: true
  beneficiary_if_unreconciled_visible_or_explicit_absence: true
  harmed_reader_or_claimant_visible_or_explicit_absence: true
  player_can_merge_split_privilege_capsule_privilege_packet_quarantine_assign_counter_reader_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_replay_count_trigger: true
  no_raw_row_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Valid entry is not “many replays exist” or “many hand rows exist.” Valid entry is a shared branch, asset, or reader whose capsule and packet states disagree in a way that can change future play.

Bound content pack

• 复盘接手冲突案卷 records the source branch, replay side, resume side, collision kind, beneficiary, harmed reader, and available first actions.
• 复盘接手对表 is the assignable management action that resolves the collision before a future reader consumes it.
• 匣行冲突默认 fires or arms when the player proceeds without reconciliation.

Storyline spine

Beat 1 — The capsule returns to the floor

A previous branch has an export capsule from 复盘导出匣. The capsule preserves a custody state, custodian or absence, counter-branch or absence, and future reader effect.

The capsule is not a save file. It is a route asset whose state can narrow or poison future use.

Beat 2 — The resume packet rebuilds the hand

The current floor receives 复盘接手包案卷. The packet may surface the same row, hide it with register, mark it cleanly absent, or prioritize another claimant.

The packet is not merely UI capacity. It is a custody object that decides what the player can see and act on first.

Beat 3 — The collision docket names the mismatch

Create or update 复盘接手冲突案卷. The docket must separate replay state from packet state. It must name who benefits if the two are treated as compatible and who is harmed by that compatibility claim.

Accepted collision kinds include:

• 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.

Beat 4 — The producer reconciles or defaults

Run 复盘接手对表. The rite demands a reconciliation handler or explicit absence, capsule custodian, packet owner, source proof, omitted counter-branch, harmed reader, bridge or cost, and selected posture.

No sponsor payment, inspector seal, editor checksum, management priority, public heat, or producer authority can resolve the collision without those slots.

Beat 5 — Future play consumes the collision state

A later route, rite, reader, desk, claimant, loadout, replay export, resume packet, appeal, public addendum, sponsor gate, edit checksum, or broadcast-reality patch must read the collision state.

If future play accepts the branch without reading the collision, 匣行冲突默认 must fire or remain armed.

Branch map

Branch A — Merge with scar

The producer makes both surfaces cite each other and preserves the scar inside the active hand.

selected_posture: merge_with_scar
state_after: merged_with_scar
relief_any:
  - active_hand_legibility_up
  - capsule_legibility_up
  - future_reader_acceptance_up
cost_any:
  - handler_burden_up
  - scar_visibility_up
  - sponsor_or_inspector_pressure_up
future_effect_any:
  - accepted_with_scope
  - packet_row_cites_capsule_state
  - capsule_names_packet_row

Branch B — Split packet and capsule

The producer refuses one clean merged truth and forces different readers to consume the two surfaces separately.

selected_posture: split_packet_and_capsule
state_after: split_required
relief_any:
  - false_clean_resume_down
  - counter_branch_visibility_up
cost_any:
  - schedule_pressure_up
  - future_reconciliation_cost_up
future_effect_any:
  - route_requires_dual_reader
  - public_or_lawful_addendum_required

Branch C — Privilege capsule scope

The replay capsule controls future use. The packet can remain playable, but it must narrow or watchlist rows that contradict the capsule.

selected_posture: privilege_capsule_scope
state_after: capsule_privileged
relief_any:
  - replay_capsule_integrity_up
  - misattribution_risk_down
cost_any:
  - active_hand_capacity_pressure_up
  - omitted_packet_rows_watchlisted
future_effect_any:
  - packet_must_respect_capsule_scope
  - sponsor_or_editor_packet_narrowed

Branch D — Privilege packet visibility

The resumed hand controls immediate play, but the capsule becomes a later clearance cost instead of disappearing.

selected_posture: privilege_packet_visibility
state_after: packet_privileged
relief_any:
  - immediate_triage_speed_up
  - active_hand_legibility_up
cost_any:
  - capsule_clearance_cost_up
  - future_reader_distrust_up
future_effect_any:
  - capsule_attestation_required_later
  - route_costlier_if_capsule_reader_objects

Branch E — Quarantine collision

The producer blocks both surfaces from clean use until bridge proof or packet rebuild exists.

selected_posture: quarantine_collision
state_after: collision_quarantined
relief_any:
  - false_clean_resume_down
  - false_clean_replay_down
cost_any:
  - route_delay_up
  - management_pressure_up
future_effect_any:
  - blocked_until_bridge
  - packet_rebuild_required

Branch F — Assign counter-reader

The producer gives the harmed reader, excluded claimant, or counter-branch an explicit route to answer the collision.

selected_posture: assign_counter_reader
state_after: counter_reader_assigned
relief_any:
  - harmed_reader_erasure_down
  - public_or_lawful_rebuttal_legible
cost_any:
  - inspection_heat_up
  - sponsor_stop_loss_pressure_up
  - edit_debt_up
future_effect_any:
  - appeal_or_rebuttal_route_opened
  - future_reader_accepts_with_challenge

Branch G — Collision default

The producer proceeds as if the two surfaces agree. A false-clean current hand or false-clean replay hardens.

selected_posture: accept_collision_default
state_after: collision_defaulted
emitted_event: storyteller.event.capsule_row_collision_default.v1
relief_any:
  - immediate_triage_burden_down
cost_any:
  - contradiction_pending_up
  - false_clean_resume_up
  - future_recovery_cost_up
future_effect_any:
  - blocked
  - costlier
  - lawful_appeal_required
  - public_addendum_required
  - sponsor_gate_required
  - edit_checksum_required
  - packet_rebuild_required
  - capsule_attestation_required
  - recovery_only

Counter contract

Every constructive branch must mutate at least three surfaces: one relief, one cost, and one future route or reader effect.

Primary surfaces:

• active_hand_legibility
• capsule_legibility
• scar_visibility
• omission_register_integrity
• counter_branch_visibility
• false_clean_resume
• false_clean_replay
• sponsor_stop_loss_pressure
• inspection_heat
• edit_debt
• public_receipt_distrust
• route_delay
• future_recovery_cost
• broadcast_reality_contradiction
• future_reader_acceptance
• route_asset_integrity

Integration notes

• With 复盘导出羁押线, capsule scope remains binding after the branch returns to the floor.
• With 复盘接手包分诊线, a finite hand can prioritize rows without erasing capsule counter-branches.
• With 导出证据回流分岔线, returned evidence must preserve both source-session and resume-packet collision state.
• With 路线装配兼容线, a route bundle cannot load a recovery-only or quarantined capsule as fresh just because the packet row is visible.
• With 读者反驳通知线, a harmed reader can receive a counter-reader route rather than being erased by capsule or packet priority.

Missability and recovery

This storyline is missed when implementation:

• treats a replay capsule and resumed packet as automatically compatible;
• lets packet readiness override capsule scope without cost;
• lets capsule existence prove a hidden packet row was visible;
• hides beneficiary and harmed reader;
• reads packet row visibility without reading capsule counter-branch;
• reads capsule scope without reading packet omission register;
• resolves conflict by generic authority, money, checksum, legality, or UI capacity;
• triggers from fixed turn, fixed day/week, raw replay count, raw row count, dashboard state, or lens health.

Recovery is allowed only with visible scar:

• late merge with scar;
• packet rebuild;
• capsule re-attestation;
• lawful appeal;
• public addendum;
• sponsor gate unwind;
• edit checksum correction;
• counter-reader notice;
• route converted to costlier, split, blocked, contradiction-pending, or recovery-only.

Replay/session evidence shape

storyline_id: storyteller.storyline.replay_resume_collision.v1
session_id: lens-replay-resume-collision-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  replay_capsule_present: true
  resume_packet_present: true
  shared_source_branch_or_route_asset_present: true
  future_reader_or_route_consumes_both_surfaces: true
  collision_kind_visible: true
  no_fixed_turn_trigger: true
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: <state>
  capsule_custodian_or_absence: <custodian or explicit_absence>
  capsule_counter_branch_or_absence: <branch or explicit_absence>
resume_side:
  resume_packet_id: storyteller.card.resume_packet_docket.v1
  packet_row_id_or_absence: <row id or explicit_absence>
  packet_state_before: <state>
  packet_owner_or_absence: <owner or explicit_absence>
  row_visible_in_packet: true | false
  omission_register_or_absence: <register or explicit_absence>
collision:
  card: storyteller.card.replay_resume_collision_docket.v1
  collision_kind: <kind>
  beneficiary_if_unreconciled: <actor or explicit_absence>
  harmed_reader_or_claimant: <reader claimant or explicit_absence>
offered:
  rite: storyteller.rite.replay_resume_reconciliation.v1
branch_result:
  selected_posture: merge_with_scar | split_packet_and_capsule | privilege_capsule_scope | privilege_packet_visibility | quarantine_collision | assign_counter_reader | accept_collision_default
  collision_state_after: <state>
  future_reader_or_route_effect: <effect>
  emitted_event: storyteller.event.capsule_row_collision_default.v1 | none_if_valid
  counter_deltas:
    relief: []
    cost: []
    future: []
assertions:
  replay_and_resume_states_are_separate: true
  collision_kind_beneficiary_and_harmed_reader_visible: true
  branch_postures_diverge: true
  constructive_success_has_cost: true
  default_is_durable: true
  future_reader_consumes_collision_state: true
  no_fixed_turn_day_week_raw_count_dashboard_or_lens_health_trigger: true

Non-goals

• Not a save/load reconciliation screen.
• Not replay UI.
• Not a generic active-hand cleanup system.
• Not a dashboard or governance page.
• Not a raw replay-count or row-count milestone.
• Not a replacement for replay export custody or resume packet triage.
• Not valid unless the collision creates branch choice, cost, and future route or reader mutation.