Confidant Repair Terms / 私约修复条件线

Confidant Repair Terms is a small aftermath storyline for named characters whose private material was used outside scope. It turns the aftermath of 私约违背线 into concrete route play: the harmed character can demand restitution, limits, proof of repair, and future route consequences.

This line answers a gap left after promise-breach resolution: once a character has been harmed, what exactly would make them work with the producer again, and what remains changed even if they do?

Storyline premise

A confidant discovers that a protected confession, refusal, source identity, checksum, witness name, route secret, child-voice trace, unreleased take, or selfhood boundary was used beyond the original promise.

The producer can no longer solve the pressure with a general apology. The character now writes terms:

• what must be returned, corrected, shielded, or replaced;
• what reader must see proof of repair;
• what use remains forbidden;
• what route can reopen, become costlier, remain blocked, or become recovery-only.

Content pack

Observed execution surfaces:

• 私约修复条件机制;
• 私约修复案卷;
• 私约修复面谈;
• 私约修复默认.

Adjacent pressure lines:

• 公开悔过账本 when public repair is demanded;
• 受保护证人薪册 when witness/source protection is demanded;
• 证人报复链 when exposure created retaliation risk;
• 处理人负荷账本 when mediation, shielding, or recusal costs a handler.

Character hooks

• 郁蓝未授权史官线 may demand source protection, correction of authorship, or a boundary on archive reuse.
• 白鸦黑箱补丁羁押线 may demand checksum return, route quarantine, or proof replacement.
• Shen Luo Storyline may demand contract language be publicly narrowed instead of privately excused.
• 韩砚霜白手套例外线 may demand lawful-only repair and refuse public apology as insufficient.
• Mu Ning Storyline may demand route separation so her vulnerability stops being an unlock key.
• 艾笙海盗频段童声线 may demand protection of the child-voice trace and a ban on sponsor-safe copy.
• 黎星瞳自我线 may demand that selfhood consent be re-separated from broadcast consent.

Flow

storyline_flow:
  entry:
    condition: breach_state_visible_and_character_demands_repair
    invalid_if: fixed_turn_day_week_raw_count_dashboard_or_lens_health
  pressure:
    character_names_harm: true
    demanded_repair_visible: true
    proof_required_visible_or_explicit_absence: true
    future_reader_consumes_result: true
  rite:
    assign: storyteller.rite.confidant_repair_interview.v1
  outcomes:
    - accept_terms
    - negotiate_restitution
    - public_contrition
    - shielded_repayment
    - route_separation
    - refuse_repair
    - performative_apology_default

Branch shape

Accept terms

The producer satisfies the character-authored demand. The route can reopen only in the named scope. Cost must remain visible: proof replacement, public addendum, witness payment, schedule delay, sponsor pressure, archive debt, handler burden, or route asset cost.

Negotiate restitution

The producer narrows the demanded repair. One reader may accept while another stays harmed. This creates partial repair, split-reader state, or future objection.

Public contrition

The breach becomes public repair only when the character demanded public acknowledgement. It helps public legitimacy but increases sponsor, license, or archive pressure.

Shielded repayment

The producer pays, protects, or shields the exposed source. This can preserve a witness or route but creates payroll, anonymity, and handler burden.

Route separation

The character refuses to be a component of the contaminated route. They may remain alive and available elsewhere, while this route becomes costlier, blocked, or recovery-only.

Refuse repair

The producer keeps proof, schedule, or sponsor position and loses repair access. The character becomes hostile, unavailable, missed, or recovery-only.

Performative apology default

The desk files apology without satisfying terms. 私约修复默认 records false repair, character terms hidden, and future route scar.

Success contract

Every non-default outcome must include:

success_contract:
  relief: at_least_one
  cost: at_least_one
  future_character_or_route_effect: at_least_one
  no_universal_forgiveness: true
  no_generic_affinity_result: true

Non-goals

• Not a count target.
• Not a generic relationship repair node.
• Not a public apology wrapper.
• Not a way to erase breach history.
• Not a fixed turn or cleanup phase.