Baiya Blackbox Patch Custody Storyline / 白鸦黑箱补丁羁押线

Bound character: Baiya.

Baiya Blackbox Patch Custody turns Baiya from a one-line black-box editor into a recruitable, missable, capturable, and hostile route asset. Her pressure is not that she can edit. Her pressure is that she can make a scarred broadcast watchable while tempting the production to pretend the scar is gone.

The recent corpus is already strong at making aftermaths visible: 申诉残留分流线 limits scarred credits, 伤痕汇流台线 stops shared stabilizers from becoming clean, and 制作人牌照负担线 turns producer authority into collateral. Baiya is the character who can smooth those states into broadcast reality. This storyline makes that smoothing playable and dangerous.

Primary playable question

When a black-box edit could make a contradiction survivable, does the producer scope Baiya’s patch, recruit her as a protected route asset, refuse the clean-grief temptation, quarantine the copy, split future readers, hand the patch to a lawful or public reader, suppress or sell the patch, or let the edit harden into false-clean broadcast reality?

No branch may make appeal residue, scar convergence, producer-license encumbrance, clean-ending custody, route-asset provenance, or broadcast reality drift clean for free.

State-triggered entry

Open this storyline only when all are true:

entry_state:
  trigger_kind: state_pressure
  blackbox_edit_can_change_broadcast_reality: true
  contradiction_or_scar_source_present: true
  source_surface_any:
    - appeal_residue
    - scar_convergence
    - producer_license_encumbrance
    - clean_ending_seizure
    - broadcast_asset_afterlife
    - cutroom_priority
    - public_contrition
    - broadcast_reality_drift
    - route_asset_custody
    - equivalent
  source_relief_and_cost_visible: true
  future_reader_present: true
  omitted_or_delayed_reader_possible: true
  baiya_state_or_explicit_absence_visible: true
  player_can_accept_scope_refuse_or_quarantine_patch: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true

This storyline never opens from fixed turn count, fixed day, fixed week, chapter quota, raw content count, raw scar count, dashboard state, or lens-health state.

Content pack

Character

• Baiya stores the character identity: black-box editor, AI-adjacent route asset, clean-grief temptation, and contested patch carrier.

Mechanic

• 白鸦黑箱补丁羁押机制 defines patch rows, source preservation, Baiya state, omitted reader, branch contract, false-clean default, and future reader consumption.

Card

• 白鸦洁净悲伤补丁案卷 records source surface, contradiction kind, Baiya state or absence, patch authority, proof bridge, omitted reader, scope, relief, cost, and future route effect.

Rite

• 白鸦黑箱补丁听证 resolves scoped patch, recruitment, refusal, quarantine, split, lawful/public handoff, suppression, sale, or overcleaning.

Event

• 白鸦伪洁净补丁默认 fires or arms when the patch is hidden, overscoped, captured, filed as clean, used without Baiya state, or consumed by a future reader without scope.

Storyline spine

Beat 1 — A contradiction asks to become watchable

A current broadcast, route asset, license review, correction slot, clean-ending custody fight, or public statement wants a contradiction made legible enough to air.

Valid sources include:

• a routed appeal residue that can support one reader but not all readers;
• a scar convergence docket whose stabilizer cannot be used cleanly;
• a producer-license encumbrance row that wants public statement, route-asset release, lawful stay, or correction authority;
• a clean-ending asset threatened by sponsor/editor/inspector/public copy claims;
• a broadcast asset provenance split between lawful copy, public receipt, editor cut, sponsor package, pirate echo, or quarantine copy;
• a cutroom priority row where a safe edit starves raw proof;
• a drift docket where the aired version and evidence version diverge.

The source result remains true. Baiya’s storyline does not retry it.

Beat 2 — Baiya appears as docket, not utility

Create or refresh 白鸦洁净悲伤补丁案卷. The docket must name:

• source surface and source row/result id;
• source relief and cost;
• contradiction kind;
• Baiya state or explicit absence;
• patch authority or absence;
• proof bridge or absence;
• omitted or delayed reader;
• patch scope;
• future reader or route effect if accepted;
• future route effect if ignored or overcleaned.

Beat 3 — The producer chooses custody of the patch

Run 白鸦黑箱补丁听证. The player chooses among:

• scoped black-box patch;
• recruit Baiya as patch route asset;
• refuse patch;
• quarantine patch;
• split patch copy;
• hand to lawful or public reader;
• suppress or sell patch;
• overclean or hide patch.

Every branch must assign handler or explicit absence, patch authority or explicit absence, proof bridge or explicit absence, patch scope or absence, omitted reader, branch cost, and target future reader.

Beat 4 — Baiya changes state

Baiya must not remain a passive tool. She becomes one of:

• uncontacted;
• offered;
• recruited;
• scoped tool;
• protected route asset;
• quarantined;
• suppressed;
• captured;
• hostile;
• missed;
• explicit absence;
• recovery-only.

Her state must change later route acceptance. Recruited or protected Baiya must unlock assignments that missed, hostile, captured, or absent Baiya cannot support.

Beat 5 — The future reader consumes the patch state

The storyline is incomplete until a future route, rite, card, or event reads the result.

Valid future consumption:

• producer-license review accepts a patched statement only as encumbered authority;
• public contrition accepts a public version while lawful route becomes costlier;
• clean-ending custody records editor-safe copy, public-countercopy, sponsor-capture, quarantine, or false owner;
• broadcast asset afterlife records the patch as lawful-only, public-only, sponsor-only, editor-safe, split, or recovery-only;
• scar convergence accepts a stabilizer as watchable but not clean;
• broadcast reality drift stores contradiction pending, false-clean patch, or black-screen fold;
• route-asset custody marks Baiya protected, captured, hostile, missed, or recovery-only.

Branch map

Branch	Baiya state	Relief	Cost	Future effect
Scoped patch	scoped_tool or protected_route_asset	continuity, legibility, route usability, or audience stability improves	edit debt, source ambiguity, heat, or public distrust rises	accepted with edit debt, audit required, split required, or costlier
Recruit patch asset	recruited or protected_route_asset	future black-box stabilization becomes assignable	handler burden, white-glove suspicion, sponsor leverage, or fan distrust rises	Baiya required, patch review required, accepted with cost
Refuse patch	offered, refused, or explicit absence	false-clean pressure and omitted-reader harm fall	broadcast, sponsor, correction, or black-screen pressure rises	alternate route required, current route costlier, recovery-only if unpaid
Quarantine patch	quarantined or protected	drift/fraud/false-owner risk falls	current route blocks, inspection/sponsor pressure or recovery cost rises	audit, lawful appeal, recovery-only
Split patch copy	scoped or split	incompatible futures stay legible	ambiguity, edit debt, distrust, future reconciliation cost rises	split required, scoped acceptance, contradiction pending
Lawful/public handoff	scoped or protected	custody clarity or public receipt improves	bureau debt, heat, sponsor pressure, witness exposure rises	lawful-only, public-only, audit required, costlier
Suppress/sell/overclean	captured, hostile, missed, false-clean, recovery-only	no true relief	capture, false-clean, drift, hostility, license pressure rises	default event; blocked, captured, hostile, black-screen, recovery-only

Counter contract

Every branch must mutate at least three counters or durable states. At least one must be relief, one must be cost, and one must change future reader or route acceptance.

Primary surfaces:

• baiya_state
• baiya_trust
• blackbox_patch_integrity
• clean_grief_temptation
• edit_debt
• source_ambiguity
• reality_drift
• continuity_hazard
• public_receipt_legitimacy
• public_receipt_distrust
• fan_oxygen_resentment
• producer_license_pressure
• false_clean_authority
• inspection_heat
• archive_debt
• sponsor_stop_loss_pressure
• contract_capture
• handler_burden
• white_glove_suspicion
• route_asset_pressure
• black_screen_pressure
• future_recovery_cost
• hostile_counterproof

Missability and recovery

Baiya is missed when the player lets a black-box patch resolve a contradiction without a docket, scope, proof bridge, omitted reader, handler, or future reader effect.

Missed or default states include:

• baiya_missed_by_clean_package;
• baiya_captured_by_sponsor_or_archive;
• hostile_blackbox_counterproof;
• false_clean_patch_hardened;
• patch_quarantine_only;
• blackbox_recovery_only;
• source_contradicted_after_patch;
• producer_license_patch_overclaim.

Recovery is allowed only with visible scar:

• reopen the docket and scope the patch;
• publish omitted reader receipt;
• attach lawful seal and accept public distrust;
• reveal source fragment and accept edit debt;
• retire the patch and sacrifice current route;
• rescue Baiya from capture with handler burden, sponsor backlash, or inspection heat;
• quarantine the copy and accept recovery-only access.

Replay/session evidence shape

storyline: storyteller.storyline.character.baiya.v1
session_id: lens-baiya-blackbox-patch-custody-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  blackbox_edit_can_change_broadcast_reality: true
  contradiction_or_scar_source_present: true
  source_surface: <source>
  source_relief_and_cost_visible: true
  future_reader_present: true
  omitted_or_delayed_reader_possible: true
  baiya_state_or_explicit_absence_visible: true
  no_fixed_turn_trigger: true
offered:
  character: char.baiya
  card: storyteller.card.baiya_clean_grief_patch_docket.v1
  rite: storyteller.rite.baiya_blackbox_patch_hearing.v1
branch_runs:
  scoped_or_recruited:
    selected_response: scoped_blackbox_patch | recruit_baiya_patch_asset
    patch_scope_or_absence: <scope>
    proof_bridge_or_absence: <proof>
    omitted_or_delayed_reader: <reader>
    baiya_state_after: scoped_tool | recruited | protected_route_asset
    future_route_effect: <effect>
    counter_deltas: {}
  refused_or_quarantined:
    selected_response: refuse_patch | quarantine_patch
    baiya_state_after: refused | quarantined | explicit_absence
    future_route_effect: <effect>
    counter_deltas: {}
  default_branch:
    selected_response: suppress_or_sell_patch | overclean_or_hide_patch
    event_seen_or_armed: storyteller.event.baiya_false_clean_patch_default.v1
    baiya_state_after: captured | hostile | missed | false_clean_tool | recovery_only
    future_route_effect: blocked | costlier | captured | hostile | black_screen_fold | recovery_only
    counter_deltas: {}
downstream_read:
  reader: producer_license | public_contrition | clean_ending_custody | asset_afterlife | scar_convergence | broadcast_reality_drift | route_asset_custody | equivalent
  consumed_state: <baiya_or_patch_state>
  route_effect_after_read: <effect>
assertions:
  - entry_is_state_triggered
  - source_scar_preserved
  - baiya_state_or_absence_visible
  - patch_scope_and_omitted_reader_visible
  - rite_requires_handler_proof_scope_cost_and_future_reader
  - recruited_scoped_refused_quarantined_default_branches_diverge
  - success_has_relief_cost_and_future_gate
  - false_clean_patch_fires_or_arms_default
  - future_reader_consumes_baiya_or_patch_state
  - no_fixed_turn_trigger

Non-goals

• Not a generic editor biography.
• Not a broad AI-cleanup system.
• Not a fixed-turn recruit/miss window.
• Not raw count expansion.
• Not a clean ending reward.
• Not a replacement for Han Cutroom, Yu Lan, public contrition, clean-ending seizure, broadcast asset afterlife, appeal residue, scar convergence, producer-license encumbrance, or broadcast reality drift.
• Not valid if Baiya’s patch does not preserve source scars, name omitted readers, mutate Baiya state, and change future route acceptance.