Call Sheet Amendment Collision / 通告单改签碰撞线

Call Sheet Amendment Collision is the pressure storyline for a late change to the official call sheet after another system has already started reading the schedule as truth.

The live-floor line asks whether the floor is staffed. Missing roll-call asks whether the expected person can be accounted for later. This storyline sits between them: it asks whether an amendment to who should be present, excused, reassigned, shielded, or delayed is visible before a future route consumes the wrong version.

Playable question

When an official call sheet changes after assignments are already in motion, does the producer:

• certify the amendment and accept delay;
• publish a countercopy for the affected reader;
• route the change through lawful or safety authority;
• rotate the lane and preserve proof of the substitution;
• quarantine the amendment until contradictions are priced;
• accept a scarred absence;
• let a silent amendment become the default version?

Every answer must change the amended subject or lane and at least one future reader.

State-triggered entry

Open this storyline only from state pressure:

entry_state_required:
  trigger_kind: state_pressure
  source_call_sheet_or_amendment_visible: true
  official_call_sheet_claim_visible: true
  proposed_or_hidden_amendment_visible: true
  expected_subject_or_lane_visible: true
  amendment_authority_or_absence_visible: true
  affected_reader_visible: true
  later_reader_consumes_amendment: true
  future_route_consumes_amendment_state: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_staff_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Do not open the line because a numbered turn, shift boundary, dashboard state, or generic upkeep phase arrived.

Bound content pack

• 通告单改签碰撞机制 defines amendment rows, authority states, reader conflicts, branch families, default payload, and future-route effects.
• 通告单改签账本 records the source call sheet, proposed amendment, expected subject or lane, authority, later reader, state after, and future route.
• 通告单改签听证 resolves certify, countercopy, lawful delay, rotate, quarantine, scar, or default.
• 静默通告单改签默认 fires when the hidden amendment becomes the version future systems read.
• Call Sheet Amendment Collision Lens observes branch reachability and default mutation.

Storyline spine

Beat 1 - A clean call sheet receives a late change

A slot, lane, witness, route asset, safety role, proof carrier, or performer assignment changes after earlier systems accepted the call sheet.

Examples:

• a camera lane is replaced after the public proof frame was promised;
• a medic lane is borrowed by an oxygen crisis after the slot was certified safe;
• a route asset carrier is moved to a different door after custody receipt;
• a witness is excused from public roll-call after access caption already prepared their line;
• a sponsor-safe substitute is inserted after a public package was chosen;
• a stage cue owner changes after blackout prevention assigned the board.

Beat 2 - The amendment ledger opens

Create Call Sheet Amendment Ledger. It must preserve both the previous official version and the amended version.

amendment_row:
  source_call_sheet: <slot_or_operation_id>
  official_call_sheet_claim: staffed | safe | legally_ordered | sponsor_paid | archive_cleared | editor_ready | public_promised | equivalent
  amendment_record: late_substitution | excused_absence | lane_rotation | authority_override | safety_hold | sponsor_insert | proof_carrier_switch | equivalent
  expected_subject_or_lane: <person_lane_asset_or_explicit_absence>
  authority_or_absence: du_mian | safety_marshal | inspector | sponsor | producer | archive | public_receipt | explicit_absence | equivalent
  later_reader: broadcast_schedule | live_floor | missing_roll_call | route_asset_reader | access_caption | fan_public | sponsor | archive | equivalent
  amendment_state_after: certified | public_countercopy | lawful_delay | rotated_with_receipt | quarantined | scarred_absence | silent_default_ready
  future_reader_or_route: <future consumer>

Beat 3 - The player prices the contradiction

Offer Call Sheet Amendment Hearing. A famous handler, sponsor, or archive order cannot erase the amendment. If the authority is absent, the row must say explicit_absence and route toward scar, quarantine, or default.

Beat 4 - Future readers consume the amended version

The branch must decide which version future play reads:

• original call sheet with a visible scar;
• certified amendment with delay;
• public countercopy;
• lawful or safety hold;
• rotated lane with receipt;
• quarantined amendment;
• silent default captured by another reader.

Beat 5 - The default becomes a false schedule fact

If ignored, Silent Call Sheet Amendment Default records who narrates the hidden change and what future route is now costlier, blocked, hostile, or recovery-only.

Branch map

Branch	Immediate relief	Cost/scar	Future state
Certify amendment	future reader sees the changed assignment	delay, inspection heat, schedule pressure	certified_with_delay, route_costlier
Publish countercopy	affected reader can contest the official sheet	sponsor/public/audit pressure	public_countercopy_required
Lawful or safety delay	unsafe or unserved change cannot silently pass	lawful-only route, delay, bureau debt	lawful_delay, safety_hold
Rotate lane with receipt	slot may continue with substitution proof	other lane fatigue, proof burden	rotated_with_receipt
Quarantine amendment	contradiction cannot contaminate canon	route blocked, archive burden	quarantined, recovery_required
Accept scarred absence	false clean amendment blocked	panic, route narrowing, ending scar pressure	scarred_absence
Silent default	fastest path keeps sheet clean briefly	hidden change hardens as false schedule fact	silent_default, blocked/costlier/recovery-only

No branch may make a late amendment acceptable to every schedule, floor, public, lawful, sponsor, archive, access, and route-asset reader at once.

Missability and recovery

The storyline is missed when future systems consume staffed, safe, served, present, excused, carrier switched, or lane rotated without recording the amendment row and its authority or explicit absence.

Recovery requires visible cost: public countercopy, lawful delay, safety hold, rotated receipt, route-asset quarantine, missing roll-call reconciliation, public contrition, or a scarred ending audit.

Replay evidence expectation

storyline_id: storyteller.storyline.call_sheet_amendment_collision.v1
session_id: lens-call-sheet-amendment-collision-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_call_sheet_or_amendment_visible: true
  expected_subject_or_lane_visible: true
  amendment_authority_or_absence_visible: true
  later_reader_consumes_amendment: true
  future_route_consumes_amendment_state: true
  no_fixed_turn_trigger: true
offered:
  card: storyteller.card.call_sheet_amendment_ledger.v1
  rite: storyteller.rite.call_sheet_amendment_hearing.v1
branch_result:
  selected_posture: certify_amendment | publish_countercopy | lawful_delay | rotate_lane_with_receipt | quarantine_amendment | accept_scarred_absence | silent_amendment_default
  amendment_state_after: <state>
  future_reader_or_route_effect: <effect>
  counter_deltas:
    relief: []
    cost: []
    future: []