Storyteller Wiki

Rebuttal Notice Afteruse Review

3 min read

Rebuttal Notice Afteruse Review

Rebuttal Notice Afteruse Review is the assignable rite for deciding how far a completed notice row may travel after its first procedural use.

It resolves one Rebuttal Notice Afteruse Docket row. A visible notice, response, annex, public line, sponsor silence clause, archive objection, or no-notice scar is insufficient unless the rite also records source boundary, response state, requested afteruse, harmed reader, proof bridge or absence, posture, cost, and future reader effect.

Required Assignment

assignment_required:
  rite_id: storyteller.rite.rebuttal_notice_afteruse_review.v1
  docket: storyteller.card.rebuttal_notice_afteruse_docket.v1
  source_notice_row: <notice row or explicit_absence>
  cited_authority_row: <authority row or explicit_absence>
  source_notice_boundary: private_notice | lawful_annex | public_counterline | editor_mask | sponsor_silence | archive_objection | split_notice | no_notice | false_notice | equivalent
  rebuttal_response_state_before_afteruse: response_open | response_answered | response_scoped | waived_with_receipt | blocked_response | false_noticed | split_record | recovery_only
  requested_afteruse: <use>
  afteruse_reader_or_route: <reader or route>
  harmed_or_excluded_reader: <reader or explicit_absence>
  proof_bridge_or_explicit_absence: <proof or explicit_absence>
  selected_afteruse_posture: certify_notice_scope | attach_rebuttal_afteruse_receipt | split_notice_from_consent | reopen_response_window | publish_response_change_notice | quarantine_notice_afteruse | false_rebuttal_notice_afteruse_default
  accepted_cost_or_explicit_absence: <cost or explicit_absence>

The rite is underfilled if it names only the prior notice row or says the affected party was “notified.”

Branches

certify_notice_scope

The player certifies the notice row only for a named afteruse and reader.

notice_afteruse_state_after: scope_certified
relief_any: [future_reader_acceptance_up, notice_integrity_up, route_legibility_up]
cost_any: [scope_narrowness_up, handler_burden_up, excluded_reader_notice_due]
future_effect_any:
  [scoped_notice_receipt_required, accepted_with_notice_scope, changed_facts_require_new_review]

attach_rebuttal_afteruse_receipt

The player attaches a response receipt, lawful annex, public counterline, checksum, archive objection, or sponsor unwind note before afteruse.

notice_afteruse_state_after: receipt_attached
relief_any: [response_continuity_up, lawful_or_public_acceptance_up, route_trace_preserved]
cost_any: [proof_burden_up, public_exposure_up, edit_or_archive_debt_up]
future_effect_any: [receipt_or_bridge_required, accepted_with_bridge_cost, checksum_due]

The player prevents the notice row from becoming waiver, consent, or universal acceptance.

notice_afteruse_state_after: notice_consent_split
relief_any: [false_waiver_down, harmed_reader_protected, consent_legibility_up]
cost_any: [route_delay_up, sponsor_or_archive_pressure_up, affected_party_hostility_up]
future_effect_any: [consent_split_due, reader_specific_use_only, alternate_route_required]

reopen_response_window

The player gives the affected party a current chance to answer the afteruse claim.

notice_afteruse_state_after: response_window_reopened
relief_any: [surprise_afteruse_down, rebuttal_legibility_up]
cost_any: [schedule_delay_up, handler_burden_up, exposure_or_retaliation_risk_up]
future_effect_any: [response_window_due, current_response_required, route_costlier]

publish_response_change_notice

The player publishes a new public counterline, lawful annex, checksum, or archive note showing that the old response state changed.

notice_afteruse_state_after: response_change_noticed
relief_any: [changed_response_visible, public_or_lawful_overread_down]
cost_any: [public_distrust_up, sponsor_pressure_up, archive_debt_up]
future_effect_any: [change_notice_due, public_counterline_due, lawful_annex_due]

quarantine_notice_afteruse

The player blocks the afteruse claim until a new receipt, annex, response, or route recovery surface exists.

notice_afteruse_state_after: afteruse_quarantined
relief_any: [false_clean_notice_down, notice_integrity_up]
cost_any: [current_route_blocked, schedule_scar_up, claimant_pressure_up]
future_effect_any: [blocked, recovery_only, new_response_required]

false_rebuttal_notice_afteruse_default

The review is skipped, underfilled, or lets a future reader consume an overbroad notice state as universal consent.

emitted_or_armed_event: storyteller.event.false_rebuttal_notice_afteruse_default.v1
notice_afteruse_state_after: false_clean_consent | captured_by_reader | recovery_only
relief_any: [immediate_pressure_down]
cost_any: [false_waiver_up, harmed_reader_hostility_up, proof_or_public_debt_up]
future_effect_any:
  [
    blocked,
    hostile,
    costlier,
    scoped_notice_receipt_required,
    response_window_due,
    sponsor_unwind_due,
    recovery_only,
  ]

Completion Contract

Every branch must write relief, cost, notice after-state, and future reader effect. The rite fails if the old notice becomes universal consent because it existed, because one reader accepted it, or because one party stayed silent under a narrower boundary.

Non-Goals

  • Not a first reader-rebuttal hearing.
  • Not a generic notice rite.
  • Not valid unless the later reader and harmed reader are both visible or explicitly absent.

Graph View

Backlinks