Storyteller Wiki

Rebuttal Notice Afteruse Receipt

3 min read

Rebuttal Notice Afteruse Receipt

Rebuttal Notice Afteruse Receipt makes a completed notice or no-notice row reusable only through named afteruse scope.

The mechanism exists when Reader Rebuttal Notice has already produced a boundary, but a later reader wants to spend that boundary in a different context. Private notice is not consent. Sponsor silence is not public waiver. Lawful annex is not public truth. Archive objection is not repair. Split notice is not universal acceptance.

Entry Contract

rebuttal_notice_afteruse_receipt:
  trigger_kind: state_pressure
  source_notice_row_visible: true
  cited_authority_row_visible: true
  source_notice_boundary_visible: true
  rebuttal_response_state_visible: true
  requested_afteruse_visible: true
  future_reader_consumes_notice_state: true
  harmed_or_excluded_reader_visible_or_explicit_absence: true
  player_can_certify_attach_split_reopen_notice_quarantine_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_notice_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Afteruse States

rebuttal_notice_afteruse_states:
  - unspent_notice
  - afteruse_requested
  - scope_certified
  - receipt_attached
  - notice_consent_split
  - response_window_reopened
  - response_change_noticed
  - afteruse_quarantined
  - false_clean_consent
  - captured_by_reader
  - hostile_reader
  - recovery_only

The implementation fails if a source notice state is collapsed into a generic notified or waived flag.

Branch Contract

Every non-default branch must record:

rebuttal_notice_afteruse_resolution:
  source_notice_row: <row id>
  cited_authority_row: <row id 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: route_unlock | sponsor_package | lawful_annex | public_table | archive_release | recap_claim | management_report | broadcast_reality | ending_gate | equivalent
  afteruse_reader_or_route: sponsor | lawful_reader | archive | public_table | route_asset | recap_lane | management_report | broadcast_reality | ending | equivalent
  harmed_or_excluded_reader: affected_party | public_reader | lawful_reader | sponsor | archive | route_asset_holder | witness | subject | explicit_absence
  proof_bridge_or_explicit_absence: notice_receipt | response_receipt | lawful_annex | public_counterline | checksum | archive_objection | sponsor_unwind | 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
  notice_afteruse_state_after: <state>
  relief_any: []
  cost_any: []
  future_effect_any: []

Failure Cases

The mechanism must fail if:

  • private notice is reused as consent;
  • lawful annex is reused as public truth;
  • public counterline is reused as lawful admissibility;
  • editor mask is reused as raw text;
  • sponsor silence is reused as clean closure;
  • archive objection is reused as repair;
  • split notice is reused as universal acceptance;
  • a no-notice or false-notice scar is used as waiver;
  • harmed or excluded reader state is hidden;
  • default changes only text, mood, reputation, or a generic pressure counter.

Default Contract

The default is False Rebuttal Notice Afteruse Default. It must record false-clean notice claim, source notice row or explicit absence, hidden or overbroad notice scope, capturing reader or route, harmed reader, after-state, future reader effect, at least three counter deltas, and durable mutation.

Graph View

Backlinks