Proof Burden Reassignment / 举证负荷再分配线

Proof Burden Reassignment is a downstream pressure storyline for evidence that has already worked.

A proof object may have protected a route, defeated a false owner, stabilized a slot, paused sponsor pressure, preserved a consent boundary, or made an archive copy admissible. That success remains true. This storyline begins when someone asks: who must now keep that proof alive?

Why this is the next useful expansion

Recent content has strong first-order and second-order pressures:

• 导出证据回流分岔线 makes old proof return into current route pressure.
• 同意债转移线 makes consent/refusal relief inherit a named carrier.
• 归档执行案卷 makes enforceable outcomes need service.
• Route Assets and Custody makes custody assets stateful.

The remaining gap is maintenance burden. If a receipt, checksum, archive seal, witness oath, fan ledger, consent row, or route asset can rescue the player once but nobody must later produce it, protect it, or answer a countercopy, then proof becomes inert provenance. This storyline makes successful proof become management work.

Primary playable question

After proof-based relief exists, does the player keep the proof burden with the subject, assign it to archive/inspector, hide it in editor maintenance, publish it through public witness, route it through沈洛 or sponsor, absorb it into production, split/escrow it, or let it default?

Every answer must preserve the earlier relief as history while changing future route access, holder posture, claimant pressure, or burden cost.

State-triggered entry

Open this storyline when all conditions below are present:

1. a prior proof object or proof row exists;
2. that proof created concrete relief;
3. the relief still supports an available, protected, public-only, lawful-only, contested, or recovery route;
4. the current proof holder is named, contested, absent, overdrawn, captured, hostile, hidden, or being replaced;
5. a challenger, countercopy, missing update, checksum duty, consent/refusal repeat duty, witness availability duty, filing duty, or proof-production demand appears;
6. at least one holder or explicit absence can be selected;
7. at least one future route, follower, claimant, or counter can mutate.

This storyline must never open from a fixed numbered turn, day interval, chapter quota, raw content count, or lens-health state.

Content pack

Mechanic

• 举证负荷再分配机制 — defines burden states, holder families, proof duties, branch families, default rules, and replay evidence shape.

Card

• 举证负荷案卷 — records source relief, proof object, current holder, proposed holder, challenger, proof duty, affected route asset, and risk if defaulted.

Rite

• 举证负荷再分配复核 — assigns, splits, escrows, or refuses the proof burden through a branchy management decision.

Event

• 举证负荷违约 — fires or arms when the burden is unassigned, falsely cleaned, overdrawn, captured, or unproduced.

Core cast and holder roles

• Han Yanshuang can carry lawful proof through seal, oath, injunction risk, or bureau debt.
• Yu Lan can move proof burden into public receipt, historian note, witness chain, or fan retaliation risk.
• Baiya can maintain checksum/source proof while increasing edit debt or source ambiguity.
• Shen Luo can bridge proof through contract language, manager carriage, sponsor stay, or complicity risk.
• 交接链跑腿 can carry physical proof, become protected under oath, be captured, or turn hostile if abandoned.
• The subject, artist, public witness, fan ledger, sponsor desk, inspector/archive, editor, or production desk can become the holder.

A named actor does not solve the burden by appearing. They must be assigned to a concrete proof duty with visible cost.

Storyline sequence

Beat 1 — Proof helped once

The storyline begins after evidence, consent, archive custody, public receipt, memorial proof, editor checksum, route asset, or witness proof produced relief.

Examples:

• a returned fan oxygen receipt blocked sponsor ownership;
• a black-box checksum preserved a contested route asset;
• a consent/refusal row protected an artist boundary;
• a lawful archive seal made a copy admissible;
• a public historian note defeated a false owner;
• a runner delivered the only valid chain receipt.

The new storyline does not undo that success.

Beat 2 — The burden becomes visible

Create or update 举证负荷案卷. The docket names source proof, prior relief, prior scar, current holder, proposed holder, challenger, duty, route asset, and default risk.

The burden is visible when someone asks for original production, checksum maintenance, consent/refusal repetition, witness availability, archive filing, public update, chain proof, escrow payment, or countercopy rebuttal.

Beat 3 — Reassignment review

Offer 举证负荷再分配复核. The player selects one branch:

• return burden to subject or original asset;
• assign to inspector/archive escrow;
• assign to editor/black-box maintenance;
• assign to public witness, historian, fan ledger, or pirate relay;
• assign to沈洛, sponsor, or settlement bridge;
• assign to production desk;
• split or escrow burden;
• refuse, hide, or falsely clean it.

Beat 4 — Holder state mutates

The selected holder becomes more than a label. They may become protected, overdrawn, public-only, lawful-only, sponsor-owned, hostile, captured, recovery-only, or bound to a future cost.

The affected route asset also changes state: protected, costlier, public-only, lawful-only, sponsor-only, captured, split-canon, contradiction-pending, recovery-only, blocked, or false-owner.

Beat 5 — Default or scarred continuity

If the burden is assigned with cost, the route remains usable but scarred.

If the player refuses to name a holder, treats authority as proof, sells the burden cleanly, lets a holder be overdrawn, or cannot produce proof when challenged, 举证负荷违约 fires or becomes default-ready.

Branch matrix

Branch	Immediate relief	Cost/scar	Future state
Subject/original asset	integrity, legibility, anti-capture	schedule/protection/sponsor/public cost	protected, public-only, lawful-only, costlier
Inspector/archive	admissibility, fraud prevention	inspection heat, bureau debt, lawful-only gate	lawful-only, protected, costlier, contradiction-pending
Editor/black-box	continuity, checksum legibility	edit debt, archive debt, source ambiguity	protected, split-canon, contradiction-pending, costlier
Public witness	public receipt, anti-capture	witness exposure, sponsor retaliation, fan risk	public-only, protected, costlier
Shen Luo/sponsor	slot survival, legal bridge	contract capture, complicity, public distrust	protected-but-owned, sponsor-only, captured, costlier
Production desk	keeps branch alive, delays faction capture	handler burden, payroll leak, recovery cost	costlier, contradiction-pending, recovery-only
Split/escrow	false owner pressure down, route stabilizes	coordination, drift, inspection/edit cost	split-canon, lawful-only, public-only, contradiction-pending
False-clean/default	short silence or none	default event, false owner, hostile holder	hostile, captured, false-owner, recovery-only, blocked

Counter contract

Every branch must mutate at least three counters or durable states. At least one must be relief and at least one must be cost.

Primary counters:

• proof_burden
• proof_legibility
• route_access_stability
• route_asset_pressure
• handler_burden
• inspection_heat
• bureau_favor_debt
• sponsor_stop_loss_pressure
• contract_capture
• edit_debt
• archive_debt
• public_receipt_legitimacy
• public_receipt_distrust
• public_exposure
• fan_oxygen_resentment
• source_ambiguity
• false_owner_pressure
• future_recovery_cost
• voice_integrity
• continuity_hazard

Missability and recovery

This storyline is missable when the player treats proof-based relief as self-maintaining.

Missed states:

• proof_burden_unassigned;
• proof_burden_defaulted;
• holder_overdrawn;
• holder_hostile_witness;
• proof_holder_captured;
• countercopy_first;
• false_owner_hardened;
• recovery_only_route.

Recovery is allowed only through visible cost:

• reopen review with stronger proof;
• assign lawful escrow and accept lawful-only play;
• publish a public update and accept exposure;
• protect or rescue the holder;
• pay sponsor/settlement cost and accept capture risk;
• return proof burden to subject and accept schedule/protection cost;
• sacrifice a weaker route asset to preserve a stronger route;
• admit split-canon and continue with public/lawful/editor divergence.

Integration notes

• With 导出证据回流分岔线, accepted, exposed, quarantined, or traded proof can later demand burden holder assignment.
• With 同意债转移线, proof burden keeps consent/refusal rows from becoming implied authority.
• With 归档执行案卷, an enforceable order may fail because the burden holder cannot produce the proof copy.
• With 处理人负荷账本, proof holders can become overdrawn rather than infinite tools.
• With 认领撞锁, a burden default can make a rival claimant narrate first or harden false ownership.
• With Route Assets and Custody, burden assignment mutates route asset state and future availability.

Multi-session evidence expectation

A correct implementation can inherit source relief from one durable replay and assign or default burden in a later replay.

Expected evidence:

storyline_id: storyteller.storyline.proof_burden_reassignment.v1
source_session_id: <session that created proof-based relief>
review_session_id: <session that assigns or defaults burden>
seed: <deterministic seed>
entry_state:
  source_proof_object_id: <proof object>
  source_relief:
    - <relief>
  source_scar:
    - <scar>
  current_holder: <holder or none>
  challenger_or_default_pressure: <challenger or pressure>
  affected_route_asset: <route asset id>
  no_fixed_turn_trigger: true
offered_choices:
  - card.proof_burden_docket
  - rite.proof_burden_reassignment_review
  - subject_or_asset_retained
  - inspector_archive_carried
  - editor_black_box_carried
  - public_witness_carried
  - shen_luo_or_sponsor_carried
  - production_carried
  - split_or_escrowed
  - false_clean_or_default
branch_result:
  selected_branch: <branch>
  holder_before: <holder or none>
  holder_after: <holder or none>
  burden_state_after: <state>
  route_asset_before: <state>
  route_asset_after: <state>
  counter_deltas:
    relief:
      - <relief counter/state>
    cost:
      - <cost counter/state>
  event_seen_or_armed: storyteller.event.proof_burden_default.v1 | none

Non-goals

• Not a proof inventory.
• Not a generic legal audit.
• Not a fixed-turn upkeep storyline.
• Not a raw count target.
• Not a governance/process page.
• Not a clean continuity repair.
• Not valid unless previous proof-based relief creates continuing playable burden.