Reader Rebuttal Notice Ledger / 读者反驳通知账本

Reader Rebuttal Notice Ledger is a route-asset card for the moment a future reader is about to treat an earlier row as authority and the row names, harms, quotes, represents, discharges, redacts, or substitutes someone who can still answer.

It closes a shallow-green gap between existing custody surfaces. Hearing Transcript Redaction records what survives in a transcript. Preair Rehearsal Contamination records what draft trace can leak into reality. Default Recovery Triage records scarred recovery. Recovery Ward Discharge Pressure records body availability. This card asks one more playable question: before a later reader consumes that record, who gets notice and what kind of rebuttal can follow it?

Entry contract

Open this card from state pressure, not from a fixed schedule:

entry_state:
  trigger_kind: state_pressure
  future_reader_intends_to_cite_prior_row: true
  cited_row_present: true
  affected_party_or_explicit_absence_present: true
  route_or_proof_would_change_if_rebuttal_exists: true
  player_can_record_notice_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true

Valid cited-row families include transcript rows, rehearsal traces, fan delegate mandates, recovery-discharge rows, default-recovery rows, asset provenance rows, public contrition receipts, protected-witness rows, archive custody rows, and equivalent route assets.

Required fields

A valid ledger row records:

reader_rebuttal_notice_row:
  source_row_id: <stable cited row id>
  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: <speaker subject witness claimant delegate artist handler fan public or explicit_absence>
  affected_party_state: reachable | protected | recovering | hostile | missing | captured | proxy_only | explicit_absence | equivalent
  notice_carrier_or_absence: ruan_chi | yu_lan | han_yanshuang | baiya | shen_luo | fan_delegate | archive_clerk | pirate_relay | handler | explicit_absence | equivalent
  rebuttal_proof_or_absence: counter_oath | raw_minutes | checksum_note | medical_boundary | public_counterline | lawful_annex | sponsor_exception | pirate_packet | explicit_absence | equivalent
  notice_boundary: private_notice | lawful_annex | public_counterline | editor_mask | sponsor_silence | archive_objection | split_notice | no_notice
  response_window_state: open | narrowed | waived_with_receipt | blocked | false_noticed | expired_by_reader_action | equivalent
  future_reader_effect: accepts_with_rebuttal | accepts_with_cost | lawful_only | public_only | sponsor_only | split_record | contradiction_pending | blocked | default_armed | equivalent

What this card is not

• Not an apology mechanic.
• Not a generic notification inbox.
• Not a clean consent reset.
• Not a turn-count reminder.
• Not valid if the future reader would behave exactly the same with or without notice.

Example rows

Transcript rebuttal row

A transcript row has been lawfully redacted, but the archive wants to cite it as full public truth. The ledger names the speaker, the missing phrase, 阮尺 as notice carrier, and a lawful annex or public counterline as response.

Rehearsal trace rebuttal row

A sponsor preview is being cited as a promise. The ledger names the affected artist or production handler, records the preview holder, and lets the player file a corrected-air boundary, public counterline, or sponsor silence with capture cost.

Recovery-discharge rebuttal row

A recovering body is being used as proof of availability. The ledger records the subject, consent receipt or explicit absence, medical boundary, requested use, and whether the future route becomes proxy-only, lawful-only, or recovery-only.

Branch hints

Notice boundary	Relief	Cost	Future reader effect
Private notice	avoids surprise citation	handler burden and delay rise	accepts with rebuttal cost
Lawful annex	legal-body fraud falls	bureau debt or inspection heat rises	lawful-only or audit required
Public counterline	private capture falls	sponsor pressure and public contradiction rise	public-only until bridge
Editor mask	witness exposure falls	edit debt and source ambiguity rise	checksum required
Sponsor silence	slot or sponsor pressure improves	contract capture and false-notice risk rise	sponsor-only or default armed
Archive objection	custody clarity improves	archive debt and claimant resentment rise	split record or contradiction pending
No notice / false notice	immediate pressure may fall	rebuttal default hardens	blocked, hostile, captured, or recovery-only

Counter surfaces

Every resolved row must mutate at least one relief surface, one cost surface, and one future-reader surface.

Potential relief surfaces: surprise_citation_down, archive_fraud_risk_down, private_capture_down, body_boundary_integrity_up, public_receipt_legitimacy_up, contradiction_legibility_up.

Potential cost surfaces: handler_burden_up, schedule_pressure_up, inspection_heat_up, bureau_favor_debt_up, sponsor_stop_loss_pressure_up, contract_capture_up, edit_debt_up, source_ambiguity_up, public_receipt_distrust_up, witness_exposure_up, future_route_cost_up.

Potential future-reader states: accepts_with_rebuttal, lawful_only, public_only, sponsor_only, split_record, contradiction_pending, default_armed, blocked, recovery_only.