Claimant Stamp Afteruse Receipt
Claimant Stamp Afteruse Receipt makes a moved claimant stamp reusable only through named afteruse scope.
The mechanism exists when a prior stamp row is still true but a later reader wants to spend it in another context. A proxy stamp does not prove universal notice. A public reassignment does not erase the protected holder. A split addendum does not satisfy an archive, sponsor, lawful, public, route-asset, management, recovery, and ending reader at once unless source stamp, holder, bridge, harmed claimant, selected posture, and future effect remain visible.
Entry Contract
claimant_stamp_afteruse_receipt:
trigger_kind: state_pressure
source_claimant_stamp_row_visible: true
source_stamp_state_visible: true
original_stamp_holder_visible_or_explicit_absence: true
protected_absent_holder_visible_or_explicit_absence: true
requested_afteruse_visible: true
future_reader_consumes_stamp_state: true
harmed_or_omitted_claimant_visible_or_explicit_absence: true
player_can_certify_restrict_bridge_reopen_split_quarantine_or_default: true
no_fixed_turn_trigger: true
no_fixed_day_or_week_trigger: true
no_raw_stamp_count_trigger: true
no_dashboard_or_lens_health_trigger: trueAfteruse States
claimant_stamp_afteruse_states:
- unspent_stamp
- afteruse_requested
- stamp_scope_certified
- reader_restricted
- bridge_attached
- protected_holder_reopened
- split_afteruse_required
- afteruse_quarantined
- false_clean_afteruse
- captured_by_reader
- hostile_claimant
- recovery_onlyThe implementation fails if a stamp state is collapsed into a generic notice served, claimant consented, stamp clean, queue resolved, or ending ready flag.
Branch Contract
Every non-default branch must record:
claimant_stamp_afteruse_resolution:
source_claimant_stamp_row: <stamp row id>
source_stamp_state: original_stamp_preserved | proxy_notice_stamped | stamp_addendum_split | reassignment_published | stamp_pad_quarantined | stamp_route_debt | scoped_proxy_stamp | false_clean_proxy_stamp | equivalent
original_stamp_holder_or_absence: <holder or explicit_absence>
protected_absent_holder_or_absence: <holder or explicit_absence>
requested_afteruse: sponsor_package | archive_release | lawful_notice | public_table | receipt_printer | route_asset_clearance | management_report | recovery_lane | ending_gate | equivalent
future_reader_or_route: sponsor_reader | archive_reader | lawful_reader | public_reader | receipt_reader | route_asset_reader | management_reader | recovery_lane | ending | equivalent
harmed_or_omitted_claimant: protected_holder | absent_holder | future_reader_advocate | claimant_family_proxy | archive_claimant | public_claimant | sponsor_claimant | explicit_absence
proof_bridge_or_explicit_absence: queue_receipt | public_notice | lawful_annex | archive_addendum | split_stamp_notice | holder_affidavit | receipt_printer_copy | explicit_absence
selected_afteruse_posture: certify_stamp_scope | restrict_stamp_afteruse_reader | attach_queue_or_public_bridge | reopen_protected_stamp_holder | split_claimant_stamp_afteruse | quarantine_stamp_afteruse
claimant_stamp_afteruse_state_after: <state>
relief_any: []
cost_any: []
future_effect_any: []Failure Cases
The mechanism must fail if:
- a proxy notice stamp is cited as universal claimant consent;
- a public reassignment is used as archive custody with no holder addendum;
- a quarantined stamp pad is treated as route-asset clearance;
- a split stamp addendum is used against the protected holder;
- a false-clean proxy stamp unlocks an ending gate;
- a future route effect changes only notification text, mood, or a generic queue counter.
Default Contract
The default is False Claimant Stamp Afteruse Default. It must record false-clean claimant stamp afteruse, source stamp row or explicit absence, hidden or overbroad stamp scope, capturing reader, harmed or omitted claimant, after-state, future reader effect, at least three counter deltas, and durable mutation.