Storyteller Wiki

Resume Packet Docket / 复盘接手包案卷

4 min read

Resume Packet Docket / 复盘接手包案卷

Resume Packet Docket is the board card for the moment an already-live production state is resumed, handed to another desk, or rebuilt into a finite active hand.

It is not a save-file viewer, a dashboard artifact, or a recap. It is an in-world production packet: the paper tray the producer sees when the crisis floor reopens and the game must decide which live pressure rows are visible now.

Design use

Use this card when a suspended or handed-off state contains more live consequences than the active hand can safely show at once, and at least one hidden row would change a future route, claimant, proof object, or custody reader.

The card exists to prevent a resume packet from laundering old pressure into silence. If a row is omitted, the omission must be explicit and priced.

Required fields

card_id: storyteller.card.resume_packet_docket.v1
resume_packet_id: <stable id>
source_session_id_or_in_world_handoff: <session id, shift handoff, archive tray, producer station, or explicit_absence>
resume_trigger:
  trigger_kind: state_pressure
  handoff_surface: suspended_crisis | producer_station_reopen | desk_transfer | route_recovery_intake | archive_tray_rebuild | equivalent
  no_fixed_turn_trigger: true
packet_owner_or_absence: <producer, archive, inspector, sponsor, editor, fan_public, logistics_carrier, or explicit_absence>
active_hand_capacity:
  visible_slots: <finite hand slot count or implementation equivalent>
  capacity_reason: handler_limit | route_pressure | UI_hand_limit | desk_transfer_limit | crisis_lane_limit | equivalent
rows:
  - row_id: <stable row>
    source_surface: dormant_claim | evidence_carryover | route_loadout | management_compression | pressure_claimant | recap_fragment | transcript_redaction | fan_token | route_asset | equivalent
    source_state_before: protected | route_asset | hostile | captured | false_owner | split_required | recovery_only | contradiction_pending | qualified | default_armed | equivalent
    custodian_or_absence: <custodian or explicit_absence>
    future_reader_or_route: <reader, route, rite, desk, claimant, or explicit_absence>
    visible_in_packet: true | false
    visibility_reason: priority | hidden_by_capacity | hidden_by_sponsor | hidden_by_inspector | hidden_by_editor | hidden_by_archive | hidden_by_public_absence | hidden_by_unclear_source | explicit_absence
    omission_risk_if_hidden: hostile | captured | false_owner | contradiction_pending | recovery_only | blocked | costlier | none
first_action_choices:
  - surface_balanced_packet
  - prioritize_claimant
  - sponsor_safe_packet
  - inspector_first_packet
  - fan_public_warning_packet
  - editor_checksum_packet
  - quarantine_resume
  - accept_hidden_row_default

Row contract

Every row listed on the docket must have a visible state and a future reader, or an explicit absence with a cost.

A valid row can come from:

  • a matured claim that has become relevant;
  • a returned proof that changes current custody;
  • a route loadout conflict;
  • a management compression debt;
  • a default actor conversion row;
  • a recap fragment or transcript that a future reader will cite;
  • a fan token whose scope is not universal;
  • any route asset that is protected, hostile, captured, false-owner, or recovery-only.

Omission register

The docket must contain an omission register whenever any live row is not placed in the visible packet.

omission_register:
  omitted_rows_min: 0
  if_omitted_rows_exist:
    omitted_row_ids: []
    omission_beneficiary: sponsor | inspector | archive | editor | management | fan_public | claimant | blackout_system | explicit_absence
    harmed_reader_or_claimant: <reader, claimant, route asset, public, or explicit_absence>
    future_effect_if_not_reopened: blocked | costlier | hostile | captured | false_owner | recovery_only | contradiction_pending | sponsor_only | lawful_only | public_only

The omission register is not a task list. It is a playable custody row that future content can cite.

Valid packet states

  • balanced_packet — selected rows show relief, cost, and future effect without hiding live defaults.
  • claimant_priority_packet — a claimant row is surfaced first and unselected rows are watchlisted.
  • sponsor_safe_packet — sponsor pressure is reduced while public or access harm becomes explicit.
  • inspector_first_packet — lawful risk is surfaced while public/sponsor/editor rows narrow.
  • fan_public_warning_packet — public harm is surfaced while inspection or sponsor pressure rises.
  • editor_checksum_packet — source safety is surfaced while public or lawful readability narrows.
  • quarantined_packet — hand reconstruction is delayed to prevent false clean resumption.
  • hidden_row_default — a live row is omitted without price and becomes a durable default.

Failure cases

This card fails its design promise if:

  • a resumed state offers a clean hand while hostile, captured, false-owner, recovery-only, or contradiction-pending rows are hidden;
  • the packet does not name the source row and state before;
  • omitted rows have no omission register;
  • capacity or UI hand limits erase pressure without a future effect;
  • the first action can proceed without naming who benefits from the packet’s omissions;
  • the packet is triggered from a fixed turn number, fixed day, raw row count, dashboard state, or lens-health state.

Non-goals

  • Not a save-file UI spec.
  • Not a replay log viewer.
  • Not dashboard or lens governance.
  • Not a generic task queue.
  • Not raw backlog cleanup.
  • Not valid unless the packet changes what current play can see, what hidden rows can later claim, and what future routes accept.

Graph View

Backlinks