Reader Collision Default / 读者冲突默认
Reader Collision Default is the event that fires, arms, or is recorded when a 裁定读者冲突案卷 is hidden, underfilled, falsely served, or allowed to be captured by the loudest reader.
It makes unresolved multi-reader pressure durable. The event does not say “nothing happened.” It names who used the source first and who now pays the scar.
Fire condition
fire_condition:
trigger_kind: state_pressure
docket_present_or_expected: storyteller.card.ruling_reader_collision_docket.v1
source_ruling_or_row_present: true
readers_min: 2
incompatible_acceptance_rules: true
one_of:
- hearing_not_offered
- docket_hidden
- row_underfilled
- selected_reader_missing
- excluded_reader_unnamed
- false_universal_acceptance_recorded
- future_reader_cites_unresolved_source
no_fixed_turn_trigger: true
no_fixed_day_or_week_trigger: trueDefault narrators
The event must name the reader or faction that captured the unresolved source.
Accepted narrators:
lawful_reader_captures— inspector or archive treats the row as lawful-only and freezes public use.public_reader_captures— fan public or historian treats the row as public-only and makes legal cleanup harder.sponsor_reader_captures— sponsor desk treats the row as clean report and captures public correction.artist_boundary_reader_captures— refusal or body/voice boundary blocks route use.editor_reader_captures— cutroom patch makes the source legible but less trusted.management_reader_captures— compression desk turns the row into false clean metrics.route_asset_reader_captures— asset holder, courier, permit, or proof object becomes seized, false-owned, or recovery-only.claimant_reader_captures— claimant floor, adverse coalition, or duplicate receipt holder hardens hostility.
The event fails if the default is narratorless.
Event payload
event: storyteller.event.reader_collision_default.v1
source:
source_ruling_or_row: <id>
source_history_preserved: true
collision:
docket: storyteller.card.ruling_reader_collision_docket.v1 | expected_but_missing
readers:
- <reader id>
- <reader id>
incompatibility: <kind>
default:
narrator: <default narrator>
capturing_reader: <reader id>
excluded_reader: <reader id>
default_kind: false_universal_key | double_reader_hardens | route_asset_seized | claimant_floor_hostile | public_only_capture | lawful_only_capture | sponsor_capture | equivalent
reader_states_after:
- reader_id: <capturing reader>
state: false_universal_key | captured | public_only | lawful_only | sponsor_only | route_asset_only
- reader_id: <excluded reader>
state: hostile | blocked | audit_required | contradiction_pending | recovery_only
counter_deltas:
relief: []
cost: []
future: []Outcome families
False universal key
A reader treats the source as if all readers accepted it.
Required consequences:
reader_collision +1or equivalent;- at least one reader becomes hostile, blocked, or recovery-only;
- future citation of the source requires audit, public correction, quarantine, or collateral.
Double reader hardens
Two public or institutional versions remain active and consume future routes differently.
Required consequences:
reality_drift +1,continuity_hazard +1, orblack_screen_slots +1;- future correction cost rises;
- one branch becomes contested rather than erased.
Route asset seized or false-owned
A custody carrier, proof object, permit, witness, or route unlock is taken by the reader who moved first.
Required consequences:
route_asset_pressure +1,custody_gap +1,archive_debt +1, orfalse_custody_owner +1;- future use requires rescue, exchange, public receipt, lawful proof, or recovery-only branch;
- high-rank authority cannot erase the seizure for free.
Claimant floor hostile
A claimant reader sees the source being used without its required notice, proof, or recognition surface.
Required consequences:
claimant_hostility +1,fan_oxygen_resentment +1, orpublic_receipt_distrust +1;- future claimant intake, settlement, public contrition, or oxygen exchange becomes harder;
- a later apology or payment cannot cleanly remove the hostility.
Sponsor capture
Sponsor or management reader converts the source into a clean report before public, artist, or lawful readers accept it.
Required consequences:
- immediate sponsor or management pressure may fall;
contract_capture +1,public_receipt_distrust +1, delayedinspection_heat +1, or artist-boundary risk rises;- public correction becomes costlier or recovery-only.
Recovery hooks
Recovery is allowed only with a scar. Valid recovery hooks:
- reopen 读者冲突听证 and name both readers;
- quarantine the source and block the route until proof is carried;
- publish the excluded reader’s receipt and accept sponsor or inspection heat;
- appoint a lawful monitor and accept bureau debt;
- rescue or replace a seized route asset;
- protect an artist boundary and lose a clean route;
- accept public-only, lawful-only, sponsor-only, route-asset-only, or recovery-only future use.
Integration notes
- If the hidden row came from Ruling Enforcement Load Docket, this event may chain from 执行负荷违约.
- If the hidden row came from 实在漂移案卷, this event may chain from 实在漂移介入.
- With 裁定读者冲突, this event is the durable default state for unresolved multi-reader demand.
Failure examples
The event is invalid if:
- it fires without two readers;
- it says the source is simply lost without naming the capturing reader;
- it erases the source ruling;
- it lets recovery reset all reader states to clean acceptance;
- it changes only prose mood;
- it triggers from fixed turn, fixed day, fixed week, chapter quota, content count, or dashboard health.
Non-goals
- Not random backlash.
- Not a soft fail.
- Not a replacement for enforcement-load default or drift intervention.
- Not valid unless a future reader captures, blocks, hardens, or scars the source.