Live Floor Crew Load / 直播现场班组负荷线

Live Floor Crew Load is a pressure-system storyline for what happens after Storyteller’s ruling surfaces have produced something that still has to go live. The player can win an archive ruling, stabilize a quote, protect a witness, or price a slot, but the broadcast floor can still fail if the call sheet is unsafe.

This storyline expands the corpus away from the recent archive / quote / custody cluster. It adds a grounded management question: can the crew actually staff the slot, and what does refusal do to the route?

The storyline binds 直播现场班组负荷机制, Call-Sheet Captain, Call Sheet Load Ledger, Call Sheet Reassignment, and Crew Refusal Default.

Playable promise

When a live or near-live operation becomes important, the game must surface real floor coverage. The player chooses whether to rest, rotate, pay, trust, publicize, force, silence, or accept absence. Each choice changes crew trust, schedule pressure, blackout risk, slot scope, and future route access.

The floor is not decoration. It can become a route ally, a hostile leak, a blackout scar, or the reason an otherwise lawful slot cannot safely air.

State-triggered entry

Open this storyline when all of the following are true:

  1. a slot or operation must be performed by floor crew;
  2. at least one crew lane is thin, exhausted, borrowed, coerced, wrong, absent, or contested by another active crisis;
  3. the operation affects schedule pressure, blackout risk, broadcast reliability, audience stability, person safety, proof movement, route-asset movement, or public legitimacy;
  4. the actual Du Mian card, handler, branch-cost surface, response, selected runner, scope-only board row, and remaining exact rite inputs can be represented;
  5. the player can explicitly choose silence_warning or accept_absence to arm a non-neutral default; passive ignore does not auto-trigger one;
  6. no entry condition depends on a fixed turn number, chapter quota, day interval, raw lens count, or governance dashboard state.

Content pack

Mechanism

NPC / route asset

  • Call-Sheet Captain is the missable crew-facing NPC who can reveal, stabilize, publicize, or leak the real call sheet.

Card

  • 通告单负荷账本 records slot, lane rows, captain state, coverage, refusal risk, blackout risk, assignments, and defaults.

Rite

  • 通告单重派 resolves the strict eleven-slot packet: the selected runner lane, the actual card.du_mian_call_sheet_captain, the production-desk handler, a branch-specific cost surface, the selected response, the unselected board row as a scope-only comparator, the harmed reader, and the future reader. The board row is never mutated as if it were selected.

Event

  • 班组拒签默认 arms only when the player explicitly selects silence_warning or accept_absence; passive inactivity is not an engine trigger.

Storyline spine

Beat 1 — A slot needs bodies, not just permission

A live broadcast, correction slot, memorial handoff, security clearance, emergency patch, public testimony, or rehearsal cannot proceed safely on legal permission alone. The call sheet becomes state-relevant.

Create or refresh a ledger row:

crew_story_entry:
  source_slot: <slot_or_operation_id>
  slot_family: live_broadcast | rehearsal | security_clearance | memorial | correction | emergency_patch | public_testimony | equivalent
  affected_future_route: <route_or_slot_effect>
  pressure_reason: exhaustion | borrowed_lane | coerced_lane | wrong_team | absent_lane | blackout_risk | refusal_risk | equivalent
  trigger_kind: state_pressure
  no_fixed_turn_trigger: true

Beat 2 — The real call sheet surfaces

Call Sheet Load Ledger shows crew lanes and their coverage states. The current rite accepts only the actual card.du_mian_call_sheet_captain; her post-choice state may become truthful captain, neutral captain, management proxy, public safety witness, suppressed voice, hostile leak, skeleton lead, or missed captain. accept_absence is the player’s deliberate disposition after assigning her, not an explicit-absence captain input.

Required row shape:

crew_lane_row:
  lane: camera | board | runner | medic | security_floor | stage | edit_floor | audience_gate | oxygen_floor | equivalent
  coverage_before: rested | thin | exhausted | borrowed | coerced | absent | wrong_team
  refusal_risk_before: none | low | armed | live
  blackout_risk_before: none | low | armed | live
  assigned_from: <handler_or_room_or_absence>
  risk_if_explicitly_unworked: <default_actor_and_state>

Beat 3 — Reassign or accept scar

Offer Call Sheet Reassignment. The player chooses among rest/rotate, overtime pay, trust/recruit captain, publicize safety, management proxy, force skeleton crew, silence warning, or accept absence.

The rite must preserve all eleven exact assignments. The selected lane is storyteller.card.call_sheet_runner_lane_input.v1; the unselected board card is scope-only; storyteller.card.call_sheet_branch_cost_surface.v1 records the branch-specific accepted cost without claiming every branch paid overtime; and card.du_mian_call_sheet_captain is the only captain input. A high-status handler cannot replace real crew coverage.

Beat 4 — Crew response changes future route

Every branch must mutate the slot and future play.

Valid outcomes include:

  • slot_narrowed_for_safety
  • overtime_covered
  • floor_crew_advocate
  • public_safety_witness
  • skeleton_crew_scar
  • suppressed_floor_voice
  • hostile_call_sheet_leak
  • blackout_risk_armed
  • crew_refusal_default
  • route_recovery_only

wrong_team_assigned remains a broader crew-pressure state, but it is not a current terminal option of event.crew_refusal_default.

When rite.call_sheet_reassignment resolves pay_overtime for Lin Qiao’s runner lane at slot.live.memorial_correction_floor_01, it creates one bounded second-hop receipt. Call-Sheet Addendum Afteruse Receipt governs any later attempt to stretch that historical staffing/pay row into current availability, fresh consent, sponsor delivery, or broadcast authority; it does not reopen the immediate crew-coverage decision.

Beat 5 — Aftermath becomes route material

The outcome feeds existing systems:

Branch map

BranchImmediate reliefCost/scarFuture state
Rest / rotaterefusal and blackout risk falldelay, narrower slot, other lane load, schedule costsafer_but_delayed, route_costlier
Pay overtimeslot can air with coverageovertime debt, sponsor capture, staff fatiguedebt_due, future refusal risk
Trust/recruit captainhidden load becomes assignabledeniability lost, inspection/schedule heatfloor_crew_advocate, safer route unlocked
Publicize safetycrew trust and legitimacy risesponsor pressure, audit heat, public-only/lawful-only routepublic_safety_witness
Force skeleton crewcancellation pressure dropsblackout, injury, fatigue, hostile leak riskskeleton_crew_scar, recovery_only
Silence warningofficial slot stays clean brieflysuppressed voice, hostile leak, staff distrusthidden_refusal_armed
Accept absenceassigned Du Mian is deliberately recorded as missedone of four exact default actors resolves the floor failurecrew_refusal_default, blocked/costlier/recovery-only

Missability

The storyline is missed when the player repeatedly treats broadcast labor as implicit after solving legal, archive, custody, sponsor, quote, or edit pressure.

Missed states:

  • missed_by_clean_ruling
  • ledger_hidden
  • suppressed_floor_voice
  • hostile_call_sheet_leak
  • wrong_team_assigned
  • blackout_skeleton_default
  • route_recovery_only

Recovery is possible only through visible cost: pay owed overtime, accept a narrower rebroadcast, sacrifice a glamour slot, publish the safety issue, restore 杜眠’s trust, or accept a blackout scar.

Failure states

The storyline should create pressure without becoming a universal game-over:

  • crew_refusal_default: the floor refuses or delays the official slot.
  • blackout_skeleton_default: the slot airs but produces blackout-prone scar.
  • hostile_call_sheet_leak: suppressed warning becomes public/audit-facing.
  • public_safety_route_only: the route survives only as public safety testimony.
  • lawful_safety_hold: audit/law protects crew but narrows broadcast options.

wrong_team_misair can still exist elsewhere in the world model, but neither it nor security_floor is an executable branch of the current refusal-default event.

Replay evidence expectation

A correct implementation proves at least one stabilizing branch and one refusal/skeleton/default branch from state pressure.

storyline_id: storyteller.storyline.live_floor_crew_load.v1
session_id: lens-live-floor-crew-load-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_slot: <slot_or_operation_id>
  pressured_crew_lane_present: true
  actual_du_mian_card_present: true
  future_route_or_slot_effect_present: true
  no_fixed_turn_trigger: true
offered:
  card: card.call_sheet_load_ledger
  rite: rite.call_sheet_reassignment
branch_runs:
  stabilizing_branch:
    response: rest_rotate | pay_overtime | recruit_captain | publicize_safety
    selected_lane: storyteller.card.call_sheet_runner_lane_input.v1
    unselected_board: storyteller.card.call_sheet_board_lane_unselected.v1
    unselected_board_semantics: scope_only
    branch_cost_surface: storyteller.card.call_sheet_branch_cost_surface.v1
    lane_state_after: <state>
    cost_state: <state>
    future_route_effect: <effect>
  refusal_or_skeleton_branch:
    response: silence_warning | accept_absence
    event_seen_or_armed: event.crew_refusal_default
    default_actor: crew_refusal | sponsor_schedule | hostile_leak | absent_captain
    default_state: slot_delayed | blackout_skeleton_default | public_safety_leak | slot_blocked
    future_route_effect: <effect>
assertions:
  - entry_is_state_triggered
  - ledger_records_slot_lanes_captain_assignments_and_defaults
  - rite_consumes_or_mutates_real_floor_coverage
  - success_has_cost
  - default_records_one_exact_actor_outcome_pair_deltas_and_route_effect

Non-goals

  • Not raw content count expansion.
  • Not a fixed-turn incident.
  • Not a governance dashboard.
  • Not a generic workplace policy page.
  • Not a full staff simulator.
  • Not a replacement for archive custody, quote recall, route assets, sponsor pressure, or production triage.
  • Not valid if a clean ruling, sponsor payment, edit patch, or legal order can erase floor coverage.