Handler Burden Ledger Storyline / 处理人负荷账本

Handler Burden Ledger is a management/RPG pressure storyline for the moment when the same trusted handler keeps being asked to solve incompatible broadcast crises.

The current Storyteller mesh already makes crises simultaneous, factions finite, witnesses payable, cutroom authority scarce, correction slots rivalrous, liabilities callable, and endings scarred. The remaining high-value gap is personal carry cost: Baiya, Yu Lan, Shen Luo, Han Yanshuang, Inspector Rhee, Han Cutroom, or a low-rank route asset can still risk becoming reusable buttons if their prior assignments do not change their future posture.

This storyline makes handler use durable, missable, recoverable, and narratively sharp without adding filler companion scenes.

Primary playable question

When a person has already carried one crisis, do you support them before asking again, respect their refusal, trade their access to a faction, overdraw them, replace them, or recover them with a scar?

Every answer must show:

• the prior burden row;
• the current crisis that wants the handler;
• the intended role;
• the support, refusal, trade, overdraw, replacement, or recovery choice;
• who benefits and who is harmed;
• how handler state changes;
• how future assignment changes.

Why this is the next useful expansion

This is not another sponsor, inspector, archive, witness, edit, or ending branch. Those already exist. The gap appears across all of them: a named person can be assigned again and again unless the engine remembers what the person personally absorbed.

The storyline binds:

• 处理人负荷账本机制;
• 处理人负荷账本;
• 处理人负荷复盘;
• 处理人透支破口.

It strengthens management + RPG design because the player is not merely allocating abstract lanes. The player is deciding what kind of person each handler becomes after being used as a lane.

State-triggered entry

Open this storyline when all of the following are true:

1. a live crisis needs a handler, witness, editor, manager, inspector, public carrier, route asset, or explicit absence;
2. one eligible handler has a prior burden row or a burden-relevant state: committed, strained, exposed, compromised, refusing, hostile, unavailable, recovered with scar, or captured;
3. the current crisis would be altered by that burden through role contradiction, faction claim, public exposure, legal visibility, sponsor capture, edit contamination, witness guilt, fatigue, or refusal;
4. the player can still choose support, refusal, access trade, overdraw, replacement, absence, or recovery;
5. the result can change future assignment cost, route access, handler state, claimant posture, or pressure counters.

This storyline must not trigger from a fixed numbered sequence.

Storyline spine

Beat 1 — The old assignment becomes a row

A prior branch creates or updates 处理人负荷账本. The row records source surface, handler, role, burden type, benefited claimant, harmed claimant, handler state, and future assignment effect.

Example burden rows:

• Baiya patched a contradiction and now carries edit contamination;
• Yu Lan published a public receipt and now carries witness exposure;
• Shen Luo bought sponsor time and now carries contract capture;
• Han Yanshuang made proof lawful and now carries bureau favor debt;
• Inspector Rhee opened a docket and now carries archive visibility;
• Han Cutroom spent final-cut authority and now carries cutroom exhaustion;
• a low-rank carrier survived custody and now carries payroll or retaliation risk.

Beat 2 — A new crisis wants the same person

A second surface asks for the handler again. The crisis may come from 制作分诊台, 剪辑室优先队列线, 受保护证人薪册, 派系承诺账本, 派系责任承保, 播出实在漂移审计, or 结局伤痕账本线.

The old row must be visible before the player reuses the handler.

Beat 3 — Review, support, refuse, trade, overdraw, replace, or recover

The player opens 处理人负荷复盘. The rite asks what makes the assignment possible:

• support the handler;
• respect refusal;
• trade access to a faction;
• force overdraw;
• replace with another handler or explicit absence;
• recover a damaged handler with a scar.

Beat 4 — Current relief creates personal consequence

The chosen branch may improve the current crisis, but the handler’s future state changes.

Valid future effects include:

• cheaper with trust;
• scarred but available;
• costs extra support;
• public-only;
• lawful-only;
• sponsor-only;
• harder;
• blocked;
• hostile counteroffer;
• captured;
• unavailable;
• requires recovery.

Beat 5 — Overdraft breaks visibly

If the player hides the burden, ignores refusal, trades access without recording capture, or forces reuse without support, 处理人透支破口 fires or the source crisis records default-ready absence.

The break is not a mood scene. It mutates handler state, claimant posture, crisis outcome, and future route access.

Branch model

Branch A — Supported reuse

The player spends support before using the handler again.

Expected outcomes:

handler_state_after: committed | recovered_with_scar | bonded | strained
current_crisis_effect: relief_with_cost
support_spent: rest | pay | safehouse | legal_cover | public_cover | edit_shield | proof_support | sponsor_retainer
future_assignment_effect: scarred_but_available | cheaper_with_trust | costs_extra_support

Branch B — Respect refusal

The player lets the handler refuse the role and solves the current surface another way.

Expected outcomes:

handler_state_after: bonded | recovered_with_scar | committed
current_crisis_effect: delayed | weaker_success | default_ready | rival_advantage
future_assignment_effect: cheaper_with_trust | costs_extra_support | scarred_but_available

Branch C — Trade handler access

The player accepts sponsor, inspector, archive, fan public, editor, pirate, or route claimant support to make the handler available.

Expected outcomes:

handler_state_after: compromised | captured | exposed | public_only | lawful_only | sponsor_only
current_crisis_effect: relief_with_capture_or_debt
future_assignment_effect: restricted_by_claimant | harder | requires_recovery

Branch D — Forced overdraw

The player pushes the handler through without adequate support.

Expected outcomes:

handler_state_after: strained | refusing | hostile | unavailable | exposed
emitted_event: storyteller.event.handler_overdraft_break.v1
current_crisis_effect: partial_relief | contaminated_success | failed_assignment | default_ready
future_assignment_effect: blocked | hostile_counteroffer | costs_extra_support | requires_recovery

Branch E — Replacement or explicit absence

The player preserves the handler and accepts a weaker or different crisis route.

Expected outcomes:

handler_state_after: unchanged | recovered_with_scar
current_crisis_effect: weaker_success | delayed | default_ready | rival_default
future_assignment_effect: handler_preserved | crisis_costlier | claimant_default_pressure_up

Branch F — Recovery with scar

The player spends a real object to bring a damaged handler back.

Expected outcomes:

handler_state_after: recovered_with_scar | bonded | committed | still_hostile
support_spent: true
scar_retained: true
future_assignment_effect: scarred_but_available | public_only | lawful_only | sponsor_only | costs_extra_support

Counter contract

Each resolution must change at least three counters or durable states, with visible relief and visible cost.

Primary states:

• handler_burden
• handler_trust
• handler_loyalty_doubt
• handler_refusal_pressure
• handler_exposure
• handler_capture_pressure
• handler_recovery_cost
• staff_fatigue
• public_exposure
• inspection_heat
• bureau_favor_debt
• contract_capture
• edit_debt
• witness_retaliation_risk
• route_asset_pressure
• unstaffed_ticket_risk
• black_screen_slots
• future_assignment_cost

Character hooks

• Baiya can resolve edit/black-box pressure, but repeated use can create edit contamination or source ambiguity.
• Yu Lan can mobilize public proof, but repeated use can expose witnesses or make the public route harder to control.
• Shen Luo can bridge sponsor pressure, but repeated use can deepen contract capture.
• Han Yanshuang can make lawful pressure survivable, but repeated use can increase inspection heat and bureau debt.
• Inspector Rhee Archive can open admissible dockets, but repeated use can capture proof inside archive visibility.
• Han Cutroom can make final cut credible, but repeated use can exhaust cutroom authority.

Missability and recovery

This storyline is missable when the implementation:

• treats a burdened handler as fresh;
• records only a hidden fatigue flag;
• lets refusal disappear without changing the crisis;
• allows sponsor or inspector access to a handler without capture/debt;
• overwrites hostile/captured/unavailable state with a clean reset;
• forgets the source burden row across sessions.

Recovery is allowed only with a scar:

• support the handler and accept route restriction;
• publish public receipt and accept exposure;
• appeal lawful protection and accept bureau debt;
• buy sponsor release and accept contract capture;
• spend edit proof and accept edit debt;
• use another handler and accept weaker proof or default pressure.

Replay/session evidence shape

storyline: storyteller.storyline.handler_burden_ledger.v1
session_id: lens-handler-burden-ledger-v1-<timestamp>
seed: <deterministic-seed>
source_burden:
  source_session_id: <session that created burden>
  source_surface: <surface id>
  row_id: <burden row>
  handler_id: <handler>
  handler_state_before: <state>
  handler_state_after_source: <state>
current_request:
  crisis_surface: <surface id>
  intended_role: <role>
  handler_state_before_review: <state>
  prior_burden_row_visible: true
offered:
  card: storyteller.card.handler_burden_ledger.v1
  rite: storyteller.rite.handler_burden_review.v1
branch_runs:
  supported_reuse:
    support: <support>
    handler_state_after: <state>
    future_assignment_effect: <effect>
  forced_overdraw:
    event: storyteller.event.handler_overdraft_break.v1
    handler_state_after: <state>
    future_assignment_effect: <effect>
assertions:
  - state_entry_not_sequence
  - prior_burden_row_visible
  - support_or_refusal_or_absence_required
  - branch_outcomes_diverge
  - handler_state_changes_future_assignment
  - overdraft_event_or_default_is_durable

Non-goals

• Not raw character-count expansion.
• Not a camp dialogue generator.
• Not a fixed rest/upkeep phase.
• Not a global stamina meter.
• Not a replacement for production triage, witness payroll, cutroom priority, faction liability, or ending scars.
• Not a clean way to reset every handler; recovery always leaves an observable scar, debt, claimant posture, or future-route change.