Rebuttal Notice Default / 反驳通知默认
Rebuttal Notice Default fires or arms when a future reader consumes a cited row as authority while the affected party’s notice, rebuttal proof, or explicit absence is missing, false, or scoped to the wrong reader.
The event makes no-notice durable. It is not a mood beat, reputation loss, or generic legal penalty. It changes future route access, reader trust, custody clarity, and the affected party’s state.
Default triggers
default_trigger:
trigger_kind: state_pressure
ledger_row_present_or_required: true
future_reader_intends_to_cite_prior_row: true
default_kind_any:
- ledger_absent
- affected_party_hidden
- explicit_absence_missing
- notice_carrier_missing
- rebuttal_proof_missing
- false_notice_filed
- private_notice_filed_as_consent
- lawful_annex_filed_as_public_truth
- public_counterline_filed_as_lawful_admissibility
- editor_mask_filed_as_raw_text
- sponsor_silence_filed_as_clean_closure
- archive_objection_filed_as_repair
- split_notice_filed_as_universal_acceptance
- no_future_reader_effect
no_fixed_turn_trigger: true
no_fixed_day_or_week_trigger: true
no_raw_count_trigger: trueEvent payload
rebuttal_notice_default:
event: storyteller.event.rebuttal_notice_default.v1
source_row_id: <stable cited row id or explicit_absence>
source_surface: transcript | rehearsal_trace | delegate_mandate | recovery_discharge | default_recovery | asset_provenance | contrition | witness | archive_custody | equivalent
citing_reader: archive | inspector | sponsor | editor | fan_public | pirate_relay | route_asset | broadcast_reality | lawful_body | management | equivalent
intended_use: proof | public_receipt | lawful_fact | sponsor_release | final_cut | route_unlock | consent_record | discharge_record | contradiction_close | equivalent
affected_party_or_absence: <party or explicit_absence>
failed_notice_boundary: private_notice | lawful_annex | public_counterline | editor_mask | sponsor_silence | archive_objection | split_notice | no_notice | false_notice | equivalent
default_narrator: archive_first | sponsor_first | inspector_first | editor_first | public_first | pirate_first | management_first | blackout_system_first | equivalent
harmed_party_state_after: hostile | blocked | captured | proxy_only | contradiction_pending | recovery_only | explicit_absence | equivalent
cited_row_state_after: false_authority | disputed_authority | sponsor_captured | lawful_only | public_only | split_record | contradiction_pending | unusable_until_notice | equivalent
future_reader_effect: blocked | costlier | hostile | captured | contradiction_pending | public_receipt_required | lawful_annex_required | sponsor_unwind_required | checksum_required | recovery_only | equivalent
counter_deltas_min: 3Durable outcomes
A firing event must leave at least one of:
- cited row becomes disputed authority;
- affected party becomes hostile, blocked, proxy-only, captured, or recovery-only;
- future reader demands a lawful annex, public counterline, checksum, sponsor unwind, or archive objection;
- route asset becomes costlier or blocked;
- broadcast reality receives contradiction-pending state;
- archive custody marks false authority or split record.
Recovery rules
Recovery may reopen the row only with visible scar:
- late lawful annex;
- late public counterline;
- checksum correction;
- sponsor unwind;
- archive objection;
- affected party receipt;
- substitute-only or recovery-only route.
No recovery may erase the prior relief/cost pair from the cited row. The future reader must still know that no-notice or false-notice happened.
Prohibitions
- No clean undo.
- No silent dead end.
- No universal reader acceptance after late notice.
- No trigger by fixed turn, day, week, raw count, dashboard, or lens-health state.