Emergency Power Priority / 应急供电优先线

Emergency Power Priority is a cross-crisis storyline about the moment when the Seventh Dome has enough emergency power to keep some reality alive, but not all of it.

The player is not asked to “avoid blackout” in the abstract. They must decide whether the live board, stage lights, relay, oxygen pumps, archive cabinet, security doors, cutroom, fan gate, corridor lights, or proof scanner keeps power. The losing surface becomes part of the world: someone cannot pass a door, a proof route loses cold-chain integrity, a stage body becomes unrecognizable, a fan oxygen pump is shed, or a sponsor meter files the result as property.

This storyline is implemented through 应急供电优先机制, 应急供电账本, 应急供电优先分配, and 供电削减默认.

Story role

Recent Storyteller content makes legal, custody, claimant, capacity, management, crew, and remedy pressure executable. This storyline adds the physical production constraint those pages imply but do not fully express: electricity has a source, a load, a switch, and a default actor.

Its dramatic question is:

Which part of reality stays powered, and who pays for the surface that goes dark?

Entry promise

Open this storyline from state pressure when:

• a blackout, capacity collision, facility route, live floor operation, fan oxygen obligation, archive proof route, or schedule contract depends on finite emergency power;
• at least two powered surfaces cannot be kept fully powered together;
• a priority decision can change future route access, schedule state, public safety, archive integrity, sponsor capture, oxygen liability, or broadcast reliability;
• the game can offer an assignment instead of silently choosing a default;
• the trigger is not a fixed turn count, day interval, chapter quota, dashboard state, or raw page-count target.

Exact runtime contract

The runtime-backed storyline uses one one-shot nine-card assignment surface. Every slot is required, accepts only the named card, and the assigned card must be present in hand.

Slot	Exact runtime card
ledger	storyteller.card.emergency_power_ledger.v1
power_source	storyteller.card.emergency_power_source.v1
protected_surface	storyteller.card.emergency_power_protected_surface.v1
shed_surface	storyteller.card.emergency_power_shed_surface.v1
priority_claim	storyteller.card.emergency_power_priority_claim.v1
handler	storyteller.card.emergency_power_handler.v1
support	storyteller.card.emergency_power_support.v1
future_reader	storyteller.card.emergency_power_future_reader.v1
default_risk	storyteller.card.emergency_power_default_risk.v1

storyteller.rite.emergency_power_priority_allocation.v1 exposes exactly eight stable branch IDs. Each branch produces exactly one branch flag, one state flag, and one future-route flag:

Branch ID	Exact state after	Exact future effect
certify_priority	priority_certified	power_priority_certificate_required
load_shed	deliberate_load_shed	shed_surface_recovery_required
split_power	split_power_degraded	degraded_power_reader_required
borrow_generator	borrowed_power_claim_attached	generator_claim_maturity_due
narrow_slot	low_power_slot_narrowed	slot_contract_reads_power_scope
public_safety_hold	public_safety_hold_visible	public_or_lawful_power_notice_required
overdraw_anyway	overdraw_default_pending	hidden_trip_recovery_pending
default_selects	priority_default_pending	default_actor_power_disposition_pending

Only choice indexes 6 and 7 (overdraw_anyway and default_selects) arm all four common pending flags:

• emergency_power.default_pending
• event.power_shed_default.armed
• future_route.power_shed_recovery_pending
• power_reality.false_clean_all_powered_claimed

The other six choices clear those flags and cannot reach the default event. Skipping or underfilling the rite does not invent a runtime default: all nine exact cards must first be assigned, then the player must explicitly choose index 6 or 7.

storyteller.event.power_shed_default.v1 exposes exactly eight terminal repairs:

Terminal ID	Exact state after	Exact future effect
governor_trip	governor_load_trip	tripped_surface_recovery_only
sponsor_meter_capture	sponsor_glamour_priority	oxygen_or_public_power_restitution_required
security_grid_lock	security_route_lock	facility_access_recovery_required
ward_reserve_priority	oxygen_preserved_slot_shed	narrowed_broadcast_reader_required
archive_freezer_priority	archive_cold_chain_preserved	lost_live_surface_addendum_required
blackout_fold	blackout_fold_recovery_only	blackout_recovery_route_required
public_queue_priority	public_feed_priority	lawful_or_archive_delay_reader_required
borrowed_source_claim	lender_power_claim_attached	generator_claim_maturity_reader_required

Every terminal clears the four pending flags while preserving its terminal state and future-reader restriction. The allocation rite is one-shot; recovery consumes the terminal scar through capacity liability, blackout residue, facility access, oxygen restitution, slot narrowing, archive addendum, or borrowed-generator claim maturity and never reopens the same rite.

Local authority boundary

All runtime and public objects are source: storyteller and localAuthorityOnly: true. They may set only these local claims true:

• recordsFinitePowerPriorityOnly
• preservesNamedSourceProtectedAndShedSurface
• preservesDefaultActorAndFutureReader
• requiresVisibleLosingSurface

They must keep these authority claims false: grantsConsent, grantsLegalValidity, grantsWaiver, grantsSettlement, grantsRouteClearance, grantsArchiveRelease, grantsProofTruth, grantsSponsorAuthority, grantsFanAuthority, grantsInspectorAuthority, grantsEditorAuthority, grantsProducerLicense, grantsGeneratorOwnership, grantsInfinitePower, grantsCleanAllPoweredState, grantsFutureReuseAuthority, and grantsUniversalBroadcastAuthority.

Core cast surfaces

This storyline can be entered by any crisis that physically consumes power.

Surface	Story use	Typical pressure
live_board	The broadcast can still cut, switch, mute, and recover.	If shed, dead air or wrong-feed reality appears.
stage_lights	The body on stage remains visible and safe.	If shed, the performer becomes misread, injured, or sponsor-deglamorized.
relay	A lawful, public, pirate, or route relay remains connected.	If shed, the channel is captured or the route becomes silent.
oxygen_pumps	Ward, audience, or fan oxygen is kept alive.	If shed, oxygen debt or public harm becomes durable.
archive_cabinet	Proof cold-chain and archive integrity remain stable.	If shed, checksum drift and custody challenge appear.
security_doors	Doors and controlled passages keep power.	If shed, routes lock open/closed or security claims default.
fan_gate	The public-facing queue feed remains safe.	If shed, crowd pressure or fan resentment rises.
cutroom	Edit patching and redaction remain possible.	If shed, blackbox ambiguity or edit debt rises.
proof_scanner	Lawful proof can still be admitted.	If shed, lawful route blocks or appeal residue rises.

Story beats

Beat 1 — The ledger opens

A crisis brings a finite power source into view:

ledger_open:
  card: storyteller.card.emergency_power_ledger.v1
  trigger_kind: state_pressure
  source_incident: <blackout_capacity_facility_or_slot_id>
  power_source_state: strained | seized | sponsor_metered | public_only | lawful_only | borrowed | failing | explicit_absence
  competing_powered_surfaces_min: 2
  future_reader_present: true

The card must name both surfaces and their consequences. “Backups are low” is not enough.

Beat 2 — Priority becomes political

The producer discovers that power priority is already being claimed by someone:

• sponsor wants stage glamour and live frame preserved;
• security wants doors and checkpoints powered;
• ward or fan public wants oxygen support;
• archive wants cold-chain integrity;
• inspector wants proof scanner or lawful feed;
• crew wants safe lighting and board reliability;
• route asset needs corridor, relay, or battery bridge.

The player must name which claim wins and what is lost.

Beat 3 — The allocation rite

应急供电优先分配 offers branch families:

• certify priority;
• load shed deliberately;
• split power;
• borrow generator;
• narrow slot;
• public safety hold;
• overdraw anyway;
• refuse priority or let default select.

Each branch must create relief, cost, and a future reader.

Beat 4 — The losing surface speaks later

The story does not end when the immediate slot airs. The shed or degraded surface must be consumed later by at least one of these readers:

• 播出容量责任级联机制 reads a powered slot, blackout fold, or narrowed slot;
• 设施通行图机制 reads door power, corridor lights, fan gate, or cutroom access;
• 直播现场班组负荷机制 reads unsafe lighting, board risk, or crew hazard;
• 路线资产维护分诊机制 reads borrowed battery wear or route asset power debt;
• Fan Oxygen reads oxygen pump shedding or public oxygen priority;
• Route Assets and Custody reads powered custody movement, locked routes, or relay failures.

Beat 5 — An explicit default choice files the scar

After all nine required cards are assigned, the player may explicitly choose overdraw_anyway or default_selects. Only those two choices arm 供电削减默认. A hidden, skipped, or underfilled review remains unresolved and cannot silently manufacture an executable default.

The default actor becomes part of the story:

• generator governor trips the board;
• sponsor meter keeps glamour and drops oxygen/proof/public load;
• security grid powers doors and captures route control;
• ward reserve protects life support and narrows broadcast;
• archive freezer keeps proof cold and sheds the live correction;
• blackout system folds the contradiction into dead air;
• public queue or borrowed source claimant files the result.

Branch families

Priority certificate route

The player names a priority claim and protects one powered surface.

Immediate relief: selected route stays powered.

Cost: losing surface becomes delayed, degraded, or scoped.

Future reader: the lost surface must appear in later capacity, facility, oxygen, archive, public, or route-asset logic.

Load-shed safety route

The player deliberately turns off a load to avoid overdraw.

Immediate relief: blackout and crew hazard risk drop.

Cost: the shed surface becomes recovery-only, public-only, lawful-only, or blocked.

Future reader: recovery or public explanation must name what was shed.

Split-power degraded route

The player keeps several surfaces partially alive.

Immediate relief: multiple options remain open.

Cost: reliability, visibility, legality, or safety worsens.

Future reader: a later route accepts the degraded state or demands full-power repair.

Borrowed generator route

The player borrows from sponsor, security, ward, fan relay, pirate relay, archive battery, or route asset.

Immediate relief: selected surface stays powered.

Cost: the lender gains claim, price, maturity, capture, or wear.

Future reader: release, repayment, route-asset maintenance, or sponsor/public dispute becomes armed.

Low-power broadcast route

The player rewrites the slot to fit reduced load.

Immediate relief: a safer version can air.

Cost: sponsor glamour, audience expectation, lawful proof, public visibility, or contract promise is scarred.

Future reader: slot contract, capacity liability, management compression, or public receipt reads the narrowing.

Public safety hold route

The player tells the audience, crew, sponsor, or inspector that power is unsafe.

Immediate relief: safety legitimacy and oxygen/crew protection improve.

Cost: sponsor pressure, schedule pressure, inspection heat, or public panic rises.

Future reader: public-only or lawful-only route opens; glamour route narrows.

Overdraw glamour route

The player keeps everything visible powered past safe load.

Immediate relief: spectacle or schedule is preserved.

Cost: hidden trip, blackout fold, oxygen drop, archive freeze, door lock, or crew hazard is armed.

Future reader: default or recovery route must consume the overdraw.

Route assets and rewards

This storyline can produce cards or durable states such as:

• Emergency Power Ledger opened;
• Power Priority Certificate;
• Load-Shed Receipt;
• Borrowed Generator Claim;
• Low-Power Slot Cut;
• Ward Reserve Priority;
• Archive Cold-Chain Priority;
• Sponsor Meter Capture;
• Door Power Lock;
• Blackout Fold Recovery Only.

These are not rewards in the sense of clean upgrades. Each one is a future reader handle.

Counter movement

Each resolved branch should move at least three surfaces:

counter_contract:
  relief_examples:
    - blackout_risk_down
    - oxygen_harm_risk_down
    - protected_route_unlocked
    - archive_integrity_preserved
    - broadcast_reliability_up
  cost_examples:
    - schedule_pressure_up
    - sponsor_stop_loss_pressure_up
    - inspection_heat_up
    - crew_hazard_up
    - route_asset_wear_up
    - public_distrust_up
  future_reader_examples:
    - shed_surface_recovery_only
    - borrowed_generator_claim_maturity_due
    - narrowed_slot_contract_reader
    - door_power_lock_facility_reader
    - blackout_fold_capacity_reader

Miss and failure shapes

The storyline should remain playable even when the player lacks clean inputs:

• no technician: split power or public safety hold may remain, but certification is blocked;
• no lawful seal: proof scanner priority becomes public-only or default-prone;
• no public notice: load shedding can still happen, but public distrust rises;
• sponsor-metered source: immediate slot power works, but sponsor capture attaches;
• borrowed route asset: power is available, but maintenance wear and future claim are armed;
• no future reader: the storyline fails validation because power scarring would be meaningless.

Replay contract

storyline_id: storyteller.storyline.emergency_power_priority.v1
session_id: lens-emergency-power-priority-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_incident_id: <id>
  finite_power_source_present: true
  competing_powered_surfaces_min: 2
  future_reader_present: true
  no_fixed_turn_trigger: true
offered:
  card: storyteller.card.emergency_power_ledger.v1
  rite: storyteller.rite.emergency_power_priority_allocation.v1
branches:
  priority_branch:
    response: certify_priority | load_shed | split_power | borrow_generator | narrow_slot | public_safety_hold | overdraw_anyway | default_selects
    protected_surface: <surface>
    shed_or_degraded_surface: <surface>
    relief: []
    cost: []
    future_reader: <route_or_slot>
  default_branch:
    event_seen_or_armed: storyteller.event.power_shed_default.v1
    selected_choice_index: 6 | 7
    terminal: governor_trip | sponsor_meter_capture | security_grid_lock | ward_reserve_priority | archive_freezer_priority | blackout_fold | public_queue_priority | borrowed_source_claim

Adjacency boundary

This storyline decides one immediate finite-power disposition: source, protected surface, losing surface, claimant, handler, support, default risk, and future reader.

• Broadcast Capacity Liability Cascade prices responsibility after a capacity result; it does not choose the powered surface.
• Blackout Incidents and blackout-residue content consume an outage scar; they do not assign the original priority.
• Borrowed-generator claim maturity prices and releases a lender claim after borrowed power is used; it does not replace the allocation.
• Facility access, fan oxygen, archive, and slot-contract readers consume this packet’s future flag; none may rewrite its protected or shed surface.

Non-goals

• Not a generic resource economy.
• Not a fixed upkeep storyline.
• Not a lore note about the Seventh Dome generator.
• Not a black-screen randomizer.
• Not a clean mitigation path.
• Not valid unless priority, losing surface, default actor, deltas, and future reader are all playable.