Recourse Collection Release / 追偿放行机制

Recourse Collection Release is the mechanism that separates collection from release. It makes sure a target changed by recourse does not become clean simply because a payer recovered, and does not become permanently dead simply because it was swept.

担保追偿优先级机制 decides who can collect and which target is scarred. This mechanism decides whether that target can be used again, by whom, under which release condition, and with which scar.

Design gap closed

The current recourse layer can already produce satisfied, swept, traded, barred, converted_to_public_restitution, and recovery_only outcomes. The missing playable question is what happens afterward:

• a route asset was seized, but can it return as lawful-only, public-only, split, or recovery-only?
• a facility room was locked, but who can reopen it and who is harmed by reopening?
• a proof object was quarantined, but is a checksum enough or does public restitution still matter?
• a schedule lane was posted as substitute collateral, but does release burn the lane or arm a future default?
• a public receipt was honored, but does private collection remain barred or merely subordinated?

Without this mechanism, recourse either becomes a hard delete or a free undo.

State-triggered entry

Open this mechanism when all of the following are true:

1. a target has a post-recourse locked state: seized, captured, posted_as_collateral, quarantined, locked_recovery_only, recovery_only, sealed, claimed, watched, poisoned, or equivalent;
2. the locked target can affect route access, facility access, proof custody, public receipt legitimacy, schedule lane capacity, handler availability, faction posture, or broadcast reality;
3. at least one release input exists or is explicitly absent: 追偿放行回执, handler, seal appeal, checksum, public restitution, substitute scar, fan receipt, or facility route;
4. at least two claimant families would interpret release differently;
5. a release branch can leave a visible scar.

This mechanism must never trigger from fixed turn count.

Core surfaces

• 追偿放行回执 records the source recourse, locked target, release condition, harmed party, and remaining scar.
• 追偿放行复核 resolves lawful, public, split, facility, refused, or mis-stamped release.
• 放行章误触 records unsafe or false clean release.

Release state machine

State	Meaning	Required consequence
locked_by_recourse	Target was changed by recovery, sweep, substitute, quarantine, or seizure.	Release review may be offered if a release input exists.
release_pending	A condition exists but has not been satisfied.	Target remains blocked, watched, or recovery-only.
lawful_only	Archive, inspector, checksum, or seal appeal release permits formal use only.	Bureau debt, inspection heat, or route cost remains.
public_only	Public receipt, fan queue, witness, or restitution release permits public use only.	Sponsor pressure, witness exposure, or audit cost remains.
split	One copy or route is released while another remains locked.	Source ambiguity and copy discipline become active.
conditional	Release works only through a room, edge, escort, or handler.	Facility access pressure or runner risk rises.
refused	Release cannot be issued.	Recovery-only or blocked route remains visible.
mis_stamped	Release is incorrectly treated as clean or routed wrongly.	Misfire event and future challenge are armed.
released_with_scar	Target re-enters play with a durable scar.	Future route, room, receipt, lane, or faction cost persists.

Claimant interpretation families

Sponsor/private release

Sponsor or manager wants the target released quietly to lower default, clean public correction, or preserve naming rights.

Expected branch pressure:

relief_any:
  - sponsor_stop_loss_pressure_down
  - immediate_route_use_up
cost_any:
  - public_receipt_distrust_up
  - contract_capture_up
  - fan_oxygen_resentment_up
future_route_effect_any:
  - public_counter_release_required
  - sponsor_capture_hardened

Inspector/archive release

Inspector or archive wants lawful release through seal appeal, quarantine receipt, admissible copy, or chain of custody.

Expected branch pressure:

relief_any:
  - custody_clarity_up
  - lawful_use_up
cost_any:
  - inspection_heat_up
  - bureau_favor_debt_up
  - route_costlier
future_route_effect_any:
  - lawful_use_unlocked_with_debt
  - appeal_route_required

Public/fan release

Fan public, public receipt, witness chain, Yu Lan, or pirate relay wants release to bind private collection to restitution.

Expected branch pressure:

relief_any:
  - public_receipt_legitimacy_up
  - fan_oxygen_balance_up
cost_any:
  - witness_exposure_up
  - sponsor_pressure_up
  - oxygen_liability_up
future_route_effect_any:
  - public_use_unlocked_with_audit
  - private_clean_release_blocked

Editor/cutroom release

Editor or cutroom wants release through checksum, redaction, source-copy split, or continuity patch.

Expected branch pressure:

relief_any:
  - slot_legibility_up
  - continuity_hazard_down
cost_any:
  - edit_debt_up
  - source_ambiguity_up
  - future_fraud_cost_up
future_route_effect_any:
  - checksum_release_required
  - later_source_challenge_costlier

Facility/production release

Production wants physical release: open room, reroute edge, spend handler, burn schedule lane, move proof, or escort target.

Expected branch pressure:

relief_any:
  - room_access_up
  - target_moved
  - emergency_access_up
cost_any:
  - runner_risk_up
  - facility_access_pressure_up
  - lane_scar_up
  - handler_fatigue_up
future_route_effect_any:
  - future_access_costlier
  - room_watched_or_burned

Branch contract

Every release branch must record:

release_id: <stable id>
source_recourse_id: <recourse row or sweep id>
source_session_id: <session that locked target>
release_session_id: <session that attempted release>
locked_target_before: <target state>
release_input: receipt | handler | seal_appeal | checksum | public_restitution | substitute_scar | fan_receipt | facility_route | explicit_absence
selected_branch: lawful_release | public_release | split_release | facility_release | refuse_release | mis_stamp
harmed_party: <claimant harmed or explicit none>
release_state_after: <state>
locked_target_after: <state>
scar_after_release: <scar>
deltas:
  - <relief>
  - <cost>
  - <future route, asset, room, receipt, lane, handler, faction, or broadcast effect>

Failure cases

The mechanism must fail if:

• collection success automatically clears seizure, quarantine, seal, or recovery-only state;
• seizure or sweep permanently hides a route asset with no recovery-only or release surface;
• release changes only money or mood;
• lawful, public, private, split, and facility release collapse into the same outcome;
• release does not name a harmed party;
• release restores a clean target without scar;
• facility release ignores node/edge state under 设施通行图机制;
• route asset release ignores Route Assets and Custody state;
• mis-stamp fails to emit or record 放行章误触.

Integration notes

• With 担保追偿级联, this mechanism begins after priority has produced a locked or scarred target.
• With 设施通行封控线, release may require room, edge, escort, or seal state.
• With 制作分诊台, release may consume handler time or scar a lane.
• With 公开悔过账本, release wording may be public-only or private-disputed.
• With 路线资产扣押播报, released copies must keep copy discipline or arm a false owner challenge.

Non-goals

• Not a general unlock screen.
• Not a second priority hearing.
• Not a clean debt payoff.
• Not a fixed collection phase.
• Not governance content.
• Not satisfied by page existence; release must be branchy, scarred, and replay-visible.