Live Floor Egress Bottleneck / 直播现场通行瓶颈线

Live Floor Egress Bottleneck is the next high-value pressure storyline after the current green surface. It targets the physical layer that the recent legal and operational content implies but does not fully force: the crisis cannot be solved until bodies, queues, proof, and route assets physically pass through a finite live-floor bottleneck.

This line is implemented through 直播现场通行瓶颈机制, 直播现场通行瓶颈账本, 直播现场通行分流, and 通行瓶颈默认.

Why this is the strongest next gap

Recent content makes service rows, remedy rows, access captions, emergency power, room occupancy, facility access, and management load executable. The weak seam is that many of these rows still assume the live floor can absorb movement once a right, room, door, or power source is assigned.

This storyline refuses that assumption. A claimant table, fan oxygen line, accessible exit, proof escort, route asset, performer withdrawal, and crew return can all be legally valid while physically incompatible.

The dramatic question is:

Who moves through the bottleneck, who waits in danger, and which future reader refuses the lie that everyone got out cleanly?

State-triggered entry

Open this storyline only when all of the following are visible:

entry_state_required:
  trigger_kind: state_pressure
  source_surface_any:
    - facility_access_lockdown
    - room_occupancy_claim_stack
    - live_floor_crew_load
    - emergency_power_priority
    - access_caption_class_action
    - capacity_notice_service_queue
    - broadcast_capacity_liability
    - fan_oxygen
    - route_asset_custody
    - broadcast_schedule
  egress_node_visible: true
  throughput_limit_visible: true
  flow_claims_min: 2
  support_need_visible_or_explicit_absence: true
  future_reader_or_route_consumes_egress_state: true
  player_response_available: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_crowd_or_notice_count_trigger: true

The line fails if it opens from fixed turn number, fixed day/week interval, chapter quota, raw crowd count, raw notice count, dashboard state, lens health, or generic evacuation aftermath.

Bound content pack

• 直播现场通行瓶颈机制 defines throughput, flow claims, transition rules, default narrator, and future-reader consumption.
• 直播现场通行瓶颈账本 records the egress node, state, throughput, direction pressure, flow claims, selected protected/deferred flow, support, receipt, and future reader.
• 直播现场通行分流 lets the player route accessible exit, safety release, proof escort, stage withdrawal, reverse-flow hold, split flow, sponsor tunnel, or default.
• 通行瓶颈默认 fires or arms when the movement bottleneck is hidden, under-supported, or falsely filed as safe for everyone.

Storyline spine

Beat 1 — The live floor stops being an abstract lane

A crisis points to a concrete node in 第七穹顶设施通行图: stage_threshold, service_corridor_chain, fan_oxygen_gate, ward_air_room, archive_counter_seven, sponsor_bridge_booth, white_glove_checkpoint, cutroom_blackbox, or equivalent.

The node is not only open or closed. It has a throughput limit: one group, one body, wheelchair line, oxygen mask queue, proof bundle only, two escorts, no reverse flow, or silence-limited passage.

Beat 2 — Incompatible flows make movement political

At least two flows claim the same bottleneck:

• fan public or oxygen queue needs safe outflow;
• access-caption readers need a caption-guided exit path;
• performer or protected witness needs to leave camera line;
• proof bundle or route asset needs escort;
• crew needs to return to board or cutroom;
• sponsor package wants private bridge priority;
• claimant public wants entry to the intake table;
• inspector, archive, or security wants a lawful counter or checkpoint hold.

The player must protect one flow and name the deferred or blocked flow.

Beat 3 — Support decides whether movement is real

A protected flow must carry the support it needs: powered door, corridor light, caption notice, oxygen reserve, escort, quiet window, checksum bag, lawful counter, public marshal, or explicit absence.

A flow that moves without support may still arrive, but arrives as contested, hostile, public-only, lawful-only, sponsor-captured, recovery-only, or proof-contaminated.

Beat 4 — The routing rite creates a scar

Run 直播现场通行分流. A valid branch must give immediate relief, visible cost, and future route/readership effect.

Beat 5 — The future reader rejects the clean evacuation story

A later system consumes the egress result:

• 设施通行图机制 reads one-way or captured passages;
• 房间占用认领栈机制 reads unreachable rooms;
• 直播现场班组负荷机制 reads crew return hazard;
• 应急供电优先机制 reads powered-door/corridor-light dependency;
• 无障碍字幕集体机制 reads uncertified accessible exit;
• 播出容量责任级联机制 reads dead air or narrowed slot;
• Fan Oxygen reads queue harm and public oxygen debt.

Branch map

Branch	Immediate relief	Cost/scar	Future state
Accessible exit first	access-caption readers or mobility-limited queue exits with guidance	sponsor/camera/proof flow waits	access receipt, public-only route, class docket pressure
Safety marshal release	largest crowd or oxygen queue exits safely	schedule pressure, security heat, inspection questions	fan oxygen review, public safety receipt
Proof or asset escort	proof, witness, or route asset moves under escort	crew return or public queue degrades	custody reader or route asset maintenance cost
Stage withdrawal	vulnerable performer/body leaves camera line	public claimant entry or sponsor glamour narrows	stage threshold recovery-only or broadcast reality scar
Reverse-flow hold	incoming flow is stopped to keep exit one-way	claimant, sponsor, or crew hostility rises	facility map records corridor one-way scar
Split flow with receipt	multiple flows move partially	confusion and slower support	future dispute has receipt but degraded state
Sponsor tunnel bargain	private route opens for sponsor/camera continuity	public/access/fan resentment and capture attach	sponsor gate, public table, or access class reads capture
Hide bottleneck default	fastest narrator moves first	hidden harm hardens	default event arms review, blockage, or recovery-only state

Counter contract

Every non-default branch must mutate:

counter_deltas_required:
  relief: at_least_one
  cost: at_least_one
  future_reader_or_route_effect: at_least_one

Expected surfaces include egress_harm_risk, crowd_pressure, access_caption_pressure, fan_oxygen_resentment, sponsor_stop_loss_pressure, security_heat, crew_hazard, schedule_pressure, public_safety_legitimacy, route_asset_pressure, proof_contamination_risk, and handler_burden.

Replay evidence expectation

storyline_id: storyteller.storyline.live_floor_egress_bottleneck.v1
session_id: lens-live-floor-egress-bottleneck-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_surface: <source>
  egress_node_visible: true
  throughput_limit_visible: true
  flow_claims_min: 2
  support_need_visible_or_explicit_absence: true
  future_reader_or_route_consumes_egress_state: true
  no_fixed_turn_trigger: true
offered:
  card: storyteller.card.live_floor_egress_ledger.v1
  rite: storyteller.rite.live_floor_egress_routing.v1
branch_result:
  selected_response: accessible_exit_first | safety_marshal_release | proof_or_asset_escort | stage_withdrawal | reverse_flow_hold | split_flow_with_receipt | sponsor_tunnel_bargain | hide_bottleneck_default
  protected_flow: <flow id>
  deferred_or_blocked_flow: <flow id or explicit_absence>
  support_or_absence: <support>
  receipt_or_absence: <receipt>
  egress_node_state_after: <state>
  future_reader_effect: <effect>
  counter_deltas:
    relief: []
    cost: []
    future: []
default_branch:
  event_seen_or_armed: storyteller.event.egress_bottleneck_default.v1 | explicit_absence
  default_narrator: <narrator or explicit_absence>
assertions:
  - entry_is_state_triggered
  - egress_node_and_throughput_visible
  - protected_and_deferred_flows_visible
  - support_receipt_and_future_reader_visible
  - no_universal_safe_exit
  - default_mutates_future_play
  - no_fixed_turn_day_week_raw_count_dashboard_or_lens_health_trigger

Missability and recovery

The storyline is missed when a future route consumes evacuated, cleared, rerouted, or safe exit without creating or reading an egress row.

Missed states include hidden_egress_harm, access_exit_unreceipted, fan_oxygen_queue_hostile, sponsor_tunnel_capture, proof_escort_contested, crew_return_hazard, stage_threshold_recovery_only, and broadcast_capacity_scarred.

Recovery is allowed only through visible cost: late public receipt, access-caption certificate, oxygen review, lawful review, corridor release, sponsor tunnel release, proof re-escort, crew hazard compensation, or recovery-only broadcast slot.

Non-goals

• Not a generic evacuation scene.
• Not a crowd mood counter.
• Not a fixed emergency phase.
• Not raw count expansion.
• Not a replacement for facility access, room occupancy, emergency power, access captions, fan oxygen, or capacity liability.
• Not valid unless egress node, throughput, protected/deferred flows, support, default narrator, deltas, and future reader are all playable.