Backbeat Crowd-Sync Ledger / 鼓点共振账本线

Backbeat Crowd-Sync Ledger is the operational second hop after Qi Jin’s backbeat has already been placed in protected custody. It asks whether that protected beat may pace a live audience, fan line, egress lane, sponsor room, public relay, or edit loop, and which debt the later reader inherits.

The line does not recruit Qi Jin and does not decide custody again. Only the protected parent result may open it.

Canonical parent gate

parent_contract:
  parent_rite_id: rite.night_shift_backbeat_custody
  required_parent_choice_index: 0
  required_parent_choice_id: recruit_carrier_with_credit
  required_readiness_flag: backbeat_crowd_sync.parent.recruit_carrier_source_ready
  other_parent_choices_open_child: false
  parent_result_materializes_readiness: true
  parent_result_gains_exactly:
    - storyteller.card.backbeat_crowd_sync_ledger.v1
    - storyteller.card.backbeat_sync_target_audience_floor.v1
    - storyteller.card.backbeat_paced_group_live_audience.v1
    - storyteller.card.backbeat_consent_refusal_row.v1
    - storyteller.card.backbeat_future_reader_blackout_floor.v1

The source packet, Qi Jin card, and payment/protection card already belong to the parent custody packet. The five cards above are producer-gained outputs of choice 0; they are not starter cards, virtual lens slots, or generic substitutes.

Playable spine

Beat 1 — Custody produces readiness

Resolve rite.night_shift_backbeat_custody with choice 0, recruit_carrier_with_credit. This writes backbeat_crowd_sync.parent.recruit_carrier_source_ready, preserves the real backbeat packet, Qi Jin, and payment/protection row, and materializes the five child cards. Suppression, editor capture, sponsor capture, public release, or no-handler custody does not open this child review.

Beat 2 — Eight exact rows form one sync docket

The child review accepts these cards in this exact order:

  1. storyteller.card.backbeat_crowd_sync_ledger.v1
  2. card.qi_jin_backbeat_packet
  3. storyteller.card.backbeat_sync_target_audience_floor.v1
  4. storyteller.card.backbeat_paced_group_live_audience.v1
  5. card.qi_jin_night_shift_drummer
  6. card.qi_jin_backbeat_payment_or_protection
  7. storyteller.card.backbeat_consent_refusal_row.v1
  8. storyteller.card.backbeat_future_reader_blackout_floor.v1

The selected posture comes from the rite choice. There is no posture prop card and no selected-branch card.

Beat 3 — The player chooses one costed use

The child rite exposes eight options in stable order:

ChoiceOption IDOperational result
0protected_conductorQi Jin conducts with protection, credit, exposure, and a scoped future reader.
1fan_chant_bridgeFans carry the count, while queue-capture risk and sponsor pressure remain visible.
2egress_pacerThe beat helps movement, while roll-call and floor liability remain due.
3sponsor_metronome_patchSponsor relief opens only inside sponsor scope and creates public unwind debt.
4pirate_rhythm_leakPublic access improves while lawful annex and source retaliation remain due.
5editor_loop_maskContinuity survives, but checksum, source ambiguity, and raw-proof cost remain.
6refuse_syncUnsafe pacing is refused; the route delays or needs a substitute stabilizer.
7hidden_use_defaultHidden pacing creates a durable panic-loop scar and arms recovery.

No branch may turn rhythm into universal audience consent, clean liveness proof, lawful custody, safe egress, sponsor truth, public truth, or unrestricted broadcast authority.

Beat 4 — The default offers scarred recovery

Hidden use arms storyteller.event.backbeat_sync_panic_loop.v1. The event must be executable and offer exactly three recovery postures:

  • publish_conductor_credit_addendum;
  • serve_egress_roll_call;
  • quarantine_sync_packet.

Every outcome clears the event’s pending flags, keeps the hidden-use scar, and writes a distinct future route posture. Recovery cannot retroactively make the pacing consensual or the beat clean proof.

Runtime-evidence requirement

Runtime satisfaction requires executable evidence rather than a Wiki assertion:

  • a durable Game CLI replay resolves parent choice 0 and then child choice 0 with all eight exact in-hand cards;
  • a second durable Game CLI replay resolves child choice 7 and then the conductor-credit recovery event;
  • a focused runtime test triggers the real event object and executes all three event choices;
  • wrong parent branches, missing cards, substituted cards, catalog-only cards, duplicate assignments, omitted child choice, and repeat resolution all fail;
  • replay source and every active object remain storyteller.

Boundary with adjacent lanes

  • night-shift-backbeat-custody owns custody and Qi Jin’s recruitment. This line consumes only its protected result.
  • audience-stability-floor owns why the audience keeps watching. This line may change a scoped audience route but cannot replace that floor.
  • live-floor-egress-bottleneck owns floor routing and missing people. Egress pacing never clears roll-call by itself.
  • Fan, sponsor, pirate, and edit branches preserve their own consent, credit, lawful-reader, and checksum limits.

This storyline remains inside the active original Storyteller world.