Route Asset Debt Reconciliation Board / 路线资产债务对账会

Route Asset Debt Reconciliation Board is a non-character storyline for the moment when several valid systems disagree about the same route asset.

A route asset may be fresh in Route Asset Maintenance Triage, still carrying consent debt in Consent Debt Transfer, marked released by Witness Carrier Discharge, claimed by a pressure actor through Pressure Claimant Conversion Chain, and read differently by Custody Oracle Crossread. This storyline makes that disagreement playable before the asset unlocks another route.

Primary playable question

When the same route asset has contradictory debt, consent, witness, custody, and claimant readings, who gets to certify its usable state — and which future route pays for that certification?

The board is not a governance scene. It is a crisis pack: the player chooses which ledger becomes authoritative, which ledger is subordinated, and what scar remains on the route asset.

Entry state

Open only from state pressure:

entry_state:
  trigger_kind: state_pressure
  route_asset_row_exists: true
  asset_has_future_route_use: true
  ledger_claims_min: 2
  conflicting_ledger_reading_present: true
  playable_certification_choice_available: true
  no_fixed_turn_trigger: true

The storyline must not open from fixed turn count, chapter count, calendar delay, lens health, or raw number of pages.

Board row

Each board row must expose the asset, at least two ledger claims, and the future-route consequence if unresolved.

reconciliation_row:
  route_asset_id: <asset id>
  intended_future_route: <route or explicit_absence>
  ledger_claims:
    - ledger: maintenance | consent_debt | witness_discharge | claimant_conversion | custody_crossread | equivalent
      source_surface: <id>
      claimant_or_carrier: <actor or explicit_absence>
      reading: fresh | due | released | assigned | contested | reverted | false_clean | captured | recovery_only | equivalent
      proof_or_absence: <proof or explicit_absence>
      cost_if_certified: <cost or explicit_absence>
      cost_if_subordinated: <cost or explicit_absence>
  conflict_kind: double_certification | false_clean_release | stale_but_released | consent_unpaid_but_asset_fresh | claimant_gate_but_route_open | custody_crossread_split | equivalent
  certification_window: open | narrowing | last_clean_certification | default_ready
  future_route_effect_if_unresolved: blocked | costlier | captured | recovery_only | contradiction_pending | watchlisted

A row is invalid if it only says asset_ok, debt_paid, cleared, or approved.

Branch model

Certify maintenance ledger

The asset freshness row becomes authoritative. The future route may open, but a consent, witness, claimant, or custody ledger is subordinated and receives a visible scar.

Certify consent ledger

The consent carrier becomes authoritative. consent_integrity or refusal_legibility rises, while route asset use becomes lawful-only, public-only, costlier, or delayed.

Certify witness discharge

The witness release row becomes authoritative. Witness burden falls, but another carrier, sponsor, archive, or production row receives the remaining cost.

Certify claimant control

A pressure claimant becomes the route asset’s gate. The route may still open, but only through claimant terms, public counterclaim, sponsor gate, lawful gate, or recovery-only use.

Split certification

Different ledgers are certified for different uses. One future route accepts the asset with scar; another route rejects, delays, or becomes costlier.

Refuse certification

The asset is frozen. Current route blocks, narrows, or needs a substitute asset; recovery hook must be named.

False-clean default

If the conflict is hidden or the loudest ledger wins without cost, the asset becomes false-clean or contradiction-pending. Future route cannot remain clean success.

Counter contract

Every resolved branch mutates at least four durable states:

1. route asset certification state;
2. certified or subordinated ledger state;
3. claimant, carrier, sponsor, witness, inspector, archive, or public pressure state;
4. future route acceptance state.

Useful surfaces include route_asset_certification_state, ledger_authority, subordinated_ledger_scar, consent_integrity, refusal_legibility, witness_carrier_burden, claimant_leverage, archive_debt, inspection_heat, sponsor_stop_loss_pressure, contract_capture, public_receipt_distrust, fan_oxygen_resentment, future_route_acceptance, and contradiction_pending.

Missability and recovery

This storyline is missed when a future route accepts a route asset even though multiple ledgers disagree and no certification, subordination, split, freeze, or default was recorded.

Recovery is allowed only with a named scar: reopen consent assignment, review witness discharge, bound the pressure claimant, accept custody crossread, split route use, or freeze the asset for recovery-only substitution.

Non-goals

• Not a governance committee or meta-design page.
• Not a generic ledger-cleanup utility.
• Not a replacement for route asset maintenance, consent debt transfer, witness discharge, pressure claimant conversion, or custody crossread.
• Not valid if a clean asset state can be asserted while contradictory ledgers remain unrecorded.
• Not valid if certification has no cost, scar, or future route restriction.
• Not triggered by fixed turn count or raw content count.