Branch Reward Afteruse Receipt
Branch Reward Afteruse Receipt makes a previously vested branch reward reusable only through named afteruse scope.
The mechanism exists when a prior reward state is still true but a later reader wants to spend it in another context. A vested reward does not prove universal permission. A split reward does not satisfy sponsor, public, lawful, archive, route-asset, management, broadcast-reality, branch eligibility, and ending readers at once unless source row, owner, accepted scope, bridge, excluded reader, selected posture, and future effect remain visible.
Entry Contract
branch_reward_afteruse_receipt:
trigger_kind: state_pressure
source_reward_row_visible: true
source_reward_state_visible: true
vested_owner_visible_or_explicit_absence: true
accepted_scope_visible_or_explicit_absence: true
requested_afteruse_visible: true
future_reader_consumes_reward_state: true
excluded_or_subordinated_reader_visible_or_explicit_absence: true
proof_bridge_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_reward_count_trigger: true
no_dashboard_or_lens_health_trigger: trueAfteruse States
branch_reward_afteruse_states:
- unspent_scoped_reward
- afteruse_requested
- reward_scope_certified
- reader_restricted
- bridge_required
- excluded_reader_reopened
- split_afteruse_required
- afteruse_quarantined
- false_clean_afteruse
- captured_by_reader
- hostile_excluded_reader
- recovery_onlyThe implementation fails if a vested reward state is collapsed into a generic reward valid, bonus accepted, package cleared, route discount, or ending ready flag.
Branch Contract
Every non-default branch must record:
branch_reward_afteruse_resolution:
source_reward_row: <reward row id>
source_reward_state: vested | split_required | escrowed | route_asset_scoped | transferred | spent_with_scar | quarantined | forfeited | captured_default | false_universal | recovery_only | equivalent
vested_owner_or_absence: <owner or explicit_absence>
accepted_scope_or_absence: <scope or explicit_absence>
requested_afteruse: sponsor_package | public_receipt | lawful_annex | archive_fastlane | route_loadout | management_report | broadcast_reality_patch | branch_eligibility_bridge | ending_gate | equivalent
future_reader_or_route: sponsor_reader | public_reader | lawful_reader | archive_reader | route_asset_reader | management_reader | broadcast_reality | branch_eligibility | ending | equivalent
excluded_or_subordinated_reader: original_beneficiary | public_reader | sponsor_reader | lawful_reader | archive_reader | route_asset_reader | claimant | artist_boundary | explicit_absence
proof_bridge_or_explicit_absence: reward_receipt | lawful_annex | archive_addendum | public_bulletin | route_asset_custody_note | transfer_receipt | split_reader_note | explicit_absence
selected_afteruse_posture: certify_reward_scope | restrict_reward_afteruse_reader | attach_reward_bridge | reopen_excluded_reader | split_reward_afteruse | quarantine_reward_afteruse
branch_reward_afteruse_state_after: <state>
relief_any: []
cost_any: []
future_effect_any: []Failure Cases
The mechanism must fail if:
- a vested reward is cited as universal sponsor and public permission;
- a transfer receipt is used as route loadout proof with no owner addendum;
- a split reward is treated as management closure;
- a lawful annex is used against the original beneficiary;
- a quarantined reward unlocks an ending gate;
- a future route effect changes only notification text, mood, or a generic reward counter.
Default Contract
The default is False Branch Reward Afteruse Default. It must record false-clean reward afteruse, source row or explicit absence, hidden or overbroad reward scope, capturing reader, harmed or excluded reader, after-state, future reader effect, at least three counter deltas, and durable mutation.