Rebuttal Notice Afteruse Docket

Rebuttal Notice Afteruse Docket records a later attempt to spend a prior notice, response, silence, objection, split notice, no-notice scar, or false-notice scar as proof, waiver, consent, public truth, lawful authority, sponsor release, route support, management cleanliness, or ending eligibility.

The docket is not another Reader Rebuttal Notice Ledger. It assumes a source notice row already exists or is explicitly absent. It records what later reader wants to do with that row and who would be harmed if the source boundary is overread.

Required Row

rebuttal_notice_afteruse_docket:
  card_id: storyteller.card.rebuttal_notice_afteruse_docket.v1
  trigger_kind: state_pressure
  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: 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 | false_rebuttal_notice_afteruse_default
  notice_afteruse_state_after: scope_certified | receipt_attached | notice_consent_split | response_window_reopened | response_change_noticed | afteruse_quarantined | false_clean_consent | captured_by_reader | recovery_only
  future_reader_or_route_effect: scoped_notice_receipt_required | consent_split_due | response_window_due | change_notice_due | sponsor_unwind_due | lawful_annex_due | public_counterline_due | blocked | hostile | costlier | recovery_only
  counter_deltas: required

Required Separations

The row is invalid if it collapses any of these:

• source notice row;
• cited authority row;
• source notice boundary;
• rebuttal or response state before afteruse;
• requested afteruse;
• afteruse reader or route;
• harmed or excluded reader;
• proof bridge or explicit absence;
• selected posture;
• after-state;
• future reader or route effect.

Valid Row Examples

• A private notice row is later cited as consent by a sponsor package; the docket requires consent split or sponsor unwind before sponsor use.
• A lawful annex notice is later cited by public recap; the docket requires public counterline, checksum, or reader restriction before public use.
• An archive objection is later treated as repair by management; the docket requires response-window reopen or quarantine.
• A no-notice scar is later cited as waiver; the docket names the affected party and blocks clean afteruse until recovery.

Non-Goals

• Not a generic action log.
• Not a replacement for Reader Rebuttal Notice Ledger.
• Not valid unless a later reader or route is visible.