Handler Burden Review / 处理人负荷复盘

Handler Burden Review is an assignable management rite for deciding whether a previously burdened handler can safely carry another crisis.

It exists for moments when the player wants to use a familiar high-value character again, but that person already has a row in 处理人负荷账本. The rite does not ask whether the character likes the player in the abstract. It asks what support, override, cover, compromise, or refusal will make the next assignment possible.

Entry conditions

Offer this rite when all of the following are true:

1. a live crisis, docket, route asset, proof chain, witness support row, correction row, cutroom row, or triage ticket needs a handler;
2. at least one eligible handler has a prior burden row or explicit absence;
3. the prior burden can affect the current assignment through exposure, oath, sponsor capture, legal visibility, edit contamination, refusal, fatigue, or hostile posture;
4. the player can assign support, respect refusal, trade access, overdraw, recover, replace, or accept absence;
5. the assignment can still mutate future route access, claimant posture, counters, or handler state.

This rite must never be offered only because a fixed numbered turn arrived.

Slots

Required assignment slots:

required_slots:
  burden_ledger: card.handler_burden_ledger
  target_handler: <handler id or explicit absence>
  current_crisis: <surface id>
  intended_role: <role id>
  prior_burden_row: <row id or explicit absence>
  support_or_override: rest | pay | safehouse | legal_cover | public_cover | edit_shield | sponsor_retainer | proof_support | replacement_handler | refusal_respected | forced_overdraw | explicit_absence
  harmed_claimant_named: true

The rite fails validation if the player can reuse a burdened handler without selecting a support/override/absence input.

Branches

Branch A — Supported reuse

The player assigns support before reuse.

Expected outcome:

handler_state_after: committed | strained | recovered_with_scar | bonded
current_crisis_relief: true
cost_any:
  - safehouse_capacity_down
  - cash_reserve_down
  - proof_support_spent
  - public_exposure_up
  - inspection_heat_up
  - contract_capture_up
  - edit_debt_up
future_assignment_effect_any:
  - cheaper_with_trust
  - costs_extra_support
  - scarred_but_available

Branch B — Refusal respected

The player accepts the handler’s boundary and assigns another path, delay, or absence.

Expected outcome:

handler_state_after: bonded | recovered_with_scar | committed
current_crisis_cost: weaker_handler | delayed | rival_advantage | unstaffed_risk_up
future_assignment_effect_any:
  - cheaper_with_trust
  - public_only
  - lawful_only
  - costs_extra_support

Branch C — Trade access

The player lets a faction carry the burden or buy the handler’s next use.

Expected outcome:

handler_state_after: compromised | exposed | captured | sponsor_only | lawful_only
current_crisis_relief: true
cost_any:
  - contract_capture_up
  - bureau_favor_debt_up
  - public_receipt_distrust_up
  - route_asset_pressure_up
  - future_blackmail_cost_up

Branch D — Forced overdraw

The player forces the handler through another assignment without sufficient support.

Expected outcome:

handler_state_after: strained | exposed | refusing | hostile | unavailable
current_crisis_relief: partial_or_temporary
cost_any:
  - handler_burden_up
  - trust_or_loyalty_down
  - unstaffed_ticket_risk_up
  - reality_drift_up
  - black_screen_slots_up
future_assignment_effect_any:
  - harder
  - blocked
  - hostile_counteroffer
  - requires_recovery

Branch E — Replace or accept absence

The player uses a weaker handler, route asset, proof object, or explicit absence.

Expected outcome:

handler_state_after: unchanged | recovered_with_scar
current_crisis_result: weaker_success | delayed | default_ready | failed
future_assignment_effect_any:
  - handler_preserved
  - crisis_costlier
  - claimant_default_pressure_up

Branch F — Recovery action

The player spends a real support object to move a handler from refusing, hostile, captured, or unavailable toward use again.

Expected outcome:

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

Resolution contract

Every resolution must write back to 处理人负荷账本. Minimum outcome fields:

resolution:
  selected_handler: <handler id or explicit absence>
  selected_branch: supported_reuse | refusal_respected | trade_access | forced_overdraw | replace_or_absent | recovery_action
  burden_row_before: <state>
  burden_row_after: <state>
  current_crisis_effect: <relief, partial, delay, default, blocked>
  claimant_benefited: <claimant>
  claimant_harmed: <claimant>
  future_assignment_effect: <effect>
  counter_deltas_min: 3

Failure/default pressure

If the rite is skipped when a burdened handler is required, the implementation should not silently treat the handler as fresh. The burden row must either block the assignment, raise support cost, create explicit absence, or route the crisis into a default from its source surface.

Non-goals

• Not a camp scene.
• Not a morality check.
• Not a fixed rest action.
• Not a universal remove-fatigue button.
• Not a generic party-management layer detached from crisis surfaces.
• Not valid if it ignores claimant benefited, claimant harmed, and future assignment effect.