Storyteller Wiki

Reader Rebuttal Notice Hearing / 读者反驳通知听证

3 min read

Reader Rebuttal Notice Hearing / 读者反驳通知听证

Reader Rebuttal Notice Hearing is the assignable rite that resolves 读者反驳通知账本 rows before a future reader consumes a cited record as authority.

The rite does not retry the old scene. It decides whether the affected party receives a usable response window and what cost the future reader pays for consuming the cited row.

Opens when

entry_state:
  trigger_kind: state_pressure
  ledger_row_present: true
  future_reader_intends_to_cite_prior_row: true
  affected_party_or_explicit_absence_present: true
  notice_boundary_unresolved: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true

Required assignment slots

A valid assignment must fill or explicitly mark absence for every slot below:

rite_assignment:
  rite: storyteller.rite.reader_rebuttal_notice_hearing.v1
  ledger: storyteller.card.reader_rebuttal_notice_ledger.v1
  source_row_id: <stable cited row id>
  citing_reader: <reader id>
  intended_use: <use id>
  affected_party_or_absence: <party or explicit_absence>
  affected_party_state: <state>
  notice_carrier_or_absence: <carrier or explicit_absence>
  rebuttal_proof_or_absence: <proof or explicit_absence>
  selected_notice_boundary: private_notice | lawful_annex | public_counterline | editor_mask | sponsor_silence | archive_objection | split_notice | no_notice
  protected_boundary_or_absence: <boundary or explicit_absence>
  waived_or_blocked_reason_or_absence: <reason or explicit_absence>
  future_reader: <future reader id>
  accepted_cost_or_absence: <cost or explicit_absence>

The rite fails if it can be completed by generic apology, generic payment, generic legal approval, or a named handler without a rebuttal proof and future reader effect.

Branches

Private notice

The affected party receives notice through a carrier before the cited row is consumed. This reduces surprise citation and hostility, but spends handler time, delays the route, and may narrow the future reader to accepts_with_rebuttal.

Lawful annex

A lawful annex is attached to the cited row. This lowers archive fraud or legal-body risk, but raises inspection heat, bureau debt, or public distrust. The future reader becomes lawful_only, audit_required, or accepts_with_cost.

Public counterline

The rebuttal becomes a public line. This blocks private capture and can improve public legitimacy, but raises sponsor pressure, witness exposure, or public contradiction. The future reader becomes public_only, public_bridge_required, or contradiction_pending.

Editor mask

An editor-protected rebuttal is attached as checksum, mask, or sealed countercut. This lowers witness exposure or source danger, but increases edit debt and source ambiguity. The future reader requires checksum or editor presence.

The sponsor or manager buys silence or narrows the notice. Immediate slot pressure can improve, but contract capture, false-notice risk, and later default risk rise. The future reader becomes sponsor_only or default_armed.

Archive objection

Archive custody records an objection without fully publicizing it. Custody clarity improves, but claimant resentment, archive debt, or contradiction pressure rises. The future reader becomes split_record or contradiction_pending.

Split notice

Different readers receive different rebuttal boundaries. This can keep both lawful and public routes alive, but burdens handlers and makes later contradiction checks unavoidable.

No notice / false notice

If no credible notice exists, or notice is falsely filed, 反驳通知默认 must fire or be armed after that event exists in the content pack. Until then, this rite must record the armed default state on the ledger row.

Result contract

Every result writes:

result:
  notice_state_after: noticed | annexed | public_counterline | editor_masked | sponsor_silenced | archive_objected | split_notice | no_notice | false_noticed
  affected_party_state_after: protected | reachable | hostile | blocked | proxy_only | captured | explicit_absence | equivalent
  future_reader_effect: accepts_with_rebuttal | accepts_with_cost | lawful_only | public_only | sponsor_only | split_record | contradiction_pending | blocked | default_armed | recovery_only | equivalent
  counter_deltas:
    relief: []
    cost: []
    future: []

Hard prohibitions

  • Private notice is not consent.
  • Lawful annex is not public truth.
  • Public counterline is not legal admissibility.
  • Editor mask is not raw text.
  • Sponsor silence is not clean closure.
  • Archive objection is not repair.
  • Split notice is not universal acceptance.
  • No-notice cannot consume a cited row as clean authority.

Graph View

Backlinks