Confidant Promise Breach / 私约违背线

Confidant Promise Breach is a character-pressure storyline for the moment a private promise becomes useful to the production desk.

The current corpus is strong at legal service, relay scope, caption reliance, proof carryover, faction commitments, mandate scarcity, handler burden, and failure arbitration. The weak surface is more personal: a named character can trust the producer with material that is powerful enough to solve a route, but that trust is not the same thing as permission to spend the material.

This storyline turns that gap into playable pressure: what did the producer promise, what is now being asked, who will be harmed if the promise is spent, and what future character route changes because of the choice?

Why this expansion matters

Without this storyline, several existing systems can accidentally flatten character play:

• 导出证据回流分岔线 can treat a returned proof object as usable without asking whether a named character gave it privately.
• 处理人负荷账本 can charge labor cost while missing the promise boundary that created the burden.
• 证人报复链 can punish exposure after the fact, but the private promise should be playable before exposure becomes inevitable.
• 同意债转移线 can move consent debt, but private promise scope should decide whether the debt was ever spendable.
• Route Assets and Custody can mark an object protected, hostile, captured, or recovery-only, but a private promise should be able to create that route state through character trust.

The goal is not to add relationship filler. The goal is to make late-route character content bite into proof economy, recruitability, missability, and broadcast reality.

Bound content pack

This storyline binds:

• 私约违背机制;
• 私约承诺账本;
• 私约承诺听证;
• 私约违背默认.

State-triggered entry

Open this storyline only when all of the following are visible or explicitly absent:

entry_state_required:
  trigger_kind: state_pressure
  named_confidant_or_explicit_absence_visible: true
  private_promise_or_boundary_present: true
  protected_material_visible: true
  requested_use_present: true
  permission_scope_visible_or_explicit_absence: true
  pressure_actor_visible: true
  threat_if_unused_visible: true
  future_character_or_route_consumes_promise_state: true
  player_can_honor_renegotiate_anonymize_protect_trade_refuse_breach_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_promise_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

The storyline fails if it opens from relationship points, fixed sequence position, chapter quota, raw character count, generic affection, dashboard state, or lens health.

Storyline spine

Beat 1 — A private promise becomes useful

A named character shares material under private scope: a witness name, source identity, refusal, checksum, rehearsal truth, selfhood boundary, contract phrase, child-voice trace, or unreleased take.

The material is not immediately spent. It enters 私约承诺账本.

Beat 2 — A pressure actor requests use

A sponsor, archive, inspector, fan public, management table, editor, route claimant, lawful desk, or broadcast-reality reader wants to consume the material as proof, public wording, lawful appeal, route unlock, sponsor copy, management metric, handler authority, or witness protection.

The threat if unused must be concrete: route blocked, legal exposure, public distrust, witness unprotected, proof gap, handler burden, sponsor capture, archive debt, or equivalent.

Beat 3 — Scope is tested before use

The player must run 私约承诺听证 or an equivalent rite before the material becomes route proof.

The hearing separates:

• the character who trusted the producer;
• the protected material;
• the requested use;
• permission scope;
• pressure actor;
• shield or cost;
• future character or route consumer.

Beat 4 — The producer chooses a scarred posture

The player may honor privacy, renegotiate consent, anonymize the source, make protected disclosure, trade the promise, refuse use, commit a public breach, or allow silent breach default.

Every constructive branch must improve something and scar something. Clean universal permission is not valid.

Beat 5 — Future character state changes

The route must remember whether the promise was honored, renegotiated, anonymized, protected, traded, refused, breached, hostile, missed, or recovery-only.

Future effects may include route costlier, substitute proof required, handler unavailable, recruit missed, witness hostile, lawful-only proof, public-only proof, sponsor gate, public contrition required, or ending scar.

Branch map

Branch	Immediate relief	Cost/scar	Future state
Honor privacy	trust and boundary preserved	proof gap, route cost, sponsor/archive pressure	substitute proof, route costlier, handler burden
Renegotiate consent	scoped use becomes legitimate	consent debt, notice burden, future recovery cost	scoped-use-only, further notice, character route costlier
Anonymize source	use possible without exposure	source ambiguity, archive debt, weaker proof	corroboration required, contradiction pending
Protected disclosure	hearing opens under shield	witness payroll, inspection heat, route delay	shield required, witness route with cost
Trade promise	immediate route pressure drops	faction capture, private capture, public distrust	faction gate, character hostile or costlier
Refuse use	breach blocked	legal exposure, public distrust, proof gap	appeal, addendum, substitute proof required
Public breach	stronger public truth or route unlock now	trust loss, exposure, recruitability damage	hostile witness, contrition, recovery-only risk
Silent breach default	fastest desk consumes material	hidden breach hardens	hostile, unavailable, missed, blocked, recovery-only

Character hooks

• 郁蓝未授权史官线 can hold a protected source identity that public proof wants to expose.
• 白鸦黑箱补丁羁押线 can share a checksum or clean-grief patch under edit-room boundary.
• Shen Luo Storyline can privately phrase a contract escape that later becomes sponsor capture if spent.
• 韩砚霜白手套例外线 can provide lawful exception material whose human scope must survive.
• Mu Ning Storyline can be protected from glass-newcomer vulnerability being converted into public proof.
• 艾笙海盗频段童声线 can make a child-voice trace playable only with shield or anonymity.
• 黎星瞳自我线 can enforce that selfhood consent is not broadcast permission.

Missability and recovery

This storyline is missable when a route consumes private material without creating or reading a promise row.

Missed states include promise_breached, confidant_hostile, handler_unavailable, recruit_missed, source_exposed, private_capture, blocked, and recovery_only.

Recovery is allowed only through visible cost: apology, restitution, public contrition, protected witness payroll, anonymized refile, lawful rehearing, substitute proof, route quarantine, or ending scar audit. Recovery cannot retroactively make the original private promise universal consent.

Replay evidence expectation

storyline_id: storyteller.storyline.confidant_promise_breach.v1
session_id: lens-confidant-promise-breach-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  named_confidant_or_explicit_absence_visible: true
  private_promise_or_boundary_present: true
  protected_material_visible: true
  requested_use_present: true
  permission_scope_visible_or_explicit_absence: true
  pressure_actor_visible: true
  threat_if_unused_visible: true
  future_character_or_route_consumes_promise_state: true
  no_fixed_turn_trigger: true
promise_row:
  card: storyteller.card.confidant_promise_ledger.v1
  promise_id: <stable id>
  confidant_character: <character>
  protected_material: <material>
  permission_scope: <scope>
  requested_use: <use>
hearing:
  rite: storyteller.rite.confidant_promise_hearing.v1
  selected_posture: honor_privacy | renegotiate_consent | anonymize_source | protected_disclosure | trade_promise | refuse_use | public_breach | silent_breach_default
  handler_or_absence: <handler or explicit_absence>
  shield_or_cost_or_absence: <shield cost or explicit_absence>
branch_result:
  promise_state_after: <state>
  character_state_after: <state>
  protected_material_state_after: <state>
  future_character_or_route_effect: <effect>
  counter_deltas:
    relief: []
    cost: []
    future: []
default:
  event_seen_or_armed: storyteller.event.confidant_breach_default.v1 | explicit_absence
assertions:
  - entry_is_state_triggered
  - named_confidant_and_protected_material_are_visible
  - requested_use_and_permission_scope_are_separate
  - threat_if_unused_is_concrete
  - hearing_assignments_are_explicit
  - branch_outcomes_diverge
  - success_has_relief_cost_and_future_effect
  - breach_mutates_character_availability_or_recruitability
  - no_generic_affinity_meter
  - no_universal_private_promise_as_permission
  - no_fixed_turn_day_week_raw_count_dashboard_or_lens_health_trigger

Non-goals

• Not romance, affection, or generic friendship content.
• Not a governance page.
• Not bulk character expansion.
• Not raw recruitable-count satisfaction.
• Not valid unless private trust can change proof, route state, recruitability, missability, or future character availability.
• Not a replacement for consent debt, evidence carryover, handler burden, witness reprisal, or protected witness payroll.