Proof Burden Reassignment / 举证负荷再分配机制

Proof Burden Reassignment is the mechanism that turns a successful proof into continuing work.

A receipt, checksum, archive copy, consent row, witness oath, public ledger, permit, or route asset may have produced relief earlier. This mechanism decides who must keep that proof usable after the next challenge appears.

It exists between proof victory and enforcement failure: the proof is not inert provenance, and the later breach is not arbitrary punishment. The player must choose a holder, split the burden, escrow it, or let it default.

Design gap addressed

The current corpus already supports:

• returned proof changing current route assets through 导出证据回流分岔线;
• consent/refusal scars moving between carriers through 同意债转移线;
• rulings becoming enforceable through 归档执行案卷;
• route assets changing durable state through Route Assets and Custody.

The missing layer is continuing proof duty. A route can be protected by proof once, then collapse later because no one can produce, maintain, repeat, pay for, or protect that proof. This mechanism gives that burden a state machine and branch contract.

Entry contract

Open this mechanism only when all conditions are true:

1. A prior branch produced proof-based relief.
2. That relief still matters to a current or future route.
3. A challenger, contradiction, expiry pressure, missing holder, or burden dispute now exists.
4. The current holder is named, absent, contested, overdrawn, captured, hostile, hidden, or being replaced.
5. At least one holder family can be selected or explicitly missing.
6. At least one route asset, follower, claimant, counter, or future availability state can mutate.

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

Core objects

Burden row

A burden row lives in 举证负荷案卷 and binds:

• source proof object;
• relief supported by that proof;
• scar already attached to that proof;
• current holder or explicit absence;
• proposed holder;
• challenger or default pressure;
• proof duty required;
• affected route asset;
• risk if the burden defaults.

Holder

A holder is the actor or object that must produce or maintain proof.

Valid holder families:

• subject_or_route_asset
• shen_luo_or_contract_bridge
• sponsor_desk
• inspector_archive
• editor_black_box
• public_witness
• production_desk
• split_or_escrow
• none_false_clean

Proof duty

The duty defines what is being carried:

• produce_original
• maintain_checksum
• repeat_consent_boundary
• keep_witness_available
• file_seal
• publish_update
• prove_chain
• pay_escrow
• rebut_countercopy
• equivalent in-world proof maintenance duty.

Burden states

State	Meaning	Required gameplay effect
unassigned	Proof relief exists but no one currently carries the burden.	Review is offered or default pressure arms.
assigned	A named holder carries burden.	Holder state and route state can be inspected.
contested	More than one holder/claimant challenges burden assignment.	Review must branch, split, escrow, or default.
escrowed	Burden is held under lawful, neutral, or split cover.	Fraud risk drops; debt or gating rises.
split	Different proof duties live with different holders.	Route becomes public-only, lawful-only, split-canon, or costlier.
public_carried	Public witness/fan/historian carries burden.	Private capture drops; exposure/retaliation rises.
lawful_carried	Inspector/archive carries burden.	Admissibility rises; lawful-only/bureau cost rises.
editor_carried	Cutroom/black-box maintains burden.	Continuity improves; edit/archive/source debt rises.
sponsor_carried	Sponsor funds or controls proof burden.	Immediate pressure drops; capture/public distrust rises.
production_carried	Crisis desk absorbs burden.	Faction capture delayed; handler burden/recovery cost rises.
overdrawn	Holder carries more proof than they can sustain.	Assignment requires relief, protection, or creates default risk.
default_ready	The challenge is unanswered.	举证负荷违约 can fire.
defaulted	Holder failed to produce or maintain proof.	Route state mutates to costlier, hostile, captured, false-owner, recovery-only, or blocked.

Branch families

Subject or route asset retains burden

Best when consent, refusal, body, voice, memory, or witness boundary must remain personal.

Relief:

• integrity, proof legibility, or private-capture resistance improves.

Cost:

• protection, schedule, public exposure, sponsor pressure, or recovery cost rises.

Future route states:

• protected, public_only, lawful_only, costlier.

Inspector/archive carries burden

Best when the route needs admissibility, custody seal, lawful proof, or fraud prevention.

Relief:

• archive signature, custody clarity, false-owner pressure, or proof admissibility improves.

Cost:

• inspection heat, bureau debt, public delay, or lawful-only gating rises.

Future route states:

• lawful_only, protected, costlier, contradiction_pending.

Editor/black-box carries burden

Best when the proof must be maintained as checksum, source tape, redaction, or continuity patch.

Relief:

• continuity hazard, reality drift, or proof legibility improves.

Cost:

• edit debt, archive debt, source ambiguity, or public distrust rises.

Future route states:

• protected, split_canon, contradiction_pending, costlier.

Public witness carries burden

Best when private capture is more dangerous than exposure.

Relief:

• public receipt legitimacy, witness strength, or anti-capture pressure improves.

Cost:

• witness exposure, inspection heat, sponsor retaliation, fan resentment, or pirate exposure rises.

Future route states:

• public_only, protected, costlier.

Shen Luo, sponsor, or settlement bridge carries burden

Best when slot survival or legal bridge matters immediately.

Relief:

• sponsor/slot pressure or legal usability improves.

Cost:

• contract capture, complicity, public distrust, false ownership, or recovery cost rises.

Future route states:

• protected_but_owned, sponsor_only, captured, lawful_only, costlier.

Production desk carries burden

Best when the player wants flexibility and delayed faction capture.

Relief:

• branch remains alive; faction capture is delayed.

Cost:

• handler burden, payroll leak, future recovery cost, route pressure, or staffing risk rises.

Future route states:

• costlier, contradiction_pending, recovery_only, protected_with_new_cost.

Split or escrow burden

Best when no single holder should own the route.

Relief:

• false owner pressure drops; route access stabilizes across multiple covers.

Cost:

• source ambiguity, coordination cost, inspection heat, edit debt, or public delay rises.

Future route states:

• split_canon, lawful_only, public_only, contradiction_pending, costlier.

False-clean or default

Occurs when the player refuses to name a holder, hides the burden, treats authority as proof, or sells proof duty without scar.

Required result:

• 举证负荷违约 fires or arms;
• the affected route mutates to hostile, captured, false_owner, recovery_only, blocked, or costlier.

Counter contract

Every assignment, split, escrow, or default must mutate at least three counters or durable states. At least one mutation must be relief and at least one must be cost.

Core counter surfaces:

• 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

Holder pressure and followers

A holder can become a route asset or liability.

Valid holder state effects:

• protected_under_oath
• overdrawn
• hostile_witness
• captured_holder
• public_only_holder
• lawful_only_holder
• sponsor_owned_holder
• production_overloaded_holder
• recovery_only_holder

High-rank characters cannot erase proof burden by appearing. They must be assigned to a concrete proof duty with visible cost.

Multi-session evidence expectation

The mechanism can inherit proof relief from an earlier session and resolve burden in a later session. The replay evidence must preserve both.

mechanic_id: storyteller.mechanic.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:
  trigger_kind: state_pressure
  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

Failure cases

This mechanism fails if:

• entry is based on a fixed numbered turn, day interval, chapter quota, content count, or lens-health state;
• no source proof-based relief is named;
• no current holder/proposed holder/explicit absence exists;
• authority, money, edit checksum, public approval, or archive seal silently replaces proof duty;
• positive resolution has no cost;
• default does not mutate future route state;
• holder state never changes;
• branch families collapse into a single generic success/failure;
• replay evidence lacks source session, burden id, holder before/after, route state before/after, selected branch, and counter deltas.

Non-goals

• Not a proof inventory.
• Not a new trial/verdict mechanism.
• Not generic upkeep.
• Not raw count expansion.
• Not governance or process documentation.
• Not a clean continuity repair.
• Not valid unless proof success creates continuing playable burden.