Route Asset Maintenance Triage Storyline / 路线资产维护分诊线

Route Asset Maintenance Triage is a non-character pressure storyline for the stage after the player has already won several useful route assets.

The old win remains true: the witness survived, the public receipt aired, the lawful copy was accepted, the editor cut held, the sponsor package bought relief, the archive docket stayed admissible, the memorial copy became real, or the scarred right remained usable. The new question is whether those assets are still fresh, protected, and trusted enough to carry the next route.

Primary playable question

When multiple earlier victories remain on the table, which route asset does the producer refresh, rotate, freeze, degrade, recover, or cannibalize — and which future route becomes harder because of that choice?

This storyline prevents prior successful custody decisions from becoming clean universal keys. It turns asset uptime into management/RPG pressure without creating a generic upkeep tax.

Gap diagnosis

The current mesh already has strong first-order and aftershock surfaces:

• 播出资产来源后生线 tracks derivative copies after broadcast.
• 受保护证人薪册 tracks person-assets who need support.
• 休眠认领复燃线 brings old rows back when relevant.
• 制作分诊台 allocates finite lanes across active crises.
• 和解反震账本 preserves relief and debt after settlement.

The remaining gap is cross-asset maintenance. The vault can create many route assets, but it still needs a surface that proves two or more prior wins cannot all remain fresh forever. This storyline makes route-asset degradation and recovery replay-visible.

State-triggered entry

Open this storyline when all are true:

1. at least two route assets, proof objects, public receipts, witness rows, editor cuts, sponsor packages, archive dockets, fan ledgers, permits, memorial copies, or scarred rights remain potentially usable;
2. at least one has maintenance pressure: payroll debt, public doubt, lawful expiry, edit ambiguity, sponsor capture, archive opacity, overexposure, false-owner risk, route wear, recovery-only state, or scar restriction;
3. a current or future route would accept, reject, tax, or narrow the asset depending on freshness, custodian, bridge, or degradation;
4. the player can choose a maintenance response;
5. the result can mutate future route availability, cost, claimant posture, or asset state.

No trigger may depend on fixed turn count, arbitrary day count, content count, or dashboard health.

Content pack

Mechanic

• 路线资产维护分诊机制 — defines asset freshness, maintenance pressure, response branches, degradation, recovery, and replay evidence.

Card

• 路线资产维护花名册 — stores asset rows, source provenance, custodian, pressure reason, accepted routes, and default if unmaintained.

Rite

• 路线资产维护分诊 — assignable rite that refreshes, rotates, accepts degraded use, freezes, cannibalizes, or defaults a route asset.

Event

• 路线资产维护违约 — breach/default event when an asset is treated as fresh after maintenance pressure should have mattered.

Primary actors

• Han Yanshuang — lawful refresh, admissibility, seal cost, bureau favor debt.
• Yu Lan — public receipt refresh, fan witness maintenance, exposure cost.
• Baiya — editor checksum refresh, degraded continuity, edit debt.
• Shen Luo — sponsor bridge, managed quiet, contract capture, cannibalized relief.
• Orion Breath — private upkeep money, clean package, ownership capture.

Route asset states

State	Meaning	Required consequence
fresh_asset	Asset is usable with current custodian and route bridge.	Future route accepts it normally until use adds wear.
maintenance_due	Asset needs explicit refresh before clean use.	Triage must offer refresh, rotation, degraded use, freeze, cannibalize, or default.
overexposed_asset	Asset is too visible to use cheaply.	Use raises heat, capture, witness risk, or public/sponsor pressure.
stale_asset	Asset exists but source/custodian/proof is no longer sufficient.	Route rejects or taxes it unless refreshed.
degraded_asset	Asset works only at reduced route quality.	Current route may proceed with scar/default risk.
frozen_asset	Asset is withheld to preserve recovery.	Current route narrows, blocks, delays, or needs substitute.
recovered_asset	Asset is restored with visible scar.	Usable again, but future restrictions remain.
cannibalized_asset	Asset is burned to sustain another.	One route improves; the source route becomes scarred, blocked, or recovery-only.
lost_asset	Asset cannot be used without replacement or terminal appeal.	Future route loses clean path.
false_fresh_asset	Asset is falsely treated as fresh.	A later check must expose contradiction or default.

Branch model

Branch A — Refresh custody

The player assigns Han Yanshuang, Yu Lan, Baiya, Shen Luo, a lawful seal, public receipt, editor checksum, sponsor waiver, fan support, payroll support, archive bridge, or equivalent.

Expected outcomes:

• selected asset becomes fresh_asset, recovered_asset, or safer maintenance_due;
• one risk improves: admissibility, public legitimacy, continuity, custody clarity, route acceptance, or asset recovery cost;
• one cost rises: inspection heat, archive debt, edit debt, handler burden, fan resentment, contract capture, public exposure, or bureau favor debt.

Branch B — Rotate use

The player preserves the pressured asset by using another route asset or weaker bridge.

Expected outcomes:

• preserved asset becomes fresh_asset or frozen_asset;
• substitute asset becomes maintenance_due, overexposed_asset, stale_asset, or degraded_asset;
• future route acceptance now depends on which asset was preserved and which was spent.

Branch C — Accept degraded use

The player uses a stale or degraded asset because the current route cannot wait.

Expected outcomes:

• current route receives partial relief;
• asset becomes degraded_asset, stale_asset, or false_fresh_asset;
• 路线资产维护违约 is armed or fired;
• future route is costlier, narrower, contradiction-pending, or recovery-only.

Branch D — Freeze for recovery

The player blocks current use to preserve the asset for later repair.

Expected outcomes:

• asset becomes frozen_asset or recovery-only;
• current route is blocked, delayed, weakened, or requires alternate asset;
• future recovery bridge is named and scarred.

Branch E — Cannibalize asset

The player burns one route asset to keep another alive.

Expected outcomes:

• target asset becomes fresh_asset or recovered_asset;
• source asset becomes cannibalized_asset, lost_asset, degraded_asset, or scarred;
• harmed claimant is recorded;
• one future route improves while another blocks or becomes costlier.

Branch F — Maintenance default

The player hides the roster, lacks support, treats stale as fresh, or lets a faction select the asset by default.

Expected outcomes:

• 路线资产维护违约 fires or becomes default-ready;
• asset becomes false_fresh_asset, lost_asset, captured_asset, hostile_asset, or degraded_asset;
• future route becomes blocked, hostile, captured, recovery-only, or contradiction-pending.

Counter contract

Every branch must change at least three counters or durable states. One must be relief, one must be cost, and one must change future route acceptance.

Primary surfaces:

• route_asset_freshness
• route_asset_wear
• asset_maintenance_due
• asset_staleness
• asset_recovery_cost
• future_route_acceptance
• custody_clarity
• lawful_admissibility
• public_receipt_legitimacy
• public_receipt_distrust
• inspection_heat
• archive_debt
• edit_debt
• handler_burden
• witness_payroll_due
• sponsor_stop_loss_pressure
• contract_capture
• fan_oxygen_resentment
• false_owner_pressure
• reality_drift

Integration notes

• With Broadcast Asset Provenance Afterlife, this storyline begins after a derivative copy has already survived but now risks staleness or copy-custody drift.
• With Protected Witness Payroll, a paid witness can still become overexposed, stale, hostile, or recovery-only if not maintained as a route asset.
• With Dormant Claim Resurfacing, a resurfaced row can enter this storyline when it is already known but not fresh enough to cite.
• With Broadcast Dividend Claim, a dividend proof can become stale, sponsor-captured, or public-only if not refreshed.
• With Claimant Collision Lock, this storyline handles the afterlife of an asset whose claimant dispute was resolved but not maintained.
• With Ending Scar Ledger, a scarred right may remain usable only if its restriction is refreshed, frozen, or honestly carried.
• With Production Triage Desk, production lanes can still decide whether maintenance is possible, but this storyline is focused on asset freshness rather than crisis staffing.

Replay/session evidence shape

storyline: storyteller.storyline.route_asset_maintenance_triage.v1
session_id: lens-route-asset-maintenance-triage-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  roster_assets_min: 2
  maintenance_due_min: 1
  future_route_depends_on_asset_state: true
  no_fixed_turn_trigger: true
roster:
  card: storyteller.card.route_asset_maintenance_roster.v1
  rows:
    - asset_id: <asset>
      source_surface: <surface>
      source_session_id: <session or explicit_absence>
      asset_state_before: <state>
      custodian: <custodian>
      maintenance_pressure: <pressure>
      accepted_routes: []
      rejected_or_costlier_routes: []
rite:
  id: storyteller.rite.route_asset_maintenance_triage.v1
  selected_asset_row: <row>
  response: refresh_custody | rotate_use | accept_degraded_use | freeze_for_recovery | cannibalize | default_selects
  handler_or_absence: <handler or explicit_absence>
  proof_bridge_or_absence: <bridge or explicit_absence>
  cost_or_scar: <cost or scar>
result:
  asset_state_after: <state>
  other_asset_state_after: <state or explicit_absence>
  event_seen_or_armed: storyteller.event.route_asset_maintenance_default.v1 | none
  future_route_effect: <effect>
  counter_deltas: {}

Missability and recovery

The storyline is missable when the implementation treats every won asset as permanently fresh, hides the roster, leaves unselected assets unchanged, or lets degraded use proceed without future route restriction.

Recovery is allowed only with named scar or bridge:

• refresh lawful proof and accept inspection or bureau cost;
• publish a public receipt and accept sponsor or exposure cost;
• create an editor checksum and accept edit/archive doubt;
• pay witness support and accept payroll/fan pressure;
• freeze the asset and accept current route delay;
• cannibalize another route asset and record the harmed claimant;
• appeal from lost/captured state through replacement or recovery-only route.

Non-goals

• Not a fixed upkeep phase.
• Not an abstract economy tax.
• Not a dashboard governance page.
• Not a replacement for production triage or individual custody/payroll/provenance systems.
• Not valid if degradation has no recovery or loss consequence.
• Not valid if all prior victories remain cleanly usable forever.