Branch Reward Afteruse Receipt

Branch Reward Afteruse Receipt starts after Branch Reward Vesting has already made a positive reward visible, owned, split, escrowed, transferred, spent with scar, quarantined, captured, or recovery-only.

The parent line answers the first reward question: what success created the reward, who owns it, which reader may spend it, and which excluded reader follows the row. This follow-on answers the later reader question: when a sponsor package, public receipt, lawful annex, archive fast-lane, route loadout, management report, broadcast-reality patch, branch eligibility bridge, or ending gate cites that old reward as clean permission, which scope can actually travel?

Playable Question

When a later reader consumes a prior branch reward state, does production certify the reward scope, restrict the afteruse reader, attach a bridge, reopen the excluded reader, split the reward afteruse row, quarantine the claim, or let a false-clean reward afteruse default harden?

Every answer must name the source reward row, source reward state, vested owner, accepted scope, requested afteruse, future reader, excluded or subordinated reader, proof bridge, selected posture, after-state, and future route effect.

State-Triggered Entry

entry_state:
  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: true

Entry cannot be a turn number, day/week interval, raw reward count, dashboard state, or lens-health state. It is always a later reader trying to spend a previous branch reward state.

Bound Content Pack

• Branch Reward Afteruse Receipt defines afteruse states, branch posture, and false-clean reward afteruse behavior.
• Branch Reward Afteruse Docket records source reward row, reward state, owner, accepted scope, requested afteruse, future reader, excluded reader, proof bridge, after-state, and future effect.
• Branch Reward Afteruse Review resolves scope certification, reader restriction, bridge attachment, excluded-reader reopening, split afteruse, quarantine, or default.
• False Branch Reward Afteruse Default records when a vested, split, escrowed, transferred, spent, quarantined, captured, or recovery-only reward is cited as universal permission.
• Branch Reward Afteruse Receipt Lens observes this contract.

Storyline Spine

Beat 1 - A branch reward survives vesting

A prior reward state may be vested, split_required, escrowed, route_asset_scoped, transferred, spent_with_scar, quarantined, forfeited, captured_default, false_universal, or recovery_only.

The old reward state remains true. This packet does not relitigate whether the original branch reward was earned or vested.

Beat 2 - A later reader spends the reward

A sponsor package, public receipt, lawful annex, archive fast-lane, route loadout, management report, broadcast-reality patch, branch eligibility bridge, or ending gate cites the old reward as proof that the current use is clean.

Create or refresh Branch Reward Afteruse Docket before the reward claim can be consumed.

Beat 3 - Review separates reward ownership from afteruse scope

Run Branch Reward Afteruse Review. The player chooses whether the old reward state can be certified for a named reader, narrowed, bridged, reopened, split, quarantined, or left to default.

No branch may make one reward clean for sponsor, public, lawful, archive, route-asset, management, broadcast-reality, branch-eligibility, and ending readers at once.

Beat 4 - Future play consumes the after-state

Future play reads branch_reward_afteruse_state_after, not the raw existence of a reward. A sponsor reader may accept a scoped credit while a public reader still demands a receipt. A route loadout may accept a transferred reward while broadcast reality still marks the row contradiction-pending until the excluded reader is named.

Branch Map

Branch	Relief	Cost/scar	Future state
certify_reward_scope	one named reader can cite the reward	universal reward permission is blocked	accepted with scoped reward
restrict_reward_afteruse_reader	overbroad sponsor, public, or management use is split	excluded reader hostility or notice cost rises	reader-specific or split required
attach_reward_bridge	reward receipt, lawful annex, archive addendum, public bulletin, route custody note, or transfer receipt can carry it	bridge burden or source ambiguity rises	bridge or addendum required
reopen_excluded_reader	subordinated reader gets answer before the reward travels	delay, public distrust, or claimant pressure rises	excluded reader reopened with scar
split_reward_afteruse	incompatible readers consume separate reward receipts	handler burden and future collision risk rise	split required
quarantine_reward_afteruse	false-clean reward use is blocked	current route loses the perk or stalls	blocked or recovery-only
false_reward_afteruse_default	fastest desk treats the old reward as universal permission	hidden reader and capture pressure harden	captured, hostile, costlier, blocked

Default

false_branch_reward_afteruse_default:
  false_clean_reward_afteruse: true
  source_reward_row_or_absence: <reward row or explicit_absence>
  hidden_or_overbroad_reward_scope: vested | split_required | escrowed | route_asset_scoped | transferred | spent_with_scar | quarantined | captured_default | false_universal | recovery_only | explicit_absence
  capturing_reader_or_route: sponsor_package | public_receipt | lawful_annex | archive_fastlane | route_loadout | management_report | broadcast_reality_patch | branch_eligibility_bridge | ending_gate | equivalent
  harmed_or_excluded_reader: original_beneficiary | public_reader | sponsor_reader | lawful_reader | archive_reader | route_asset_reader | claimant | artist_boundary | explicit_absence
  branch_reward_afteruse_state_after: false_clean_afteruse | reader_restricted | bridge_required | excluded_reader_reopened | split_required | afteruse_quarantined | captured | recovery_only
  future_reader_effect: reward_scope_receipt_required | reader_restriction_due | bridge_due | excluded_reader_reopen_due | split_afteruse_required | blocked | hostile | costlier | recovery_only
  counter_deltas_min: 3
  durable_mutation: true

Non-Goals

• Not a replacement for Branch Reward Vesting.
• Not a generic bonus shop.
• Not a raw reward-count audit.
• Not valid unless a later reader or route consumes the old reward state.