Settlement Discharge Receipt / 和解清偿回执线

Settlement Discharge Receipt begins after Settlement Aftershock Ledger has already produced a real result and someone wants to mark the debt as discharged.

The prior settlement remains history. This storyline asks the narrower afterlife question: what proof lets a later reader trust the discharge, who paid or carried it, which claimant remains excluded, and what scar prevents the discharge from becoming universal clean closure?

Playable Question

When an aftershock row is marked discharged, does production issue a scoped receipt, publish restitution, file lawful/archive proof, let sponsor pay privately, split discharge into escrow, quarantine the row, or let a false discharge harden?

Every answer must name:

• the source settlement or aftershock row;
• the discharge claim;
• the payer, carrier, authority, or explicit absence;
• the excluded claimant or explicit absence;
• the spent resource, favor, proof, or scar;
• the selected posture;
• one relief surface;
• one cost surface;
• the future reader or route effect.

State-Triggered Entry

Open this storyline only when discharge is about to be consumed:

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
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Do not open from a generic settlement mood, a clean accounting flag, a reputation meter, or a fixed aftermath timer. The trigger is a concrete future reader trying to consume a discharge claim.

Bound Content Pack

• Settlement Discharge Receipt defines discharge scope, payer/authority state, excluded claimant, scar, and false-discharge default.
• Settlement Discharge Receipt records the source row, discharge claim, payer, excluded claimant, spent scar, after-state, and future route effect.
• Settlement Discharge Review resolves scoped, public, lawful, sponsor, split, quarantine, or default posture.
• False Settlement Discharge Default records when a discharge is filed as clean without payer, excluded claimant, scar, or future reader mutation.
• Settlement Discharge Receipt Lens observes the wiki binding and computed branch contract.

Storyline Spine

Beat 1 - A discharged row asks for a reader

An aftershock row says its debt is discharged, converted, paid, released, settled, or closed. A future public table, sponsor package, route asset, lawful reader, archive desk, management report, or broadcast slot now wants to cite that discharge.

Beat 2 - The receipt separates payment from closure

Create or refresh Settlement Discharge Receipt.

settlement_discharge_receipt:
  source_settlement_row: settlement_aftershock.public_aftershock_reconciled.001 | <equivalent>
  discharge_claim: debt_paid | settled_with_scope | release_after_cost | equivalent
  payer_or_discharge_authority: sponsor_escrow | public_restitution | archive_seal | editor_checksum | production_favor | explicit_absence
  excluded_claimant_or_absence: fan_public | lawful_reader | sponsor_counterdesk | archive_claimant | route_asset_holder | explicit_absence
  spent_resource_or_scar: payment | public_receipt | bureau_favor | edit_debt | route_cost | explicit_absence
  discharge_state_after: scoped | public_receipted | lawful_only | sponsor_only | split_escrowed | quarantined | false_clean
  future_reader_or_route_effect: accepted_with_scar | public_addendum_required | lawful_only | sponsor_gate_required | split_required | recovery_only

The receipt fails if it only says “paid” or “closed.” It must show what was spent, who remains outside the discharge, and what future reader can do with the result.

Beat 3 - The review chooses discharge posture

Run Settlement Discharge Review. The valid posture families are:

• issue scoped discharge receipt;
• public restitution discharge;
• lawful archive discharge;
• sponsor private discharge;
• split discharge escrow;
• refuse or quarantine discharge;
• false settlement discharge default.

Each branch preserves the source settlement row while changing relief, cost, and future-reader state.

Beat 4 - Future play consumes the receipt

The future reader must read discharge_state_after, not a bare boolean. The row may be accepted with scar, public-only, lawful-only, sponsor-only, split, quarantined, recovery-only, or false-clean.

Beat 5 - False discharge becomes a durable scar

If the implementation lets management, sponsor, archive, or production file discharge without payer/authority, excluded claimant, spent resource, or future reader effect, False Settlement Discharge Default fires or remains armed.

Branch Map

Branch	Immediate relief	Cost/scar	Future state
Issue scoped receipt	discharge can be cited for one reader	public addendum or route scar remains	accepted_with_scar
Public restitution discharge	public/fan legitimacy improves	sponsor, inspection, or archive pressure rises	public_receipted
Lawful archive discharge	formal proof improves	lawful-only mismatch or bureau favor debt rises	lawful_only
Sponsor private discharge	sponsor pressure drops	public distrust, capture, or claimant hostility rises	sponsor_gate_required
Split discharge escrow	false universal closure is blocked	two readers require later reconciliation	split_required
Refuse/quarantine	unsafe discharge is stopped	route remains costlier or recovery-only	quarantined_or_recovery_only
False default	short relief may appear	false discharge hardens	recovery_only_or_challenged

No branch may turn one discharge receipt into clean closure for public, lawful, sponsor, archive, management, route-asset, and broadcast readers at once.

Missability And Recovery

This storyline is missed when implementation:

• records aftershock_discharged without a receipt row;
• names payment but not an excluded claimant;
• lets sponsor, archive, lawful, or management discharge stand in for public acceptance;
• hides the resource or favor spent to discharge the row;
• lets a future route consume clean closure from a settlement aftershock.

Recovery requires visible cost: issue a late receipt, publish restitution, reopen lawful/archive proof, split discharge into escrow, quarantine the route, accept sponsor unwind, or mark the row recovery-only.

Non-goals

Not a new settlement trial, generic accounting page, reputation repair, global debt ledger, or clean undo of aftershock pressure. The prior settlement remains true; this storyline only controls how its claimed discharge is consumed.