Collection Release Review / 追偿放行复核

Collection Release Review is the playable rite that decides whether a target locked by recourse can re-enter use as lawful, public, split, partial, refused, or mis-stamped.

It follows 追偿优先级听证 when the player has a target that is already collected, swept, substituted, quarantined, or recovery-only. The rite does not relitigate priority. It asks whether release conditions have been satisfied and what scar remains after release.

Fill condition

Open this rite when all of the following are true:

1. a locked target exists through 担保追偿案卷, 追偿放行回执, facility sealing, archive quarantine, route-asset custody, public restitution, or substitute collateral;
2. the player can provide at least one release input: receipt, handler, seal appeal, checksum, public restitution proof, substitute collateral scar, fan receipt, or facility route;
3. at least one party would be harmed or empowered by release;
4. the result can mutate a route asset, room, proof object, public receipt, schedule lane, handler, faction posture, or broadcast reality state.

The rite is state-triggered. It has no fixed numbered trigger.

Required slots

rite: storyteller.rite.collection_release_review.v1
locked_target_slot:
  accepts: route_asset | facility_room | proof_object | public_receipt | schedule_lane | handler_time | fan_oxygen_pool | legal_seal
release_receipt_slot:
  accepts: card.collection_release_receipt | explicit_absence
handler_slot:
  accepts: producer | legal_handler | archive_handler | editor | runner | public_witness | security | explicit_absence
condition_slot:
  accepts: paid | subordinated | public_restitution_posted | checksum_verified | seal_appealed | substitute_collateral_spent | fan_receipt_signed | route_rerouted | impossible
route_or_room_slot:
  accepts: facility_node | facility_edge | archive_counter | stage_threshold | service_corridor | explicit_absence
harmed_party_slot:
  accepts: sponsor | inspector | archive | editor | fan_public | artist | witness | producer | route_claimant | none

A build may collapse these into UI groups, but evidence must preserve each role.

Branches

Branch A — Lawful release with scar

The target is released through archive, inspector, checksum, seal appeal, or lawful receipt.

Expected outcomes:

release_state_after: released_with_scar | lawful_only
relief: lawful_use_up | custody_clarity_up | archive_fraud_down
cost: bureau_favor_debt_up | inspection_heat_up | route_costlier
future_route_effect: lawful_use_unlocked_with_debt

Branch B — Public restitution release

The target is released because fan/public restitution, Yu Lan proof, witness oath, or public receipt condition is satisfied.

Expected outcomes:

release_state_after: public_only | released_with_scar
relief: public_receipt_legitimacy_up | fan_oxygen_balance_up | audience_stability_up
cost: sponsor_pressure_up | witness_exposure_up | oxygen_liability_up
future_route_effect: public_use_unlocked_with_audit

Branch C — Split copy release

One copy is lawful, one copy is public, or one copy remains quarantined while another becomes usable.

Expected outcomes:

release_state_after: split
relief: one_route_unlocked | claimant_collision_down
cost: source_ambiguity_up | future_fraud_cost_up | copy_discipline_required
future_route_effect: duplicate_copy_challenge_possible

Branch D — Conditional facility release

The release is valid only if moved through a specific room, edge, escort, or service route under 设施通行图机制.

Expected outcomes:

release_state_after: conditional | routed_with_scar
relief: target_moved | room_access_up | emergency_access_up
cost: runner_risk_up | facility_access_pressure_up | room_watched
future_route_effect: future_access_costlier

Branch E — Refuse release and keep recovery-only

The player cannot or will not satisfy release conditions.

Expected outcomes:

release_state_after: refused | recovery_only
relief: false_clean_release_blocked | unsafe_use_blocked
cost: claimant_hostility_up | schedule_pressure_up | black_screen_slots_up
future_route_effect: recovery_only_route_remains

Branch F — Mis-stamp release

The player tries to release without the correct input, or the system incorrectly treats release as clean.

Expected outcomes:

release_state_after: mis_stamped
emitted_event: storyteller.event.release_stamp_misfire.v1
relief: immediate_route_use_up | room_access_up
cost: future_fraud_cost_up | public_receipt_distrust_up | claimant_hostility_up
future_route_effect: false_release_challenge_armed

Required outcome packet

result:
  release_id: <stable id>
  source_recourse_id: <id>
  locked_target_before: <state>
  selected_branch: lawful_release | public_release | split_release | facility_release | refuse_release | mis_stamp
  harmed_party: <party>
  release_state_after: <state>
  target_state_after: <state>
  room_or_route_state_after: <state or none>
  deltas:
    - <relief>
    - <cost>
    - <future route effect>

Failure cases

The rite fails if:

• there is no concrete locked target;
• release has no harmed party;
• release restores a clean target with no durable scar;
• public release, lawful release, and private release produce equivalent outcomes;
• facility movement ignores room or edge state;
• refusal hides the route instead of leaving recovery-only evidence;
• mis-stamp does not emit or record 放行章误触.

Non-goals

• Not a second priority hearing.
• Not an abstract legal appeal.
• Not a fixed collection phase.
• Not a clean unlock button.
• Not valid unless the result mutates future route, asset, room, receipt, lane, handler, faction, or broadcast state.