Reader Rebuttal Notice / 读者反驳通知机制

Reader Rebuttal Notice is a cross-surface mechanism for route assets that are about to become authority. It ensures a future reader cannot consume a transcript, rehearsal trace, delegate mandate, discharge row, recovery row, or archive asset as clean proof when the affected party has not had a visible notice or rebuttal boundary.

Design problem

Existing green content already answers many first-order questions:

• Hearing Transcript Redaction asks what a hearing transcript preserves, masks, or falsifies.
• Preair Rehearsal Contamination asks how draft traces contaminate reality before final air.
• Default Recovery Triage asks how defaulted states can be recovered only with scars.
• Recovery Ward Discharge Pressure asks when care is being converted into availability.

The hidden shallow point is later-reader authority. A future route can still treat the preserved row as if no living counterparty exists. This mechanism inserts a playable response window at consumption time.

Core rule

When a future reader uses a cited row as authority, the game must classify the affected party and one of these notice boundaries:

notice_boundaries:
  - private_notice
  - lawful_annex
  - public_counterline
  - editor_mask
  - sponsor_silence
  - archive_objection
  - split_notice
  - no_notice

A boundary is valid only if it changes the future reader’s acceptance, cost, route access, or contradiction state.

State-triggered entry

entry_state:
  trigger_kind: state_pressure
  cited_authority_row_present: true
  future_reader_present: true
  intended_use_present: true
  affected_party_or_explicit_absence_present: true
  notice_boundary_unresolved: true
  route_or_proof_would_change_if_rebuttal_exists: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true

Never trigger from raw content count, dashboard health, fixed turn number, fixed day/week interval, or generic unrest.

Surface objects

• 读者反驳通知账本 records the cited row, future reader, affected party, carrier, proof, boundary, and future reader effect.
• 读者反驳通知听证 lets the player assign a boundary and cost.
• 反驳通知默认 fires or arms when no credible notice exists, notice is false, or reader scope is breached.

Reader acceptance table

Boundary	Can satisfy	Cannot satisfy cleanly	Required scar
Private notice	personal response, reduced hostility	consent, public truth, lawful proof	handler burden or delay
Lawful annex	archive or inspector reader	public legitimacy	audit, heat, or public addendum
Public counterline	fan public or public receipt	lawful admissibility	lawful bridge or contradiction state
Editor mask	source-safe proof	raw public transcript	checksum dependency
Sponsor silence	sponsor release	clean closure	capture discoverability
Archive objection	custody clarity	repair	split record or future hearing
Split notice	multi-reader survival	universal acceptance	contradiction pending
No notice	nothing clean	all authority use	default or recovery-only state

Interaction with nearby systems

Transcript rows

A redacted transcript cannot be cited as whole-public truth unless the affected speaker has notice, annex, public counterline, or explicit absence. Otherwise Rebuttal Notice Default marks the transcript as disputed or false authority.

Rehearsal traces

A rehearsal trace cannot be cited as promise, lawful fact, or route unlock unless the trace holder and affected party receive a boundary. Otherwise the trace becomes contradiction-pending or false rehearsal authority.

Fan delegate mandates

A delegate cannot speak as consensus if an excluded constituency has no notice row. The result becomes public-only, sponsor-captured, split, or false representative.

Recovery discharge

A recovering body or voice cannot become proof of availability if the subject’s response boundary is hidden. The future reader must accept proxy-only, lawful-only, public-only, sponsor-only, recovery-only, or costlier access.

Default recovery

A recovered row cannot be filed as original without notifying harmed party or naming explicit absence. Substitute-only and recovery-only states remain visible.

Branch contract

Every non-default resolution must include:

branch_contract:
  relief_min: 1
  cost_min: 1
  future_reader_effect_min: 1
  affected_party_state_after_visible: true
  cited_row_state_after_visible: true

Failure/default contract

Default is armed when:

• ledger is absent;
• affected party is hidden;
• explicit absence is not recorded;
• notice carrier or proof is missing;
• private notice is filed as consent;
• lawful annex is filed as public truth;
• public counterline is filed as lawful admissibility;
• editor mask is filed as raw text;
• sponsor silence is filed as clean closure;
• archive objection is filed as repair;
• split notice is filed as universal acceptance;
• no future reader state changes.

The default must alter future play, not just prose.

Counters and durable states

Primary counters/states:

• surprise_citation
• rebuttal_legibility
• affected_party_hostility
• archive_fraud_risk
• public_receipt_legitimacy
• public_receipt_distrust
• sponsor_stop_loss_pressure
• contract_capture
• inspection_heat
• bureau_favor_debt
• edit_debt
• source_ambiguity
• witness_exposure
• body_boundary_integrity
• future_route_cost
• contradiction_pending
• reader_scope_breach

Non-goals

• Not governance methodology.
• Not a notification UI.
• Not a generic apology branch.
• Not a consent-cleaning spell.
• Not a fixed cleanup phase.
• Not valid unless reader acceptance changes.