Baiya Patch Custody Readback / 白鸦补丁羁押回读线

Baiya Patch Custody Readback is the system-facing wrapper above Baiya Blackbox Patch Custody. The existing Baiya character storyline proves whether Baiya can be offered, recruited, scoped, refused, quarantined, captured, hostile, missed, or explicitly absent. This storyline asks the wider implementation question: when a future reader consumes a black-box patch, did the patch row preserve source scar, scope, omitted reader, proof bridge, handler, cost, and future route effect?

The line is needed because Baiya can be unavailable or deliberately absent while the patch custody state still matters. A producer license, scar convergence result, clean-ending asset, cutroom priority row, broadcast asset afterlife copy, appeal residue, public contrition, or broadcast reality drift surface must never treat a black-box patch as a clean universal correction.

Playable Question

When a scarred result can be made watchable by a black-box patch, does production scope the patch, recruit Baiya as a protected patch asset, refuse the smoothing, quarantine the copy, split future readers, hand the patch to a lawful or public reader, or file it as clean and arm the false-clean default?

Every answer must name:

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

State-Triggered Entry

Open this storyline only from live state pressure:

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_scope_recruit_refuse_quarantine_split_handoff_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Do not open from a fixed turn, fixed day/week, chapter quota, raw scar count, dashboard state, lens health, or a generic continuity problem without a future reader.

Bound Content Pack

• Baiya Blackbox Patch Custody defines source preservation, Baiya state or explicit absence, patch states, branch costs, and false-clean default.
• Baiya Blackbox Patch Custody Storyline remains the character route for recruitment, missability, capture, and hostility.
• Baiya Clean-Grief Patch Docket records source patch request, selected patch row, authority, proof bridge, omitted reader, scope, and future effect.
• Baiya Blackbox Patch Hearing resolves scoped, recruited, refused, quarantined, split, lawful/public handoff, and false-clean branches.
• Baiya False-Clean Patch Default hardens hidden source scar, missing scope, omitted reader, captured patch, or unscoped future consumption.
• Baiya Patch Custody Readback Lens observes the non-character system contract.

Storyline Spine

Beat 1 - A scarred result asks for watchability

A source result is useful but not clean. It may come from appeal residue, scar convergence, producer-license encumbrance, clean-ending custody, broadcast asset afterlife, cutroom priority, public contrition, broadcast reality drift, route-asset custody, or an equivalent scarred surface.

The source result remains true. This storyline never retries it or lets the patch erase it.

Beat 2 - The docket makes the patch a custody object

Create or refresh Baiya Clean-Grief Patch Docket.

The docket must record:

baiya_patch_custody_docket:
  source_patch_request:
    source_surface: <surface>
    source_row_or_result_id: <stable id>
    contradiction_kind: <kind>
    source_relief_preserved: <relief>
    source_cost_preserved: <cost>
  patch_row:
    row_id: <stable id>
    intended_relief: <relief>
    patch_authority_or_absence: <authority or explicit_absence>
    omitted_or_delayed_reader: <reader or explicit_absence>
    proof_bridge_or_absence: <proof or explicit_absence>
    patch_scope: continuity_only | public_version_only | lawful_version_only | sponsor_package_only | recovery_copy_only | split_copy | forbidden | explicit_absence
  baiya_state_or_explicit_absence: <state>
  future_reader_or_route_effect: <effect>

It is invalid if it records only safe edit, clean grief, continuity issue, or Baiya opportunity.

Beat 3 - The hearing selects patch custody

Run Baiya Blackbox Patch Hearing. Valid posture families:

• 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, proof bridge or explicit absence, patch scope or explicit absence, omitted reader, branch cost, and target future reader.

Beat 4 - Future play consumes the patch state

The storyline is incomplete until a future reader consumes the result. Valid consumers include producer-license review, public contrition, clean-ending custody, broadcast asset afterlife, scar convergence, cutroom priority, broadcast reality drift, and route-asset custody.

The consuming future must know whether the patch is scoped, recruited, refused, quarantined, split, reader-scoped, captured, false-clean, hostile, or recovery-only.

Beat 5 - False-clean defaults remain durable

If a future surface cites the patch while scope, source scar, proof bridge, omitted reader, Baiya state or explicit absence, handler, or future effect is hidden, Baiya False-Clean Patch Default fires or remains armed.

Branch Map

Branch	Immediate relief	Cost/scar	Future state
Scoped black-box patch	continuity, legibility, route usability, or audience stability improves	edit debt, source ambiguity, inspection heat, or public distrust rises	accepted with edit debt, audit required, split required, or costlier
Recruit Baiya asset	future black-box stabilization becomes assignable	handler burden, white-glove suspicion, sponsor leverage, or fan distrust rises	Baiya required or patch review required
Refuse patch	source integrity or omitted-reader visibility is protected	broadcast, sponsor, correction, schedule, or black-screen pressure rises	alternate route, costlier route, or recovery-only
Quarantine patch	drift, fraud, or false-owner risk falls	current route blocks, archive debt rises, or recovery cost rises	audit required, lawful appeal, or recovery-only
Split patch copy	incompatible futures stay legible	ambiguity, edit debt, public distrust, or future reconciliation cost rises	split required or contradiction pending
Lawful/public handoff	one reader contains the patch	bureau debt, heat, sponsor pressure, or witness exposure rises	lawful-only, public-only, audit required, or costlier
False-clean default	no clean relief	capture, drift, source contradiction, hostility, or black-screen pressure rises	blocked, hostile, captured, black-screen fold, or recovery-only

No branch may make the patch clean for public, lawful, sponsor, archive, edit, route-asset, and broadcast-reality readers at once.

Missability And Recovery

This storyline is missed when implementation:

• hides the source row or source cost;
• stores Baiya as flavor text without state or explicit absence;
• lets a patch proceed without scope;
• hides omitted reader, proof bridge, handler, or future route effect;
• treats a recruited Baiya as a relationship reward with no later assignment change;
• fires from fixed time, raw count, dashboard state, or lens health;
• lets an overcleaned patch resolve without durable false-clean default state.

Recovery requires a scarred readback: reopen the docket, publish omitted reader receipt, attach lawful seal, reveal source fragment, retire the patch, rescue Baiya from capture, or quarantine the copy. A recovered patch may support a future route only with audit, edit debt, public countercopy, license review, source ambiguity, future recovery cost, or another visible scar.