Callback Consumption Review / 回叫消费复核

Callback Consumption Review is the assignable rite for deciding whether a future reader may consume a prior relief row after callback obligations have entered the story.

It is not the original callback settlement. It happens later, when a desk, package, route, sponsor, public receipt, lawful annex, archive copy, broadcast slot, or ending reader tries to use the relief as proof that a problem is settled.

Rite shape

rite_id: storyteller.rite.callback_consumption_review.v1
duration_class: state-pressure-window
requires_any:
  - card.callback_consumption_docket
  - equivalent callback consumption row
assign_slots: 4_to_5
primary_costs:
  - owed reader pressure
  - callback carrier burden
  - public debt
  - lawful annex
  - sponsor unwind
  - route delay
  - archive quarantine
  - recovery-only scar
failure_surface: storyteller.event.callback_laundering_default.v1

The rite is reusable and opens from live state pressure only. It is not a fixed appointment, timer, chapter beat, cleanup phase, or dashboard health response.

Required assignment slots

Slot 1 — Source relief row

Assign one source row or explicit absence:

  • relief callback row;
  • broadcast slot relief;
  • signatory counterclaim release;
  • oxygen clawback stay, haircut, or foreclosure relief;
  • future broadcast witness relief;
  • sponsor release;
  • public receipt;
  • lawful annex;
  • route asset unlock;
  • explicit absence.

Absence is not neutral. It weakens, blocks, or defaults the review.

Slot 2 — Callback state

Assign the callback state that travels with the relief:

  • honored;
  • assigned;
  • owed;
  • deferred;
  • disputed;
  • converted;
  • quarantined;
  • waived with named harm;
  • defaulted;
  • explicit absence.

The rite must fail or arm default if the state is summarized as handled without the owed reader and future effect.

Slot 3 — Future reader and intended use

Assign who wants to consume the relief and why:

  • public receipt;
  • lawful annex;
  • archive proof;
  • sponsor release;
  • management closure;
  • producer-license review;
  • route asset unlock;
  • broadcast reality;
  • black-box or ending reader;
  • equivalent.

The intended use must be visible: proof package, closure report, precedent citation, slot binding, sponsor release, route unlock, public receipt, lawful annex, ending scar, or equivalent.

Slot 4 — Owed reader, carrier, proof bridge, or explicit absence

Assign at least one carrier/proof object and name the owed or excluded reader:

  • callback carrier;
  • public bulletin;
  • lawful addendum;
  • sponsor unwind;
  • archive stamp;
  • edit checksum;
  • witness receipt;
  • route asset return;
  • handler burden;
  • explicit absence.

A carrier cannot erase the reader. A proof bridge cannot erase harm. Explicit absence must create cost or block the clean claim.

Slot 5 — Boundary cost

Optional for weak branches, required for strong acceptance:

  • route delay;
  • public debt note;
  • lawful annex;
  • sponsor unwind;
  • reader scope split;
  • archive quarantine;
  • witness protection;
  • recovery-only scar;
  • future surcharge.

Branch outcomes

Branch A — Accept with callback

Requirements:

  • source relief is present;
  • callback state is honored, assigned, or carried with proof;
  • owed reader is visible;
  • future reader accepts only inside named boundary.

Effects:

callback_consumption_state_after: accepted_with_callback
relief_any:
  - callback_legitimacy_up
  - future_reader_trust_up
cost_any:
  - route_delay_up
  - handler_burden_up
  - public_receipt_complexity_up
future_reader_effect_any:
  - accepted_with_callback
  - costlier

Branch B — Attach callback cost to the route

Requirements:

  • the relief can be used before full callback settlement;
  • the delayed obligation remains visible and attached to a carrier.

Effects:

callback_consumption_state_after: cost_attached
relief_any:
  - immediate_route_pressure_down
  - closure_report_allowed_with_callback
cost_any:
  - callback_debt_up
  - owed_reader_leverage_up
  - future_route_cost_up
future_reader_effect_any:
  - callback_required
  - costlier

Branch C — Convert reader scope

Requirements:

  • public, lawful, sponsor, archive, route, or broadcast-reality readers cannot all accept the same relief;
  • the player chooses an allowed reader scope.

Effects:

callback_consumption_state_after: reader_scoped
relief_any:
  - false_clean_relief_down
  - consumer_scope_clarity_up
cost_any:
  - incompatible_reader_pressure_up
  - split_required_up
future_reader_effect_any:
  - public_only
  - lawful_only
  - sponsor_only
  - split_required

Branch D — Publish callback debt

Requirements:

  • the callback is owed or deferred;
  • the future reader can proceed only if the debt becomes public, lawful, archive, or route memory.

Effects:

callback_consumption_state_after: debt_published
relief_any:
  - callback_discoverability_up
  - hidden_exclusion_down
cost_any:
  - sponsor_pressure_up
  - public_confusion_up
  - lawful_heat_up
future_reader_effect_any:
  - public_only
  - lawful_annex_required
  - contradiction_pending

Branch E — Quarantine relief

Requirements:

  • proof bridge, owed reader, carrier, or named harm is absent or disputed;
  • the player blocks clean consumption.

Effects:

callback_consumption_state_after: quarantined
relief_any:
  - false_clean_relief_down
  - source_relief_preserved
cost_any:
  - route_delay_up
  - archive_debt_up
  - recovery_only_pressure_up
future_reader_effect_any:
  - blocked
  - recovery_only
  - contradiction_pending

Branch F — Waive with named harm

Requirements:

  • the player chooses speed or narrow release;
  • the harmed reader and harm are named.

Effects:

callback_consumption_state_after: waived_with_named_harm
relief_any:
  - immediate_consumption_allowed
cost_any:
  - owed_reader_hostility_up
  - public_receipt_distrust_up
  - future_recovery_cost_up
future_reader_effect_any:
  - hostile
  - costlier
  - contradiction_pending

Branch G — Launder as clean default

Requirements:

  • missing callback state, hidden owed reader, hidden carrier, missing proof bridge, or unnamed waiver harm;
  • the future reader accepts the relief as clean anyway.

Effects:

callback_consumption_state_after: false_clean_laundered
emits_or_arms: storyteller.event.callback_laundering_default.v1
cost_any:
  - false_clean_relief_up
  - callback_laundering_up
  - owed_reader_hostility_up
  - broadcast_reality_drift_up
future_reader_effect_any:
  - false_clean_relief
  - blocked
  - hostile
  - recovery_only

Blocked and weakened reasons

Expose blocked offers rather than hiding them:

  • source_relief_missing
  • callback_state_hidden
  • owed_reader_hidden
  • excluded_reader_hidden
  • carrier_missing
  • proof_bridge_missing
  • future_reader_overbroad
  • waiver_harm_unnamed
  • sponsor_clean_capture_active
  • public_lawful_surface_collision

Counter contract

Every resolution must mutate at least three counters or durable states. At least one must be relief, one cost, and one future-reader effect.

Primary counters:

  • callback_legitimacy
  • callback_debt
  • callback_laundering
  • false_clean_relief
  • owed_reader_hostility
  • future_reader_trust
  • route_delay
  • handler_burden
  • public_receipt_legitimacy
  • public_receipt_distrust
  • lawful_heat
  • sponsor_pressure
  • sponsor_capture
  • archive_debt
  • broadcast_reality_drift
  • future_route_cost
  • recovery_only_pressure

Non-goals

  • Not the original relief settlement.
  • Not a generic legal review.
  • Not a fixed cleanup phase.
  • Not valid if it lets a later reader consume relief without source relief, callback state, owed reader, future reader, selected posture, cost, and future effect.