Backbeat Custody Readback / 鼓点羁押回读线

Backbeat Custody Readback is the system-facing wrapper above Night-Shift Backbeat Custody. The existing Qi Jin Night-Shift Drummer character route proves whether 祁烬 can be found, recruited, protected, suppressed, made hostile, missed, or explicitly absent. This storyline asks the wider implementation question: when a blacked-out broadcast leaves only a beat, did the beat packet preserve source surface, custodian, liveness claim, legality class, claimant pressure, branch cost, and future route effect before another reader consumes it?

The line is needed because 祁烬 can be unavailable while the backbeat still moves through editor continuity, sponsor sync, public receipt, pirate relay, archive admission, or route-asset recovery. A live audio trace must never become a clean universal proof token merely because the official image failed.

Playable Question

When live backbeat residue is the only durable proof that a room remained present during a blackout, does production recruit the carrier, seal the trace, mix it into continuity, package it for sponsor recovery, release it publicly, relay it through pirate sync, mute it, quarantine it, or let the chain break?

Every answer must name:

• source blackout or unreliable-feed surface;
• backbeat packet id and beat source;
• custodian or explicit absence;
• 祁烬 state or explicit absence;
• liveness claim and legality class;
• claimant families and desired future use;
• payment, protection, proof, 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
  live_audio_residue: true
  image_or_official_feed_unreliable: true
  source_surface_any:
    - blackout
    - counterbroadcast
    - memorial
    - archive_seizure
    - fan_queue
    - editor_cut
    - pirate_relay
    - sponsor_package
    - equivalent
  backbeat_can_change_future_route: true
  claimant_families_min: 2
  future_reader_or_route_present: true
  qi_jin_state_or_explicit_absence_visible: true
  player_can_recruit_seal_mix_sync_release_relay_mute_quarantine_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, day/week interval, chapter quota, raw audience count, dashboard state, lens health, or a generic blackout mood scene without a future reader.

Bound Content Pack

• Night-Shift Backbeat Custody defines the audio custody object, state-triggered entry, branch families, durable states, and future route consequences.
• Qi Jin Night-Shift Drummer remains the character route for encounter, recruitment, suppression, hostility, missability, and recovery.
• Qi Jin Night-Shift Drummer records the person plus backbeat packet state.
• Night-Shift Backbeat Custody resolves recruit, official seal, editor mix, sponsor sync, public/pirate release, mute, quarantine, and no-handler branches.
• Backbeat Chain Break hardens mishandled, unpaid, hidden, false-owned, panic-loop, or recovery-only audio custody.
• Backbeat Custody Readback Lens observes the non-character system contract.

Storyline Spine

Beat 1 - The image fails but the room keeps a rhythm

A broadcast surface becomes unreliable. The official picture may black out, split, stall, or get replaced by editor-safe continuity, but a click, drum monitor, crowd clap, breath count, mic bleed, emergency metronome, or pirate sync remains.

The beat is not ambience. It can change whether future play accepts blackout recovery, liveness proof, public receipt, editor continuity, sponsor sync, archive admission, pirate counterbroadcast, or quarantine.

Beat 2 - The card makes the beat a custody packet

Create or refresh Qi Jin Night-Shift Drummer.

The card must record:

backbeat_custody_packet:
  card_id: storyteller.card.qi_jin_night_shift_drummer.v1
  backbeat_packet_id: <stable id or explicit_absence>
  source_surface: blackout | counterbroadcast | memorial | archive_seizure | fan_queue | editor_cut | pirate_relay | sponsor_package | equivalent
  beat_source: drum_kit | monitor_click | crowd_clap | breath_count | emergency_metronome | mic_bleed | pirate_sync
  qi_jin_state_or_explicit_absence: uncontacted | recruitable | recruited | suppressed | hostile | missing | captured | recovery_only | explicit_absence
  custodian: performer | production | editor | archive | inspector | sponsor | fan_public | pirate_relay | explicit_absence
  liveness_claim: alive_room | staged_room | coerced_room | substituted_room | unknown_room
  legality_class: lawful_trace | public_receipt_only | editor_safe_mix | sponsor_sync_package | pirate_signal_only | quarantined | contested
  future_route_acceptance: accepted | rejected | costlier | recovery_only | hostile

It is invalid if the card only says audio proof, drummer available, or blackout clue without custodian, legality, liveness, and future route state.

Beat 3 - The hearing chooses custody posture

Run Night-Shift Backbeat Custody. Valid posture families:

• recruit carrier;
• official seal;
• editor mix;
• sponsor sync;
• public release;
• pirate release;
• mute trace;
• quarantine;
• explicit absence or no handler default.

Every branch must assign beat carrier or explicit absence, primary handler, custody posture, payment or protection, target future use, and future route effect.

Beat 4 - Future play consumes the beat state

The storyline is incomplete until a future reader consumes the result. Valid consumers include blackout recovery, liveness proof, public receipt, editor continuity, sponsor sync, pirate counterbroadcast, archive admission, route-asset custody, audience stability, and recovery-only quarantine.

The consuming future must know whether the beat is recruited, officially sealed, editor-mixed, sponsor-captured, publicly released, pirate-amplified, muted, quarantined, hostile, false-owned, panic-looped, or recovery-only.

Beat 5 - Chain break defaults stay durable

If a future surface cites the beat while carrier, custodian, proof, payment, protection, handler, source surface, legality class, or future use is hidden, Backbeat Chain Break fires or remains armed.

Branch Map

Branch	Immediate relief	Cost/scar	Future state
Recruit carrier	liveness clarity, audience stability, or route usability improves	performer retaliation, payroll, protection burden, or pirate attention rises	blackout recovery or liveness proof accepted with carrier cost
Official seal	admissibility and archive legitimacy improve	inspection heat, archive debt, and performer exposure rise	lawful or archive reader accepts with cost
Editor mix	broadcast legibility improves	edit debt, source ambiguity, and raw-proof cost rise	editor continuity accepted but public/lawful proof stays costlier
Sponsor sync	budget, slot, or stop-loss pressure drops	contract capture, fan distrust, and musician hostility rise	sponsor package opens while public/artist route gets costlier
Public/pirate release	public copy legitimacy or counterbroadcast proof improves	pirate heat, crowd sync pressure, and retaliation risk rise	public receipt or counterbroadcast opens with lawful/sponsor cost
Mute/quarantine	panic or false-owner risk may drop	current route delay, hostile witness, or recovery cost rises	blocked, quarantined, or recovery-only
Chain-break default	no clean relief	false ownership, panic loop, hostile carrier, capture, or recovery-only state hardens	future route blocked, hostile, costlier, captured, or recovery-only

No branch may make the beat clean for public, lawful, sponsor, archive, editor, pirate, route-asset, and audience-stability readers at once.

Missability And Recovery

This storyline is missed when implementation:

• treats black-screen audio as flavor or a free proof token;
• hides source surface, custodian, liveness claim, legality class, or future reader;
• records 祁烬 only as a portrait or follower without backbeat packet state;
• lets sponsor sync count as public truth;
• lets editor continuity count as raw proof;
• lets public release count as lawful archive seal;
• fires from fixed time, raw count, dashboard state, or lens health;
• suppresses or sells the beat without durable Backbeat Chain Break state.

Recovery requires scarred readback: reopen the packet, pay or protect the carrier, publish a receipt, attach lawful seal, quarantine the trace, expose the false owner, split public/pirate/lawful copies, or route the blacked-out room through recovery-only proof.