Replay Export Custody / 复盘导出羁押线

Replay Export Custody is a storyline about what happens after a branch has become replayable enough to be useful. The producer can no longer treat the replay as private memory: sponsors want a clean clip, editors want checksum continuity, inspectors want sealed proof, fan publics want raw receipts, and management wants a case-study metric.

The line turns replay export into route-asset custody. The player must decide whether the replay capsule is scoped, sealed, traded, exposed, quarantined, refused, or captured as a false-clean object.

Storyline gap

The current surface already has strong coverage for public recap capture, stability package authorship, evidence carryover, management compression, and route-asset state. The missing story pressure is the exportable replay object that sits between them.

A replay can now become:

  • a lawful annex that blocks public use;
  • a sponsor-safe proof that lowers stop-loss pressure while hiding fan debt;
  • an editor checksum that smooths continuity while increasing source ambiguity;
  • a fan-public receipt that protects truth while exposing witnesses;
  • a management case that counts relief while hiding who paid;
  • a route asset that opens future play only with scope, scar, and custodian attached.

Entry conditions

This storyline opens from state, not from a fixed turn:

entry_state:
  trigger_kind: state_pressure
  source_branch_result_present: true
  source_branch_has_relief_or_route_access: true
  source_branch_has_scar_or_omitted_cost: true
  export_request_present: true
  claimant_count_min: 2
  future_reader_present: true
  no_fixed_turn_trigger: true

Good source branches include:

  • a stability package whose omitted frame is still alive;
  • a public recap that made a scar citeable or hidden;
  • an evidence carryover proof that now affects a route asset;
  • a management compression report that wants clean metrics;
  • an editor checksum split;
  • a sponsor bridge;
  • an inspector hold;
  • a fan oxygen receipt;
  • a route-asset custody dispute.

Cast pressure

The line does not require a new central NPC. It reuses existing desks and claimants as pressure:

  • sponsor pressure wants relief proof and liability safety;
  • editor pressure wants replay continuity and checksum acceptance;
  • inspector/archive pressure wants lawful-only admissibility;
  • fan-public pressure wants public receipts and raw proof;
  • management pressure wants yield proof;
  • producer pressure wants future route access without universal exposure;
  • route-asset claimants want the replay to confirm, contest, or poison custody.

Beats

Beat 1 — The capsule opens

A scarred branch becomes exportable. 复盘导出匣 enters the offer set with source branch, relief, scar, claimants, requested use, future reader, and default author.

Player-readable question:

Who gets to show this replay, and what part of the branch must remain attached?

Beat 2 — Claimants name different exports

At least two claimants propose incompatible uses:

  • sponsor wants sponsor_defense or liability_safe_clip;
  • editor wants editor_checksum or continuity_playback;
  • inspector wants lawful_annex or sealed_proof;
  • fan-public wants public_receipt or raw_branch;
  • management wants management_case or metric_reuse;
  • route claimant wants route_asset_proof.

Each row must state required input, omitted branch or cost, and future route effect.

Beat 3 — Attestation

复盘导出验讫 asks for custodian, proof anchor, consent scope, counter-branch, bridge/cost, and future reader.

Branches:

  • scope_replay: export with scope and visible scar;
  • seal_replay: lawful/archive/inspector-only proof;
  • trade_replay: immediate relief in exchange for faction leverage;
  • expose_replay: public truth with witness and consent cost;
  • quarantine_replay: preserve but block until proof catches up;
  • refuse_export: protect the source but fail the future reader;
  • clean_clip_default: another claimant files first or the player exports a false-clean clip.

Beat 4 — Misattribution or future use

If attestation is missing, underfilled, or clean-clipped, 复盘匣误归属默认 hardens. The future route then reads the capsule as sponsor-only, lawful-only, public-only, editor-smoothed, captured, false-clean, blocked, or recovery-only.

If attestation succeeds, the future reader still pays the scar: scope, bridge, appeal, addendum, protection, extra cost, or narrowed route access.

Branch outcomes

Scoped export route

The replay becomes usable but not universal.

result:
  capsule_state_after: scoped
  relief_any: [route_access_unlocked, replay_capsule_legibility_up]
  cost_any: [future_clearance_cost_up, handler_burden_up]
  future_effect_any: [accepted_with_scope, forbidden_scope_named]

Lawful seal route

The replay survives audit but loses clean public mobility.

result:
  capsule_state_after: sealed | lawful_only
  relief_any: [admissibility_up, witness_exposure_down]
  cost_any: [archive_debt_up, public_receipt_distrust_up]
  future_effect_any: [lawful_only, public_addendum_required]

The replay buys immediate pressure relief and makes future use faction-bound.

result:
  capsule_state_after: traded | sponsor_only | captured
  relief_any: [sponsor_stop_loss_pressure_down, schedule_pressure_down]
  cost_any: [contract_capture_up, source_ambiguity_up]
  future_effect_any: [sponsor_gate_required, route_costlier]

Public exposure route

The replay becomes public proof and creates protection debt.

result:
  capsule_state_after: exposed | public_only
  relief_any: [public_receipt_legitimacy_up, private_capture_blocked]
  cost_any: [witness_exposure_up, consent_debt_up, sponsor_stop_loss_pressure_up]
  future_effect_any: [public_only, protection_required]

Quarantine or refusal route

The replay avoids false-clean use but delays or blocks the future reader.

result:
  capsule_state_after: quarantined | held_private | recovery_only | blocked
  relief_any: [false_clean_replay_down, consent_violation_risk_down]
  cost_any: [schedule_pressure_up, route_delay_up, public_receipt_distrust_up]
  future_effect_any: [proof_required, alternate_proof_required, recovery_only_if_ignored]

Misattribution route

The wrong author hardens the capsule before the player attests it.

result:
  emitted_event: storyteller.event.replay_capsule_misattribution_default.v1
  capsule_state_after: misattributed | captured | false_clean | recovery_only
  future_effect_any: [blocked, costlier, lawful_appeal_required, public_addendum_required, sponsor_gate_required, edit_checksum_required]

Failure and miss states

Missing or mishandling the capsule should create durable consequences:

  • replay_capsule_misattributed
  • capsule_captured_by_sponsor
  • capsule_lawful_only
  • capsule_public_only
  • false_clean_replay_hardened
  • future_reader_unserved
  • route_asset_integrity_down
  • source_scar_visibility_down
  • recovery_only_capsule

Replay evidence shape

storyline_id: storyteller.storyline.replay_export_custody.v1
session_id: replay-export-custody-v1-<timestamp>
seed: <deterministic_seed>
entry_state:
  trigger_kind: state_pressure
  source_branch_result_present: true
  source_branch_has_relief_or_route_access: true
  source_branch_has_scar_or_omitted_cost: true
  export_request_present: true
  claimant_count_min: 2
  future_reader_present: true
offered:
  card: storyteller.card.replay_export_capsule.v1
  rite: storyteller.rite.replay_export_attestation.v1
branches:
  scoped_or_constructive:
    selected_posture: scope_replay | seal_replay | trade_replay | expose_replay | quarantine_replay | refuse_export
    capsule_state_after: <state>
    future_route_effect: <effect>
    counter_deltas: {}
  default_or_miss:
    emitted_event: storyteller.event.replay_capsule_misattribution_default.v1
    capsule_state_after: misattributed | captured | false_clean | recovery_only | blocked
    future_route_effect: <effect>
    counter_deltas: {}

Non-goals

  • Not a tutorial for replay UI.
  • Not a generic save/load system.
  • Not a public recap or stability package duplicate.
  • Not a clean proof export.
  • Not a fixed turn trigger.
  • Not valid unless the replay capsule changes future route availability, cost, custody, or broadcast reality.