Release Stamp Afteruse Receipt

Release Stamp Afteruse Receipt prevents a prior release stamp from laundering later use of a locked, scarred, split, conditional, public-only, lawful-only, or recovery-only target.

Required state surfaces:

• source release stamp and source release state;
• source locked target;
• release scope;
• requested afteruse and future reader or route consuming the stamp;
• harmed or omitted claimant or explicit absence;
• facility route state or explicit absence;
• proof bridge or explicit absence;
• selected afteruse posture and state after resolution;
• counter deltas for facility pressure, public trust, inspection heat, source ambiguity, route cost, and claimant hostility.

State Machine

State	Meaning	Required consequence
stamp_pending_afteruse	A future reader wants to cite the release stamp.	Docket must be created or explicit absence recorded.
scope_certified	One named reader may consume the release.	Other readers remain restricted.
reader_restricted	Overbroad afteruse is blocked.	Capturing reader cannot claim universal release.
bridge_required	Facility, public, lawful, checksum, restitution, or route bridge must carry the stamp.	Bridge cost and proof burden remain visible.
target_or_claimant_reopened	Source lock, target, or harmed claimant needs a new answer.	Later route is delayed, scarred, or costlier.
split_required	Different readers need separate release receipts.	Copy discipline and source ambiguity stay active.
afteruse_quarantined	The release stamp cannot be spent yet.	Current use is blocked or recovery-only.
false_clean_afteruse	A desk consumes the stamp as universal release.	False release stamp afteruse default mutates future play.

Default behavior is not flavor text. If the player lets false-clean afteruse stand, the game records a scar that future readers can consume as a disputed release stamp rather than clean proof.