Relief Callback Settlement / 救济回叫清算
Relief Callback Settlement is the management rite that resolves one row from 救济回叫案卷.
The rite runs when a prior relief is about to be reused by a future reader and the original excluded, deferred, burdened, or explicitly absent reader still has a callback obligation attached to that relief.
Required assignment
The rite cannot resolve from a vague pay debt or send notice action. It requires explicit assignment:
assignment_required:
docket: storyteller.card.relief_callback_docket.v1
source_relief_id: <stable id or explicit_absence>
source_surface: <surface>
relief_beneficiary: <reader>
relief_granted: <relief kind>
relief_cost_or_absence: <cost or explicit_absence>
delayed_obligation: notice | repayment | service | correction | recourse | public_answer | lawful_annex | witness_protection | route_asset_return | equivalent
owed_to_reader: <reader>
excluded_or_deferred_reader_or_absence: <reader or explicit_absence>
future_reader: <reader that now wants to consume the relief>
callback_trigger: <state pressure trigger>
callback_carrier_or_absence: <handler carrier or explicit_absence>
proof_bridge_or_absence: receipt | lawful_annex | public_bulletin | route_asset_release | sponsor_unwind | archive_stamp | edit_checksum | witness_receipt | explicit_absence | equivalent
selected_settlement: honor_now | assign_carrier | convert_to_recourse | publish_debt | fold_into_precedent_scope | quarantine_relief | waive_with_named_harm | default_unanswered
accepted_cost_surface_or_absence: <cost scar or explicit_absence>
future_reader_effect: <effect>The rite fails if sponsor money, archive authority, public sympathy, legal language, management urgency, or broadcast reality resolves the callback without naming owed reader, carrier, proof bridge, settlement, cost, and future reader effect.
Branch families
| Branch | Immediate relief | Cost/scar | Future state |
|---|---|---|---|
| Honor now | delayed reader becomes answerable; false-clean relief blocked | handler burden, route delay, sponsor/public pressure | accepted with callback cost |
| Assign carrier | current route can proceed with visible holder | carrier leverage, capture risk, future audit | callback required or costlier |
| Convert to recourse | relief remains usable while debt holder is named | indemnity pressure, producer-license or sponsor debt | recourse shelf or review required |
| Publish debt | hidden exclusion becomes public memory | sponsor pressure, public confusion, lawful heat | public-only or bulletin required |
| Fold into precedent scope | old relief can be cited only with callback boundary | scope complexity, reader split, archive debt | scoped precedent or variance required |
| Quarantine relief | unsafe reuse blocked | current route blocks, schedule pressure, claimant hostility | blocked or recovery-only |
| Waive with named harm | fastest limited use may proceed | harmed reader becomes hostile or scarred | hostile reader, contradiction pending, costlier |
| Default unanswered | relief appears clean short-term | false-clean relief, excluded-reader retaliation | false-clean, blocked, hostile, or recovery-only |
Success rules
A valid branch must mutate all three:
branch_contract:
relief_surface_changes: true
cost_or_scar_surface_changes: true
future_reader_effect_changes: trueValid future effects include accepted_with_callback, callback_required, costlier, public_only, lawful_only, sponsor_only, split_required, contradiction_pending, blocked, hostile, recovery_only, or false_clean_relief.
Character hooks
-沈洛 can assign sponsor unwind or convert callback into recourse, but contract capture rises. -郁蓝 can publish the debt into public memory, but sponsor pressure and public contradiction rise. -韩砚霜 can attach lawful annex or quarantine relief, but inspection heat and bureau debt rise. -白鸦 can bridge the callback through checksum or route copy state, but source ambiguity and edit debt rise. -A worker witness or public delegate can carry the callback only if protected from becoming silent liability.
Missability
The rite is missed when implementation:
- treats relief as clean once the first crisis is over;
- records callback only as flavor;
- lets one callback satisfy public, lawful, sponsor, route asset, archive, and broadcast-reality readers at once;
- hides the excluded or deferred reader;
- omits carrier or explicit absence;
- produces no future reader effect;
- opens from fixed turn, day/week, raw count, dashboard, or lens-health state.
Recovery is allowed only through visible scar: late honor, public debt bulletin, sponsor unwind, lawful annex, recourse shelf, route quarantine, contradiction-pending route, or recovery-only callback.