Crisis Ledger Reconciliation Storyline / 危机台账对表线

Crisis Ledger Reconciliation is a pressure-system storyline for the producer desk after one crisis ledger has produced relief but before that relief is allowed to travel as universal truth.

The player may have stabilized a slot, paid oxygen, obtained an archive seal, aired public contrition, accepted sponsor makegood, or preserved a route asset. This storyline asks the next management question: which reader is allowed to consume that relief, and which reader is still unpaid?

It is a storyline because the mismatch unfolds through a pack of objects: a docket, a review rite, a breach event, counters, residual debts, future route effects, and route-asset scars.

Why this is the next useful gap

Existing Storyteller surfaces already define strong local pressure loops:

• 呼吸索赔交易所 makes oxygen settlement local and claimant-driven.
• 播出档期合约机制 makes schedule authority scoped by reader and harmed reader.
• 公开悔过账本机制 makes public wording into a stateful object.
• 和解反震账本 keeps post-settlement debt from disappearing.
• Route Assets and Custody makes proof and people persistent assets.

The missing playable gap is cross-ledger false equivalence. A replay can satisfy each local mechanism yet still fake progress if it lets one green result clear every other ledger. This storyline makes those conversions explicit, costed, and replay-provable.

Primary playable question

When one ledger is relieved and another ledger wants to consume that relief, does the producer convert with receipt, split readers, publish the mismatch, quarantine the mismatch, pawn it to a claimant, or suppress it until breach?

No answer may satisfy schedule, oxygen, archive, sponsor, public legitimacy, route recovery, and lawful proof for free.

State-triggered entry

Open this storyline when all conditions are true:

1. at least two pressure ledgers reference the same crisis surface;
2. one ledger has relief and one ledger has debt, incompatible reader, omitted claimant, or uncertain proof;
3. a target use is being attempted: public reality, lawful proof, fan refund, sponsor relief, archive signature, route recovery, audience stability, schedule release, correction authority, or memorial voice;
4. a handler, route asset, proof carrier, claimant, or explicit no-show can be assigned;
5. future content will consume the reconciliation result.

The storyline is entered from ledger mismatch. It must not be opened from a fixed sequence number, page count, or lens-health condition.

Content pack

Mechanic

• 危机台账对表机制 — defines mismatch rows, source relief, target use, reader scope, branch contracts, residual debt, breach, and replay evidence.

Card

• 危机台账对表案卷 — stores the mismatch rows and future-reader scars.

Rite

• 危机台账对表复核 — assignable review where player chooses conversion posture.

Event

• 危机台账错配破口 — breach when false conversion becomes visible.

Primary actors and handlers

• Shen Luo can convert with sponsor language, pawn pressure, or buy immediate schedule relief while creating capture.
• Yu Lan can publish mismatch, attach public/fan receipt, and make omitted harm visible at sponsor or inspection cost.
• Han Yanshuang can make conversion lawful, quarantine false proof, or impose archive/bureau debt.
• Baiya can split readers through checksum, edit lane, black-box proof, or patching, while adding ambiguity and future correction cost.
• Route assets from Route Assets and Custody can become proof carrier, residual-debt hostage, omitted claimant, or recovery sacrifice.

Core storyline states

State	Meaning	Required consequence
reconciliation_unopened	Ledgers disagree but no docket row exists.	Future use risks hidden false conversion.
mismatch_open	Docket row names source relief, target use, target reader, and incompatible reader.	Review, split, publish, quarantine, pawn, or suppress are available.
conversion_under_review	Handler, proof anchor, posture, and residual destination are assigned.	Both source and target ledgers can mutate.
converted_with_residual	Relief travels with a visible debt row.	Target improves; omitted claimant/future reader is scarred.
split_reader_truth	Public, lawful, sponsor, fan, archive, editor, or route readers receive different scopes.	Later content must consume narrowed reader states.
mismatch_published	Producer makes the incompatibility public.	Legitimacy can rise, but sponsor/inspection/schedule/route pressure rises.
mismatch_quarantined	Producer blocks unsafe conversion.	Fraud/capture falls; delay, audience, fan, sponsor, or route cost rises.
mismatch_pawned	Claimant carries the mismatch for immediate relief.	Capture or favor debt becomes future narration right.
mismatch_suppressed	Producer hides omitted reader or missing proof.	Breach is armed.
mismatch_breached	False conversion becomes visible.	Event mutates route, reader, legality, or custody state.
false_conversion_hardened	Ignored mismatch becomes route law.	Recovery requires addendum, counterproof, public admission, split, or sacrifice.

Branch model

Branch A — Convert with receipt

The player records a conversion row that lets relief travel to a new reader while preserving residual debt.

Expected outcomes:

• converted_with_residual;
• target reader improves: public legitimacy, lawful proof, schedule release, fan refund legibility, archive signature, route recovery, or audience stability;
• residual debt rises for a named claimant;
• future route reads a scarred success, not clean universal victory.

Branch B — Split readers

The player makes incompatible readers explicit instead of pretending they agree.

Expected outcomes:

• split_reader_truth;
• public-only, lawful-only, sponsor-only, fan-only, archive-only, editor-only, or route-only states are created;
• contradiction, schedule pressure, source ambiguity, or future correction cost rises;
• later routes can choose which scope to consume.

Branch C — Publish mismatch

The player exposes the mismatch as part of public truth.

Expected outcomes:

• mismatch_published;
• public receipt, fan legitimacy, artist trust, or private-capture resistance improves;
• sponsor pressure, inspection heat, schedule pressure, witness exposure, or route retaliation rises;
• a later claimant can attack the publication if residual debt is unpaid.

Branch D — Quarantine mismatch

The player blocks transfer until missing proof or claimant consent is handled.

Expected outcomes:

• mismatch_quarantined;
• false clean slot use, archive fraud, reality drift, contract capture, or false owner risk falls;
• audience churn, schedule pressure, fan resentment, sponsor pressure, route delay, or recovery cost rises;
• future route requires addendum, counterproof, or public receipt.

Branch E — Pawn to claimant

The player lets sponsor, archive, inspector, fan public, editor, artist, route asset, or blackout system carry the mismatch for immediate relief.

Expected outcomes:

• mismatch_pawned;
• immediate pressure may drop;
• capture, bureau favor debt, public distrust, fan resentment, route capture, or future recovery cost rises;
• pawned claimant gains future narration right.

Branch F — Suppress, breach, or harden

The player hides the mismatch, omits the harmed reader, lacks proof, spends split state as universal truth, or consumes source relief without residual.

Expected outcomes:

• mismatch_suppressed, mismatch_breached, or false_conversion_hardened;
• 危机台账错配破口 fires or arms;
• future content becomes blocked, hostile, captured, costlier, recovery-only, public-only, lawful-only, sponsor-only, or contradiction-pending.

Counter contract

Every branch must mutate at least three counters or durable states. Required movement:

• at least one source relief preserved or target relief granted;
• at least one residual cost or omitted-claimant pressure increased;
• at least one future reader/route scope changed.

Primary counters and states:

• source_relief_preserved
• residual_debt
• target_legitimacy
• public_receipt_legitimacy
• public_receipt_distrust
• fan_oxygen_balance
• fan_oxygen_resentment
• archive_signature_legitimacy
• archive_debt
• custody_gap
• inspection_heat
• bureau_favor_debt
• sponsor_stop_loss_pressure
• contract_capture
• schedule_pressure
• slot_authority_clarity
• false_clean_slot_use
• audience_stability
• audience_churn
• artist_trust
• artist_boundary_pressure
• route_asset_pressure
• route_delay
• route_asset_capture
• source_ambiguity
• future_correction_cost
• contradiction_pending
• reality_drift
• black_screen_slots

Missability and recovery

This storyline is missable when the player treats source relief as clean universal success, hides missing proof, fails to name target reader, omits incompatible claimant, consumes a split reader as universal, or lets pawned claimant narrate before review.

Recovery is allowed only with stateful cost:

• reopen the docket and publish mismatch;
• add lawful proof and accept public distrust;
• attach fan refund and accept sponsor or archive cost;
• quarantine and accept schedule/audience pressure;
• split readers and accept contradiction pending;
• sacrifice route asset, favor, or sponsor relief to unwind hardening.

Integration notes

• With Oxygen Claim Exchange Storyline, oxygen relief can become a source row, not a universal proof.
• With 播出档期合约绑定线, scoped authority can be reconciled with public or lawful readers.
• With 档期抢占认领线, displaced claims become incompatible reader evidence.
• With 公开悔过账本, apology wording can be reconciled against lawful, archive, sponsor, or fan readers.
• With 和解反震账本, later aftershock inherits row ids and residual debt instead of generic escalation.

Replay/session evidence expectation

Expected evidence:

storyline_id: storyteller.storyline.crisis_ledger_reconciliation.v1
session_id: lens-storyteller-crisis-ledger-reconciliation-v1-<timestamp>
seed: <deterministic-seed>
source_surface:
  ledger: <ledger>
  object_id: <object or explicit_absence>
  relief: <relief>
  debt: <debt or explicit_absence>
docket:
  row_id: <row>
  target_claimed_use: <use>
  target_reader: <reader>
  incompatible_reader_or_claimant: <reader or claimant>
  proof_anchor: <anchor or explicit_absence>
review:
  handler: <actor or absence>
  posture: convert_with_receipt | split_readers | publish_mismatch | quarantine_mismatch | pawn_to_claimant | suppress_or_default
  residual_debt_destination: <claimant or none>
outcome:
  row_state_after: <state>
  future_route_effect: <effect>
  event_seen_or_armed: storyteller.event.crisis_ledger_mismatch_breach.v1 | none
  counter_deltas:
    relief: []
    cost: []
    future: []

Non-goals

• Not filler escalation.
• Not a fixed sequence storyline.
• Not a governance or implementation-policy page.
• Not another generic settlement aftermath.
• Not satisfied by raw lens count or placeholder rows.
• Not a universal resource exchange.
• Not a replacement for the source ledgers; it binds the moment one ledger tries to speak for another.