Storyteller Wiki

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

4 min read

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

This lens observes whether 路线资产债务对账会 makes cross-ledger contradiction playable before a route asset unlocks another route.

The observed mesh already has Route Asset Maintenance Triage, Consent Debt Transfer, Witness Carrier Discharge, Pressure Claimant Conversion Chain, and Custody Oracle Crossread. This lens checks the bridge between them: one asset must not become cleanly usable while its ledgers disagree.

This lens observes:

It is observed through:

Observable promise

When two or more ledgers disagree about the same route asset, the game must ask: which reading certifies the asset, which reading is subordinated, and what scar does the future route read?

A pass cannot be achieved by an inventory flag, a clean asset_available result, or prose-only contradiction.

Must pass

1. Entry is 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
  no_fixed_turn_trigger: true

The lens fails if eligibility is fixed turn count, chapter count, calendar delay, lens health, or raw page count.

2. Ledger claims are visible

A board row must show at least two claims against the same route asset. Valid ledger families are maintenance or freshness, consent debt carrier, witness discharge, pressure claimant control, custody crossread, or equivalent route-asset ledger.

Each claim must show source surface, reading, proof or absence, and cost if certified or subordinated.

3. Conflict kind is named

The implementation must name the conflict kind: double certification, stale-but-released, consent unpaid but asset fresh, claimant gate with route open, custody crossread split, or equivalent.

The lens fails if the asset simply becomes usable without a named contradiction.

4. Certification branches diverge

At least four branch families must be playable or explicitly blocked by state:

  • certify maintenance ledger;
  • certify consent ledger;
  • certify witness discharge;
  • certify claimant control;
  • split certification;
  • refuse certification;
  • default certification.

Each branch must change asset state, ledger authority, pressure state, and future route effect differently.

5. Subordinated ledger scar is recorded

Whenever one ledger becomes authoritative, at least one other ledger must be subordinated or explicitly absent.

subordinated_ledger:
  ledger: <ledger or explicit_absence>
  state_before: <state or explicit_absence>
  state_after: subordinated | scarred | contradiction_pending | recovery_only | explicit_absence
  scar_or_cost: <cost or explicit_absence>

The lens fails if certification erases the losing ledger.

6. Future route reads the certification result

At least one later route, rite, or event must read the certification outcome.

future_route_acceptance_check:
  route_or_rite: <id>
  certified_ledger_required_or_blocked: <ledger or state>
  accepted_states: []
  rejected_or_costlier_states: []
  route_effect_after_branch: unlocked_with_scar | costlier | delayed | lawful_only | public_only | sponsor_gate_required | recovery_only | blocked | contradiction_pending

The lens fails if certified, split, frozen, and default outcomes all produce the same future route behavior.

7. Recovery requires named scar

The story may recover a route asset only by naming the scar: reopened consent assignment, reviewed witness release, bounded claimant gate, custody crossread cost, split route use, or recovery-only substitution.

Replay evidence expectation

lens_id: storyteller.lens.route_asset_debt_reconciliation_board.v1
entry_state:
  trigger_kind: state_pressure
  route_asset_row_exists: true
  ledger_claims_min: 2
  conflicting_ledger_reading_present: true
  no_fixed_turn_trigger: true
selected_branch:
  response: certify_maintenance | certify_consent | certify_witness_discharge | certify_claimant_control | split_certification | refuse_certification | default_certification
  authoritative_ledger: <ledger or explicit_absence>
  subordinated_ledger: <ledger or explicit_absence>
  cost_or_scar: <cost or scar>
result:
  route_asset_state_after: <state>
  ledger_state_after: <state>
  pressure_state_after: <state>
  future_route_effect: <effect>

Progress metric

  • 20%: board opens from state pressure with one route asset and at least two ledger claims.
  • 40%: conflict kind and future route risk are named.
  • 60%: certification branch chooses authoritative and subordinated ledger.
  • 80%: branch result mutates asset state, ledger authority, pressure state, and future route effect.
  • 100%: replay evidence proves one certified branch and one split/refuse/default branch without fixed turn trigger.

Non-goals

  • Not a meta-governance lens.
  • Not a new generic debt meter.
  • Not a replacement for maintenance, consent, witness, claimant, or custody crossread lenses.
  • Not valid if certification deletes the losing ledger.
  • Not valid if contradictory route assets can unlock clean future routes.

Graph View