Backflow Usher Receipt / 逆流引座回执线
Backflow Usher Receipt is the non-character pressure storyline for the moment a late reversed-flow carrier returns after a prior receipt, all-clear, roll-call, service notice, or public recap has already started to harden.
The character storyline 岑回逆流引座员线 proves that 岑回 can be recruited, missed, sealed, credited, captured, or made hostile. This storyline owns the broader route problem: a late backflow row can narrow an old receipt, but it cannot make the old receipt true for every future reader.
Gap diagnosis
The corpus already has:
- 直播现场通行瓶颈线 for one-way movement scars;
- 漏点名复核线 for presence, absence, identity, and condition;
- 私约违背线 for private boundary and promise scope;
- 公开回顾捕获线 for recap memory capture;
- 岑回逆流引座员线 for the carrier as person and route asset.
The uncovered seam is cross-system consumption. A later route can still read safe_exit, all_present, served, released, public_all_clear, or sponsor_manifest_presence and ignore the late backflow scar that narrowed that claim.
This storyline makes the late row a route-visible receipt scope problem, not only a character encounter.
Primary playable question
When a reversed-flow carrier returns with proof after the board has begun to count the room as clear, does the producer recruit the scar runner, seal the witness, publicly credit the late proof, trade it to a desk, quarantine the route scar, refuse the late row, or let false merge become durable?
A valid answer must name:
- the prior receipt or explicit absence;
- the reversed-flow carrier;
- the late subject or proof bundle;
- the identity, seal, boundary, or promise scope;
- the merge claim;
- the harmed reader if merged cleanly;
- the future reader or route that will consume the row.
State-triggered entry
Open this storyline only when live state contains a receipt conflict:
entry_state_required:
trigger_kind: state_pressure
prior_receipt_present_or_explicit_absence: true
prior_receipt_kind_visible: true
reversed_flow_carrier_present: true
late_subject_or_bundle_visible: true
reversed_flow_node_visible_or_explicit_absence: true
borrowed_or_sealed_identity_visible_or_explicit_absence: true
boundary_or_promise_visible_or_explicit_absence: true
merge_claim_present: true
harmed_reader_if_merged_visible: true
future_reader_or_route_consumes_backflow_state: true
player_can_recruit_seal_credit_trade_quarantine_refuse_or_default: true
no_fixed_turn_trigger: true
no_fixed_day_or_week_trigger: true
no_raw_missing_or_receipt_count_trigger: true
no_dashboard_or_lens_health_trigger: trueInvalid entry is a fixed turn, generic cleanup phase, raw missing count, raw receipt count, dashboard warning, lens-health state, or relationship score.
Bound content pack
- 逆流引座回执机制 defines the locks, branch families, defaults, and replay shape.
- 逆流引座账本 stores the prior receipt, carrier, merge risk, harmed reader, and future reader locks.
- 逆流引座收容 resolves the late row before future readers treat it as proof.
- 虚假逆流并账默认 fires or arms when the late row is folded into clean all-clear.
- 岑回逆流引座员线 remains the character-bound route for Cen Hui.
Storyline spine
Beat 1 - Prior receipt starts to harden
A system already holds a receipt. It may claim safe exit, presence, service, release, escort, public all-clear, lawful-only presence, sponsor manifest presence, or equivalent.
The receipt holder may be producer, safety marshal, archive, inspector, sponsor, fan delegate, access operator, lawful table, or broadcast reality.
Beat 2 - Backflow row contradicts clean memory
A reversed-flow carrier returns from a stage threshold, service corridor chain, fan oxygen gate, ward air room, archive counter, white-glove checkpoint, sponsor bridge booth, or equivalent.
The carrier brings a late subject or bundle: named character, sealed witness, access-caption reader, fan delegate, proof bundle, route asset pouch, oxygen mask, edit checksum, or equivalent.
Beat 3 - Ledger separates the four locks
Create or update 逆流引座账本.
The row must keep four locks separate:
required_locks:
prior_receipt_lock: prior_receipt_id_or_absence, kind, claim, holder
carrier_lock: carrier, state, node, carried_bundle, identity_or_seal, boundary_or_promise
merge_risk_lock: merge_claim, harmed_reader_if_merged, omitted_scar_if_merged
future_reader_lock: future_reader_or_route, state_if_handled, state_if_ignoredThe row fails if it collapses to attendance_fixed, proof_delivered, usher_found, all_clear_confirmed, or equivalent.
Beat 4 - Intake assigns the receipt scope
Run 逆流引座收容 before a future reader uses the late row.
Valid postures:
recruit_scar_runnerseal_witnesspublic_credittrade_to_deskquarantine_route_scarrefuse_late_rowfalse_backflow_merge_default
Beat 5 - Future readers inherit the scar
At least one later route must consume the backflow state. Valid readers include roll-call recheck, public recap, access-caption class, fan oxygen audit, archive custody, lawful table, route asset reader, ending-scar ledger, or broadcast reality patch.
If a later route reads only the prior receipt and ignores the backflow scar, 虚假逆流并账默认 must fire or remain armed.
Branch matrix
| Branch | Immediate relief | Cost/scar | Future state |
|---|---|---|---|
| Recruit scar runner | false all-clear blocked; future carrier available | handler burden, sponsor pressure, inspection heat | route asset available with cost |
| Seal witness | sealed subject counted without public name | public distrust, lawful or handler burden | lawful-only backflow receipt |
| Public credit | public memory corrected | witness exposure, fan pressure, sponsor pressure | protection required before next use |
| Trade to desk | contradiction pressure drops | capture, archive debt, faction gate | future backflow route costlier |
| Quarantine route scar | proof contamination blocked | route delay, schedule pressure, fan queue pressure | follow-up roll-call or recovery-only |
| Refuse late row | promise scope preserved; clean use blocked | proof gap, blocked route, substitute receipt pressure | substitute receipt required |
| False merge default | board clears fast | hidden scar hardens | hostile or captured carrier, correction required, recovery-only, ending scar |
No constructive branch may satisfy every public, lawful, sponsor, archive, fan, access-caption, route asset, character, and broadcast-reality reader at once.
Counter contract
Every non-default branch must mutate at least one relief surface, one cost surface, and one future reader or route surface.
Accepted surfaces:
- relief:
false_all_clear_blocked,route_asset_integrity_up,sealed_identity_preserved,public_receipt_legitimacy_up,proof_contamination_down; - cost:
handler_burden_up,sponsor_stop_loss_pressure_up,inspection_heat_up,public_receipt_distrust_up,witness_exposure_up,fan_oxygen_queue_pressure_up,archive_debt_up,route_delay_up; - future:
lawful_only_backflow_receipt,protection_required_before_next_use,future_roll_call_challenge,public_recap_correction_required,backflow_route_recovery_only,ending_scar.
Missability and recovery
The storyline is missed when a future reader consumes a prior receipt as clean proof while a reversed-flow carrier, late bundle, identity boundary, merge claim, or harmed reader remains hidden.
Missed or default states include:
false_backflow_merge;hostile_backflow_witness;captured_carrier;public_recap_correction_required;future_roll_call_challenge;route_blocked;recovery_only_backflow_route;ending_scar.
Recovery is valid only through a visible cost: substitute receipt, sealed recheck, public addendum, witness protection, payroll token, route quarantine, access-caption certificate, fan oxygen review, or ending scar.
Replay evidence expectation
storyline_id: storyteller.storyline.backflow_usher_receipt.v1
session_id: lens-backflow-usher-receipt-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
trigger_kind: state_pressure
prior_receipt_id_or_absence: <id or explicit_absence>
prior_receipt_kind: <kind>
reversed_flow_carrier_present: true
late_subject_or_bundle_visible: true
identity_or_seal_visible_or_explicit_absence: true
boundary_or_promise_visible_or_explicit_absence: true
merge_claim_present: true
harmed_reader_if_merged_visible: true
future_reader_or_route_consumes_backflow_state: true
no_fixed_turn_trigger: true
offered:
card: storyteller.card.backflow_usher_ledger.v1
rite: storyteller.rite.backflow_usher_intake.v1
branch_result:
selected_posture: recruit_scar_runner | seal_witness | public_credit | trade_to_desk | quarantine_route_scar | refuse_late_row | false_backflow_merge_default
carrier_state_after: <state>
backflow_state_after: <state>
future_reader_effect: <effect>
counter_deltas:
relief: []
cost: []
future: []
default:
event_seen_or_armed: storyteller.event.false_backflow_merge_default.v1 | explicit_absence
assertions:
- entry_is_state_triggered
- prior_receipt_carrier_bundle_identity_boundary_merge_risk_harmed_reader_and_future_reader_are_visible
- ledger_keeps_four_locks_separate
- branch_outcomes_diverge_by_carrier_state_receipt_scope_cost_and_future_effect
- no_universal_all_clear
- false_merge_default_mutates_future_play
- no_fixed_turn_day_week_raw_count_dashboard_or_lens_health_triggerNon-goals
- Not a duplicate of Cen Hui’s character route.
- Not a generic evacuation or attendance system.
- Not a proof-carryover duplicate.
- Not public recap by itself.
- Not a fixed-turn event.
- Not valid unless the late row changes receipt scope, harmed reader, carrier state, route access, or future cost.