Settlement Discharge Receipt / 和解清偿回执机制

Settlement Discharge Receipt is the mechanism for turning aftershock_discharged, debt_paid, release_after_cost, or equivalent closure into a scoped route object.

It exists because Settlement Aftershock Ledger can correctly leave relief plus debt, while Management Compression Desk can later over-count that relief. This mechanism prevents the middle step from being too clean: discharge is useful only when payer, excluded claimant, scar, and future reader are visible.

Entry Contract

Open only from state pressure:

entry_state:
  trigger_kind: state_pressure
  source_settlement_aftershock_row_present: true
  discharge_claim_visible: true
  payer_or_discharge_authority_visible: true
  excluded_claimant_or_explicit_absence_visible: true
  spent_resource_or_scar_visible: true
  future_reader_consumes_discharge_state: true
  no_fixed_turn_trigger: true

State Machine

StateMeaningFuture rule
discharge_unreada row claims closure but no future reader has checked itoffer receipt/review
scoped_discharge_receiptedone reader can consume the discharge with scarfuture use must match scope
public_restitution_dischargepublic/fan surface sees the paid costpublic route can proceed with cost
lawful_archive_dischargeformal proof exists but public acceptance may notlawful/archive use only
sponsor_private_dischargesponsor pays or holds the costsponsor gate and public distrust remain
split_discharge_escroweddischarge is split between readerslater reconciliation required
discharge_quarantinedclosure is refused as unsaferecovery-only or costlier route
false_clean_dischargedischarge is filed without required locksdefault event mutates future play

Branch Contract

Every constructive branch must expose:

  • source settlement row;
  • discharge claim;
  • payer, authority, or explicit absence;
  • excluded claimant or explicit absence;
  • spent resource or scar;
  • selected posture;
  • future reader or route effect.

Every branch must mutate one relief, one cost, and one future reader state.

Counters And Surfaces

Valid surfaces include public_receipt_legitimacy, public_receipt_distrust, sponsor_stop_loss_pressure, contract_capture, inspection_heat, bureau_favor_debt, archive_debt, edit_debt, route_asset_pressure, future_recovery_cost, claimant_hostility, and management_false_clean.

Failure Rule

If discharge is consumed without payer/authority, excluded claimant, spent scar, and future reader effect, False Settlement Discharge Default fires or arms. The default must not be a reputation penalty; it must change route access, reader trust, claimant hostility, or recovery cost.

Integration