Confidant Repair Docket / 私约修复案卷

Confidant Repair Docket is a route-bearing card for the moment after a private promise has already been breached, overrun, publicly softened, or used outside its named scope.

It does not record whether the producer is sorry. It records whether the harmed confidant can author concrete repair terms that future route readers must respect.

Card role

The docket prevents a breached promise from collapsing into trust -1, a generic apology, or a clean recovery flag. A valid repair row keeps three things separate:

  • what was breached;
  • what the character now demands;
  • what route, proof, recruitment, or public surface will remain changed even if the repair succeeds.

Required row

confidant_repair_row:
  repair_id: <stable id>
  source_promise_id_or_absence: <promise id or explicit_absence>
  confidant_character: yu_lan | baiya | shen_luo | han_yanshuang | mu_ning | ai_sheng | li_xingtong | equivalent
  breach_state_before: breached | hostile | exposed | public_only | lawful_only | sponsor_only | missed | recovery_only | equivalent
  breached_material: source_identity | private_refusal | witness_name | checksum | route_secret | selfhood_boundary | child_voice_trace | unreleased_take | equivalent
  violated_scope: private_only | named_hearing_only | anonymous_public | lawful_only | route_asset_only | emergency_only | disputed | explicit_absence
  breach_reader: public | lawful_table | sponsor | archive | management | route_claimant | broadcast_reality | fan_public | equivalent
  harm_named_by_character: <one sentence harm claim>
  demanded_repair: return_material | replace_proof | publish_boundary | shield_source | pay_witness | withdraw_recap | route_separation | public_contrition | handler_recusal | equivalent
  proof_required_by_character: oath | receipt | checksum | public_addendum | lawful_seal | witness_payroll | route_quarantine | explicit_absence | equivalent
  nonnegotiable_limit: no_public_name | no_sponsor_copy | no_archive_reuse | no_broadcast_echo | no_handler_contact | no_route_asset_use | explicit_absence | equivalent
  selected_repair_posture: accept_terms | negotiate_restitution | public_contrition | shielded_repayment | route_separation | refuse_repair | performative_apology_default
  repair_state_after: pending | accepted | partial | refused | performative | hostile | route_separated | missed | recovery_only | equivalent
  future_character_or_route_effect: recruitable_again_with_cost | handler_unavailable | proof_replaced | public_addendum_required | route_costlier | character_hostile | route_blocked | ending_scar | equivalent

A row fails if it only stores mood, loyalty, romance state, generic affinity, or a public statement without the character-authored repair term.

Valid entry surfaces

A repair row may be created from:

Repair states

repair_states:
  accepted:
    meaning: the character accepts specific repair terms; no universal forgiveness is created
  partial:
    meaning: one reader accepts the repair while another reader or route keeps the scar
  refused:
    meaning: the producer preserves proof or schedule but loses repair access
  performative:
    meaning: apology wording exists without restitution and arms the default
  hostile:
    meaning: the character becomes an opposing witness, claimant, or route blocker
  route_separated:
    meaning: the character may remain alive in story but refuses this route asset or desk
  recovery_only:
    meaning: the route can continue only through replacement proof, public addendum, shield, or ending scar

Counter contract

Every resolved row must mutate at least one relief, one cost, and one future character or route effect.

Expected surfaces include confidant_repair_legitimacy, character_availability, recruitability, missability, proof_replacement_cost, witness_protection_cost, handler_burden, public_receipt_distrust, sponsor_capture, archive_debt, producer_license_pressure, broadcast_reality_drift, and ending_scar_pressure.

Non-goals

  • Not an apology flavor card.
  • Not a relationship meter.
  • Not a way to erase 私约承诺账本.
  • Not valid unless the harmed character, breached material, demanded repair, proof of repair, and future reader are visible or explicitly absent.