Consent Debt Transfer / 同意债转移线

Consent Debt Transfer is a downstream pressure storyline for consent/refusal debt after the show has already used consent language to survive.

The player may have saved a slot, paused a sponsor default, passed an audit, repaired continuity, or opened a route through a consent clause. That relief remains true. This storyline starts later and asks: who now carries the consent debt?

Why this is the next useful expansion

The recent 沈洛合同捕获分岔线 makes consent packaging playable and branchy. The broader vault already has aftershock, burden, stabilization, and custody surfaces through 和解反震账本, 处理人负荷账本, and Route Assets and Custody.

The remaining gap is specific inheritance: consent/refusal scars need a durable route object. Without this, a folded consent success can become a generic settled liability. That would erase exactly the thing Shen Luo’s route is supposed to make dangerous: consent can be useful, but its debt remains personal.

Primary playable question

When a previous consent/refusal clause produced relief, does the debt return to the subject, move to沈洛, get bought by sponsor, get narrowed by inspector/archive, get hidden in edit continuity, get carried by the public, get absorbed by production, or revert as false-clean harm?

Every answer must keep the earlier relief as history while changing future route access, character posture, or claimant pressure.

State-triggered entry

Open this storyline when all conditions below are present:

1. a prior consent/refusal/proxy/split/absence row exists;
2. that row created concrete relief;
3. a beneficiary is named;
4. subject, proof, or explicit absence remains visible;
5. the current carrier is unassigned, contested, overdrawn, hostile, captured, absent, or being reused;
6. at least one later route can become protected, owned, public-only, lawful-only, sponsor-only, costlier, hostile, blocked, or recovery-only.

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

Content pack

Mechanic

• 同意债转移机制 — defines consent debt row state, carrier states, reversion rules, branch families, and evidence shape.

Card

• 同意债转移案卷 — stores source consent row, subject, original state, proof/absence, relief, beneficiary, carrier, scar, and future route effect.

Rite

• 同意债分配复核 — assigns or challenges the carrier through subject return,沈洛 carriage, sponsor carriage, inspector/archive carriage, editor carriage, public witness, production burden, or false-clean default.

Event

• 同意债回转 — fires or arms when the debt was treated as clean, hidden, reused, implied, captured, or contradicted.

Main actors and surfaces

• Shen Luo — carries the debt as protective manager, refusal witness, lawful escrow handler, or sponsor broker.
• Yu Lan — turns the debt into public receipt, historian witness, fan legitimacy, or public backlash.
• Baiya — carries debt through cutroom checksum, black-box proof, continuity patch, or edit contamination.
• Han Yanshuang — routes debt through lawful seal, audit docket, archive quarantine, or white-glove surety.
• Sponsor desk — can pause default by carrying debt privately, but converts the route toward ownership.
• Subject or route asset — can reclaim the debt, refuse, split, narrow, or make clean use impossible.
• Production desk — can carry the debt internally, but it becomes handler burden, staffing risk, or future recovery cost.

Storyline flow

Beat 1 — Useful consent has already happened

The player previously chose a clause, public hearing, proxy posture, settlement, edit patch, memorial license, or lawful escrow. That choice did something useful.

Examples:

• schedule stabilized;
• sponsor default paused;
• audit passed;
• continuity became watchable;
• public panic dropped;
• route access opened;
• custody dispute was delayed.

The new storyline does not undo that success.

Beat 2 — The debt carrier becomes visible

A row enters 同意债转移案卷. It names the original subject, state, proof, relief, beneficiary, and current carrier or explicit absence.

Beat 3 — Carrier assignment review

The player resolves 同意债分配复核. The rite asks who will carry the debt and what scar they accept.

Beat 4 — Carrier changes future play

The carrier changes what later branches cost:

• subject retained routes are cleaner but harder to schedule; -沈洛 carriage preserves legal relief but alters his trust, complicity, burden, or witness posture;
• sponsor carriage protects the slot while increasing ownership capture;
• inspector/archive carriage reduces fraud while narrowing routes to lawful-only play;
• editor carriage stabilizes continuity while growing edit/archive debt;
• public witness carriage blocks private capture while increasing exposure;
• production carriage keeps the branch alive while overloading internal handler/resource economy;
• false-clean creates reversion or hardening.

Beat 5 — Reversion or discharge

If the player names a carrier and pays a scar, the row may be assigned, escrowed, contested, or discharged with scar.

If the player hides the debt, reuses it without proof, lets proxy authority become implied consent, or treats sponsor/inspection/edit/public approval as consent, 同意债回转 fires or becomes default-ready.

Branch families

Branch A — Subject reclaim or retention

The player lets the subject keep control of consent/refusal, accepts a narrower clause, publishes refusal, or treats absence as binding.

Relief:

• consent integrity or refusal legibility rises;
• private capture can be blocked;
• later public or lawful route remains credible.

Cost:

• schedule, sponsor, inspection, public, route-asset, or recovery cost rises.

Future route effects: protected, public_only, lawful_only, or costlier.

Branch B — Shen Luo manager carriage

The player assigns沈洛 as manager bridge, refusal witness, lawful escrow handler, or sponsor broker.

Relief:

• legal relief stays usable;
• schedule or contract pressure can improve;
• the player preserves a character route if his posture is honest.

Cost:

• contract_capture, shen_luo_complicity, handler_burden, future_recovery_cost, or witness hostility may rise.

Future route effects: protected, protected_but_owned, lawful_only, contradiction_pending, or recovery_only.

Branch C — Sponsor carriage

The player lets sponsor collateral, naming right, private settlement, or stop-loss language carry the debt.

Relief:

• sponsor pressure or slot pressure may fall.

Cost:

• public distrust, fan resentment, contract capture, or future ownership debt rises.

Future route effects: protected_but_owned, sponsor_only, captured, or recovery_only.

Branch D — Inspector/archive carriage

The player routes debt into audit, lawful escrow, archive seal, or custody docket.

Relief:

• fraud, drift, or custody ambiguity improves.

Cost:

• inspection heat, bureau debt, lawful-only routing, public delay, or sponsor objection rises.

Future route effects: lawful_only, costlier, or contradiction_pending.

Branch E — Editor/black-box carriage

The player hides the debt in continuity work or makes an edit proof carry the contradiction.

Relief:

• continuity hazard or audience churn drops.

Cost:

• edit debt, archive debt, public distrust, or later contradiction rises.

Future route effects: public_only, costlier, contradiction_pending, or recovery_only.

Branch F — Public witness carriage

The player publishes the debt through fan ledger, historian note, public receipt, witness oath, or pirate relay.

Relief:

• private capture is blocked;
• public legitimacy, audience stability, or fan trust rises.

Cost:

• sponsor retaliation, inspection heat, witness risk, fan resentment, or public grief instability rises.

Future route effects: public_only, protected, or costlier.

Branch G — Production carriage

The player keeps the debt inside the production desk rather than giving it to a faction.

Relief:

• the current branch survives;
• faction capture is delayed.

Cost:

• handler burden, unstaffed ticket risk, production lane scar, or future recovery cost rises.

Future route effects: costlier, contradiction_pending, or recovery_only.

Branch H — False-clean reversion

The player refuses to name a carrier or lets authority imply consent.

Relief:

• immediate pressure may still fall.

Cost:

• 同意债回转 arms or fires;
• a witness, subject, sponsor, inspector, editor, public, route claimant, or false owner attacks the clean route.

Future route effects: hostile, recovery_only, blocked, or captured.

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:

• consent_debt
• consent_integrity
• refusal_legibility
• contract_capture
• shen_luo_trust
• shen_luo_complicity
• handler_burden
• sponsor_stop_loss_pressure
• inspection_heat
• bureau_favor_debt
• edit_debt
• archive_debt
• public_receipt_legitimacy
• public_receipt_distrust
• fan_oxygen_resentment
• continuity_hazard
• reality_drift
• route_asset_pressure
• future_recovery_cost
• false_owner_hardened

Integration notes

• With 沈洛合同捕获分岔线, this storyline begins after a clause result and tests whether沈洛’s posture persists.
• With Shen Luo Storyline, it gives his route a downstream use beyond the first capture/recruit/miss branch.
• With 黎星瞳自我线, it prevents saint persona utility from becoming implied selfhood consent.
• With Mu Ning Storyline, protective consent for a fragile newcomer can help but must leave ownership or recovery consequences.
• With Orion Breath Storyline, sponsor carriage converts relief into capture debt.
• With Han Cutroom Storyline, cutroom continuity can carry proof but not consent.
• With Inspector Rhee Archive Storyline, audit proof can narrow route legality without replacing consent.
• With 和解反震账本, this is the consent-specific row that can be one aftershock surface.
• With 处理人负荷账本, named carriers become burdened people, not free tools.
• With Route Assets and Custody, the consent debt row itself can become protected, captured, hostile, false-owner, sacrificed, or route asset state.

Missability and recovery

This storyline is missable when the player treats a consent-based relief as clean and keeps playing other systems without a debt carrier.

Missed states:

• no_carrier_false_clean;
• consent_debt_reverted;
• consent_debt_hardened;
• false_owner_hardened;
• shen_luo_hostile_witness;
• subject_reclaim_hostile;
• recovery_only_route.

Recovery is allowed only through visible cost:

• reopen assignment review with stronger proof;
• return debt to subject and accept route/schedule cost;
• publish a public receipt and accept sponsor or inspection backlash;
• file lawful escrow and accept lawful-only play;
• ask editor/black-box to carry proof and accept edit/archive debt;
• sacrifice a route asset or favor to unwind false ownership;
• recover沈洛 from sponsor broker or hostile witness into refusal witness, if his route has not been fully missed.

Multi-session evidence expectation

A correct implementation can inherit a source consent row from one replay/session and resolve it in a later review/session.

Expected evidence:

storyline_id: storyteller.storyline.consent_debt_transfer.v1
source_session_id: <session that created consent relief>
review_session_id: <session that assigned or challenged the debt>
seed: <deterministic seed>
entry_state:
  source_row_id: <row id>
  subject_id: <subject id or explicit absence>
  original_consent_state: <state>
  relief_created: [<relief>]
  beneficiary: <beneficiary>
  carrier_before: <carrier or none>
  no_fixed_turn_trigger: true
offered_choices:
  - card.consent_debt_transfer_docket
  - rite.consent_debt_assignment_review
  - return_to_subject
  - shen_luo_carried
  - sponsor_carried
  - inspector_archive_carried
  - editor_black_box_carried
  - public_witness_carried
  - production_carried
  - no_carrier_false_clean
branch_result:
  carrier_after: <carrier>
  debt_state_after: <state>
  counter_deltas: {}
  future_route_effect_after: <effect>
  event_seen_or_armed: <optional consent debt reversion>
assertions:
  - prior relief persists
  - original consent/refusal remains visible
  - carrier is named or explicit false-clean exists
  - at least three counters or states mutate
  - future route effect changes

Non-goals

• Not another generic liability ledger.
• Not a duplicate of first consent negotiation.
• Not a moralized punishment system.
• Not a turn-count consequence.
• Not satisfied by page existence.
• Not satisfied by reducing pressure while leaving consent/refusal, carrier, and future route unchanged.
• Not a way to imply consent from sponsor funding, inspection seal, proxy authority, edit checksum, public applause, or route utility.