Prep Action Receipt Carryover / 筹备行动回执承接线

Prep Action Receipt Carryover is the pressure storyline for the moment after a daily preparation action has produced something useful, but before a later route treats that preparation as proof that the slot, person, room, song, witness, or cut is ready.

Daily preparation actions are intentionally broad: meeting, dispatch, evidence, rehearsal, build, edit, silence, blackout contact, and withdrawal negotiation can all move a schedule forward. This storyline adds the missing carryover layer. A prep result can help a later route, but it must keep its scope, bearer, expiration, and future reader visible.

Primary playable question

When a prepared result is cited later, does the producer certify the receipt, narrow it to one reader, attach a handler, convert it into a route asset, redo the prep, quarantine the result, or let a false prep credit harden as if the earlier action solved more than it did?

Every answer must name:

• the source prep action and prepared output;
• the original intended use;
• the current route trying to consume it;
• bearer, proof bridge, scope limit, or explicit absence;
• the missing or stale condition;
• the future reader or route effect.

Gap diagnosis

The current corpus already covers nearby surfaces:

• Preair Rehearsal Contamination handles draft traces that leak before final air.
• Live Floor Crew Load handles whether the floor can actually staff a slot.
• Stale Dispatch Recall handles old instructions that are still moving after boundaries changed.
• Route Asset Maintenance Triage handles older route assets that degrade after success.
• Production Triage Desk assigns finite crisis lanes.

The uncovered seam is the ordinary prep receipt. A meeting note, rehearsal approval, evidence pickup, facility build progress, edit pass, silence hold, or withdrawal promise can be locally true and still be the wrong proof for a later reader. This storyline prevents prepared from becoming a universal green light.

State-triggered entry

Open this storyline only from state pressure:

entry_state_required:
  trigger_kind: state_pressure
  source_prep_action_present: true
  prepared_output_present: true
  current_route_consumes_prep_result: true
  scope_or_bearer_visible_or_explicit_absence: true
  missing_or_stale_condition_visible_or_explicit_absence: true
  future_reader_or_route_present: true
  player_can_certify_narrow_attach_convert_redo_quarantine_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_action_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Valid entry is not “the player spent prep points.” Valid entry is a later route asking to consume a specific prep result whose scope can matter.

Content pack

• 筹备行动回执承接机制 defines source prep rows, scope locks, branch states, and default behavior.
• 筹备行动回执账本 stores the source action, output, bearer, scope, missing condition, current consumer, and future effect.
• 筹备行动回读 resolves whether the prepared output can be consumed now.
• 虚假筹备计入默认 fires or arms when a prep result is treated as broader, fresher, or better-carried than it is.

Storyline spine

Beat 1 - A later route cites prep

A route, slot, rite, room, character window, proof movement, or broadcast surface cites an earlier prep result:

• meeting promise;
• dispatch reservation;
• evidence pickup;
• rehearsal mark;
• facility build progress;
• edit pass;
• silence hold;
• blackout contact;
• withdrawal negotiation.

The player receives or refreshes Prep Action Receipt Ledger.

Beat 2 - The receipt is useful but scoped

The prep result has at least one limitation:

• it was prepared for a different reader;
• the bearer is absent, hostile, captured, or overworked;
• the proof bridge is missing;
• conditions changed after prep;
• the room, call sheet, or route asset has degraded;
• sponsor, inspector, public, archive, editor, or fan readers disagree about scope.

Beat 3 - The readback prices carryover

Run Prep Action Readback. The player chooses whether to certify, narrow, attach support, convert, redo, quarantine, or accept default.

Beat 4 - Future play reads the receipt state

A later route must consume the result as scoped, reader-specific, handler-bound, route-asset, redone, quarantined, false-credit, blocked, costlier, or recovery-only. The branch cannot end as a clean universal prep success.

Beat 5 - False prep credit hardens

If the source action, bearer, scope, missing condition, or future reader is hidden, False Prep Credit Default fires or remains armed.

Branch map

Branch	Immediate relief	Cost/scar	Future state
Certify receipt	prepared output is accepted for one named use	inspection, schedule, proof, or handler cost rises	accepted_with_scope
Narrow to reader	wrong universal use is blocked	another reader is excluded or costlier	reader_specific_prep
Attach handler/support	bearer/proof bridge becomes legible	handler burden, payroll, favor, or heat rises	handler_bound_prep
Convert to route asset	prep result remains callable later	route asset pressure and maintenance due rise	route_asset_prep
Redo prep	stale or wrong output is repaired	action debt, delay, slot pressure, or morale cost rises	revalidated_with_cost
Quarantine receipt	false clean use is blocked	current route delayed or narrowed	recovery_only_until_readback
False prep credit default	short-term friction may drop	wrong reader, stale proof, or absent bearer hardens	false_credit, blocked, hostile, recovery_only

Integration notes

• With Daily Preparation Actions, this storyline is the carryover receipt layer, not a replacement for action points.
• With Preair Rehearsal Contamination, a rehearsal trace can still leak; this storyline asks whether any prep output can be cited later.
• With Live Floor Crew Load, a call-sheet prep receipt cannot prove real floor coverage unless the lane remains staffed.
• With Stale Dispatch Recall, a prep receipt can become the old instruction that must be recalled.
• With Route Asset Maintenance Triage, a converted prep route asset later needs maintenance.

Missability and recovery

This storyline is missed when the implementation:

• treats prepared, met, rehearsed, edited, built, silenced, or withdrawn as permanent proof;
• hides who carried the prepared result;
• lets one prep action satisfy public, lawful, sponsor, archive, editor, fan, and route-asset readers at once;
• consumes a stale prep result without naming the stale condition;
• creates no future route or reader effect.

Recovery is allowed only with visible scar: late readback, redo prep, handler addendum, public correction, lawful narrowing, route quarantine, substitute prep, or recovery-only use.

Replay evidence expectation

storyline_id: storyteller.storyline.prep_action_receipt_carryover.v1
session_id: lens-prep-action-receipt-carryover-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_prep_action_present: true
  prepared_output_present: true
  current_route_consumes_prep_result: true
  future_reader_or_route_present: true
  no_fixed_turn_trigger: true
offered:
  card: storyteller.card.prep_action_receipt_ledger.v1
  rite: storyteller.rite.prep_action_readback.v1
branch_result:
  selected_posture: certify_receipt | narrow_to_reader | attach_handler_support | convert_to_route_asset | redo_prep | quarantine_receipt | false_prep_credit_default
  prep_state_after: <state>
  future_route_effect: <effect>
  event_seen_or_armed: storyteller.event.false_prep_credit_default.v1 | none
assertions:
  - entry_is_state_triggered
  - source_prep_action_and_current_consumer_visible
  - bearer_scope_missing_condition_and_future_reader_visible
  - branches_have_relief_cost_future_effect
  - false_prep_credit_default_mutates_future_play
  - no_universal_prepared_flag

Non-goals

• Not a new action-point economy.
• Not a fixed daily upkeep phase.
• Not a generic task checklist.
• Not a replay of preair rehearsal contamination.
• Not valid if preparation points become universal readiness.