Rebuttal Notice Afteruse Receipt Lens
This lens checks that a completed reader-rebuttal notice row cannot later be spent as clean universal consent unless the afteruse scope, reader, harmed reader, proof bridge, scar, and future effect remain visible.
Entry Oracle
entry_state:
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: trueThe lens fails if entry is driven by fixed turn, fixed day/week, raw notice count, dashboard state, or lens-health state.
Checks
1. Docket Preserves Notice Row, Reader, And Afteruse
rebuttal_notice_afteruse_docket:
source_notice_row: required
cited_authority_row: required
source_notice_boundary: required
rebuttal_response_state_before_afteruse: required
requested_afteruse: required
afteruse_reader_or_route: required
harmed_or_excluded_reader: required
proof_bridge_or_explicit_absence: required
selected_afteruse_posture: required
notice_afteruse_state_after: required
future_reader_or_route_effect: required
counter_deltas: required2. Review Branches Diverge
Required branch families:
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;future_effect_any.
3. Default Mutates Future Play
false_rebuttal_notice_afteruse_default:
false_clean_notice_claim: true
source_notice_row_or_absence: required
hidden_or_overbroad_notice_scope: required
capturing_reader_or_route: required
harmed_or_excluded_reader: required
notice_afteruse_state_after: required
future_reader_effect: required
counter_deltas_min: 3
durable_mutation: true4. Runtime Rollup Status Is Explicit
This is a direct-wiki contract bound to an evaluator entry. Runtime source objects and durable replay can be added later if rebuttal notice afteruse becomes executable in the game-content rollup.