Preair Rehearsal Contamination / 预播排练污染线
Preair Rehearsal Contamination is a pressure-system storyline for the moment before a planned broadcast becomes reality, when a rehearsal trace starts acting like a promise, proof, receipt, refusal, lawful fact, sponsor preview, editor cut, or public leak.
The current corpus is strong on what happens after reality is broadcast: drift can be audited, package authorship can be contested, derivative copies can develop afterlives, claimants can be briefed in dangerous order, and factions can spend finite leverage. The missing pressure seam is earlier: the game can prepare a rite without deciding whether prep has already contaminated the world.
This storyline makes preair traces dangerous and playable.
Primary playable question
When a not-yet-aired rehearsal trace can be cited before final broadcast, does the player seal it as draft, air a corrected boundary, let sponsor or inspector lock it, rewrite it through cutroom, admit public witness, quarantine the route, or let the trace leak into false rehearsal reality?
Every answer must change:
- the rehearsal trace state;
- the trace holder’s leverage;
- final-air integrity;
- at least one future route, slot, proof, package, public receipt, or route asset reader.
Why this is the next useful expansion
Existing green surfaces already cover nearby but different problems:
- 播出实在漂移审计 handles contradiction after reality has been aired.
- 播出资产来源后生线 handles derivative copy pressure after public or institutional asset use.
- 稳播包装队列线 handles package authorship after a crisis becomes packageable.
- 认领告知顺序线 handles who learns first.
- 派系承诺账本 handles finite faction leverage.
The new gap is not notice, copy afterlife, or package authorship. It is draft contamination: assignments made during rehearsal can be mistaken for a broadcasted fact before the official version exists.
Bound content pack
This storyline binds:
State-triggered entry
Open this storyline when all are true:
entry_state:
trigger_kind: state_pressure
planned_broadcast_or_rite_present: true
rehearsal_trace_present: true
authoritative_broadcast_not_yet_resolved: true
trace_holder_present: true
claimants_min: 2
future_reader_present: true
player_can_set_boundary_or_record_default: true
no_fixed_turn_trigger: true
no_fixed_day_or_week_trigger: true
no_raw_count_trigger: trueValid source surfaces include:
- a rite assigned but not yet aired;
- a scratch cut before final cut;
- sponsor preview wording;
- inspector-safe blocking;
- stage mark or live-floor call sheet;
- artist refusal rehearsal;
- witness protection rehearsal;
- fan-door recording;
- pirate relay echo;
- AI continuity memory;
- route-asset test handoff.
Storyline spine
Beat 1 — A rehearsal trace becomes citable
A planned broadcast has not yet resolved, but a trace exists. Someone can hold it, quote it, suppress it, or confuse it with the final version.
The player receives 预播排练案卷. The docket must name the planned broadcast, the trace, the holder, the apparent claim, the conflict with final intent, and the future reader.
Beat 2 — Two claimants want incompatible boundaries
The trace is not dangerous unless at least two claimants want different boundaries.
Examples:
- sponsor wants preview wording treated as a promise;
- inspector wants blocking notes treated as lawful fact;
- editor wants scratch cut treated as safe continuity;
- fan public wants rehearsal proof admitted to block private capture;
- artist or witness wants refusal rehearsal preserved;
- production wants the trace sealed until final airing;
- pirate relay wants to publish first.
Beat 3 — The player assigns containment
The player opens 预播排练收束.
The rite must name:
- source rite or scene;
- planned broadcast version;
- rehearsal trace;
- trace holder;
- trace claim;
- conflict with final intent;
- selected boundary;
- final-air carrier or absence;
- proof bridge or absence;
- counterclaimant or absence;
- accepted cost;
- future reader.
Beat 4 — Boundary changes future play
The result must not be a flavor label. It changes later route acceptance.
Valid future effects include:
- final airing requires boundary note;
- sponsor-only preview is citable;
- lawful-only hold blocks public use;
- editor checksum is required for future proof;
- public-only witness admission demands lawful bridge;
- route is quarantined until containment;
- false rehearsal reality captures, blocks, or surcharges a future route.
Beat 5 — Leak/default becomes visible
If the docket is hidden, proof bridge absent, trace holder unnamed, final-air carrier absent, or one claimant cites first, 排练痕迹泄漏 fires or is armed.
The event must name the leak vector, capturing reader, harmed claimant, state before/after, and future route effect.
Branch map
| Branch | Relief | Cost | Future route effect |
|---|---|---|---|
| Seal draft | contamination and false reality fall | schedule, proof burden, distrust, handler load rise | final air requires boundary note |
| Air corrected version | drift falls, public receipt can improve | sponsor pressure, inspection heat, cutroom pressure, churn rise | corrected airing becomes required bridge |
| Sponsor preview lock | budget/slot/sponsor pressure improves | contract capture, preemption, public distrust rise | sponsor-only or public route costlier |
| Inspector hold | false use blocked, custody clarity improves | inspection heat, bureau debt, schedule pressure rise | lawful-only until airing |
| Editor checksum rewrite | continuity and legibility improve | edit debt, source ambiguity, raw-proof cost rise | checksum required later |
| Public witness admission | private capture blocked, legitimacy improves | witness exposure, panic, sponsor pressure, pirate heat rise | public-only until lawful bridge |
| Quarantine | false unlock blocked | route delay, missed pressure, churn rise | route requires containment or recovery |
| Default leak | immediate cost may be avoided | contamination, drift, preemption, panic, heat rise | route captured, blocked, costlier, or recovery-only |
Character and faction hooks
- Shen Luo can negotiate sponsor preview lock, but contract capture and future public distrust rise.
- Han Yanshuang can attach lawful hold, but inspection heat or bureau debt rises.
- Baiya can convert scratch trace into checksum boundary, but edit debt and source ambiguity rise.
- Yu Lan can defend public witness admission, but witness exposure and public panic become live.
- Sponsor, inspector, editor, fan public, artist, witness, pirate relay, production, and blackout system can all become trace holders or capturing readers.
Counter contract
Every branch must mutate at least three counters or durable states. At least one must be relief, one cost, and one future-route or broadcast-reality effect.
Primary surfaces:
rehearsal_contaminationfalse_rehearsal_realitytrace_holder_leveragefinal_air_integrityreality_driftcontinuity_hazardpublic_receipt_legitimacypublic_receipt_distrustsponsor_stop_loss_pressuresponsor_preemptioncontract_captureinspection_heatbureau_favor_debtedit_debtsource_ambiguitywitness_exposurepublic_panicpirate_heatschedule_pressureroute_delayfuture_route_acceptance
Missability and recovery
This storyline is missed when implementation:
- treats rehearsal prep as harmless until final broadcast;
- lets sponsor preview, inspector blocking, editor scratch cut, or fan recording count as final proof with no boundary;
- hides trace holder or future reader;
- has no default leak when a claimant cites first;
- offers only a clean final-air branch;
- triggers from fixed turn, day, week, chapter, raw count, or lens health.
Recovery is allowed only with scar:
- publish boundary note after sponsor preview capture;
- file lawful addendum after public witness admission;
- air corrected version after leak and accept churn;
- release checksum after scratch-cut source ambiguity;
- quarantine route until trace holder is named;
- protect artist or witness after rehearsal exposure;
- accept recovery-only route asset after false rehearsal reality hardens.
Replay/session evidence shape
storyline_id: storyteller.storyline.preair_rehearsal_contamination.v1
session_id: lens-preair-rehearsal-contamination-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
trigger_kind: state_pressure
planned_broadcast_or_rite_present: true
rehearsal_trace_present: true
authoritative_broadcast_not_yet_resolved: true
trace_holder_present: true
claimants_min: 2
future_reader_present: true
no_fixed_turn_trigger: true
source:
source_rite_or_scene: <id>
planned_broadcast_version: <version>
rehearsal_trace_kind: <kind>
trace_holder: <holder>
trace_claim: <claim>
conflict_with_final_intent: <conflict>
offered:
card: storyteller.card.preair_rehearsal_docket.v1
rite: storyteller.rite.preair_rehearsal_containment.v1
branch_runs:
contained_branch:
selected_boundary: seal_draft | air_corrected | sponsor_preview_lock | inspector_hold | editor_checksum_rewrite | public_witness_admission | quarantine
state_before: <docket state>
state_after: <docket state>
final_air_state_after: <state>
future_route_effect: <effect>
counter_deltas:
relief: []
cost: []
future: []
leak_branch:
event_seen_or_armed: storyteller.event.rehearsal_trace_leak.v1
leak_vector: <vector>
capturing_reader: <reader>
harmed_reader_or_claimant: <claimant>
state_after: trace_leaked | false_rehearsal_reality | rehearsal_recovered_with_scar
future_route_effect: <effect>
assertions:
- entry_is_state_triggered
- trace_holder_visible
- rehearsal_trace_not_interchangeable_with_final_air
- claimants_have_incompatible_boundaries
- containment_rite_assignable
- branches_diverge_by_state_cost_and_future_reader
- default_leak_mutates_future_route
- no_fixed_turn_trigger
- no_fixed_day_or_week_trigger