Reader Rebuttal Notice / 读者反驳通知线

Reader Rebuttal Notice is a pressure-system storyline for the moment a later route tries to use a prior row as authority while the affected party still has a live, scarred, protected, hostile, proxy-only, or explicitly absent claim.

The pack is designed as a high-leverage follow-up to recently stabilized custody and consent arcs. The corpus now has strong surfaces for transcript survival, rehearsal trace boundaries, default recovery, recovery discharge, fan delegate mandates, and asset afterlife. This storyline asks what happens when those results are later cited.

Primary playable question: Before a future reader consumes a cited row as proof, route unlock, public receipt, lawful fact, sponsor release, final cut, discharge record, consent record, or contradiction closure, does the player give the affected party private notice, lawful annex, public counterline, editor mask, sponsor silence, archive objection, split notice, or no notice?

Why this is not covered by nearby storylines

• 阮尺删改速记员线 covers transcript survival and stenographer route state, not mandatory rebuttal when future readers cite the transcript.
• 预播排练污染线 covers draft trace boundary before final air, not response rights when a later reader cites the trace.
• 默认恢复分诊线 covers scarred recovery, not notice before recovered rows are filed as authority.
• 复原病房出院压迫线 covers conversion of care into availability, not later rebuttal when that discharge row is consumed by archive, sponsor, fan, or broadcast-reality readers.
• 粉丝委任分裂线 covers who speaks for fans, not notice to excluded constituencies when the chosen mandate is reused as consensus.
• 认领告知顺序线 covers who learns first; this storyline covers whether a cited row can be answered before it becomes authority.

Bound content pack

This storyline binds:

• 读者反驳通知机制;
• 读者反驳通知账本;
• 读者反驳通知听证;
• 反驳通知默认.

Rebuttal Notice Afteruse Receipt handles the later seam: a served notice, public counterline, lawful annex, sponsor silence clause, archive objection, split notice, no-notice scar, or false-notice scar can be cited by a future reader only when the afteruse docket names scope, harmed reader, proof bridge or absence, after-state, and future effect.

State-triggered entry

Open this storyline when all are true:

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
  row_would_change_route_proof_receipt_or_closure: true
  notice_boundary_unresolved: 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 rows include transcript rows, rehearsal traces, fan delegate mandates, recovery-discharge ledgers, default-recovery rows, asset provenance rows, public contrition receipts, protected-witness rows, archive custody rows, and equivalent route assets.

Storyline spine

Beat 1 — A prior row becomes authority

The archive, inspector, sponsor, editor, fan public, pirate relay, broadcast-reality reader, lawful body, management desk, or route asset attempts to consume a prior row.

The player receives 读者反驳通知账本. The ledger names source row, source surface, citing reader, intended use, affected party or explicit absence, affected-party state, and why route/proof/receipt/closure would change if rebuttal exists.

Beat 2 — The affected party is reachable, protected, hostile, captured, proxy-only, or absent

The row must not collapse into generic person was notified. The affected party’s state shapes the available notice boundary.

Examples:

• speaker reachable but afraid after redaction;
• artist recovering and proxy-only after discharge pressure;
• fan constituency excluded by a delegate mandate;
• witness protected by payroll;
• editor can carry checksum without exposing source;
• sponsor controls a silence clause;
• archive has only explicit absence.

Beat 3 — The player assigns rebuttal boundary

The player opens 读者反驳通知听证.

The rite requires source row, citing reader, intended use, affected party or explicit absence, carrier or explicit absence, rebuttal proof or explicit absence, selected notice boundary, protected boundary or explicit absence, waived/blocked reason or explicit absence, future reader, and accepted cost.

Beat 4 — The future reader changes acceptance

The future reader must not treat all outcomes the same.

Valid effects include:

• accepts with rebuttal cost;
• lawful-only;
• public-only;
• sponsor-only;
• split record;
• contradiction pending;
• checksum required;
• public receipt required;
• lawful annex required;
• sponsor unwind required;
• blocked;
• recovery-only.

Beat 5 — No-notice becomes default

If ledger, affected party, explicit absence, notice carrier, proof, or future reader effect is missing, 反驳通知默认 fires or is armed.

The event names default kind, default narrator, harmed state after, cited row state after, future reader effect, and counter deltas.

Branch map

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

Character hooks

• Redaction Stenographer can carry a transcript rebuttal notice, but her exposure, burden, or hostility can rise.
• Yu Lan can carry a public counterline, but public contradiction and sponsor retaliation rise.
• Han Yanshuang can attach lawful annex, but bureau debt or inspection heat rises.
• Baiya can mask the rebuttal through checksum, but edit debt and source ambiguity rise.
• Shen Luo can bargain sponsor silence, but contract capture and false-notice risk rise.
• 海盗频段童声 can relay public rebuttal when lawful readers are captured, but pirate exposure and relay custody risk rise.

Missability and recovery

This storyline is missed when implementation:

• lets future readers consume cited rows without an affected party or explicit absence;
• treats private notice as consent;
• treats lawful annex as public truth;
• treats public counterline as lawful proof;
• treats editor mask as raw text;
• treats sponsor silence as clean closure;
• treats archive objection as repair;
• treats split notice as universal acceptance;
• produces no future reader effect;
• triggers from fixed turn, fixed day/week, raw content count, dashboard state, or lens-health state.

Recovery is allowed only with scar: late annex, late counterline, checksum correction, sponsor unwind, archive objection, affected party receipt, substitute-only route, or recovery-only route.

Replay evidence shape

storyline_id: storyteller.storyline.reader_rebuttal_notice.v1
session_id: lens-reader-rebuttal-notice-v1-<timestamp>
seed: <deterministic-seed>
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
  no_fixed_turn_trigger: true
source:
  source_row_id: <stable cited row id>
  source_surface: <surface>
  citing_reader: <reader>
  intended_use: <use>
  affected_party_or_absence: <party or explicit_absence>
offered:
  card: storyteller.card.reader_rebuttal_notice_ledger.v1
  rite: storyteller.rite.reader_rebuttal_notice_hearing.v1
branch_runs:
  valid_branch:
    selected_notice_boundary: private_notice | lawful_annex | public_counterline | editor_mask | sponsor_silence | archive_objection | split_notice
    notice_carrier_or_absence: <carrier or explicit_absence>
    rebuttal_proof_or_absence: <proof or explicit_absence>
    affected_party_state_after: <state>
    cited_row_state_after: <state>
    future_reader_effect: <effect>
    counter_deltas:
      relief: []
      cost: []
      future: []
  default_branch:
    event_seen_or_armed: storyteller.event.rebuttal_notice_default.v1
    default_kind: <kind>
    default_narrator: <narrator>
    harmed_party_state_after: <state>
    future_reader_effect: <effect>
assertions:
  - entry_is_state_triggered
  - affected_party_or_explicit_absence_visible
  - notice_boundary_assignable
  - branch_families_diverge
  - future_reader_acceptance_changes
  - no_notice_default_is_durable
  - no_fixed_turn_trigger

Non-goals

• Not a governance checklist.
• Not an inbox or UI notification feature.
• Not a retry of the original hearing, rehearsal, discharge, or recovery scene.
• Not an apology-only branch.
• Not filler content for raw count growth.
• Not valid if a cited row has the same future-reader effect with and without rebuttal.