Route Asset Maintenance Default / 路线资产维护违约

Route Asset Maintenance Default is the breach event for a route asset that was treated as usable after its maintenance pressure should have mattered.

It fires or becomes armed when 路线资产维护花名册 is hidden, under-supported, falsely cleared, or resolved without changing future route acceptance. It is the event surface for 路线资产维护分诊机制 and 路线资产维护分诊.

Event promise

The event is not a punishment popup. It names which prior asset stopped being trustworthy, who claimed or damaged it, and which future route now rejects, taxes, or recovers it.

A valid event must show:

• source route asset;
• maintenance pressure that was ignored or mishandled;
• default actor;
• asset state mutation;
• future route effect;
• recovery path or terminal loss;
• at least three counter/state deltas.

Fire or arm condition

Fire immediately, or arm as the next relevant route check, when any condition is true:

1. an asset in maintenance_due, overexposed_asset, stale_asset, degraded_asset, frozen_asset, recovery_only_asset, or false_fresh_asset is used as if it were fresh;
2. the player opens maintenance triage but assigns no credible handler, proof bridge, cost, substitute, or scar;
3. a stale public receipt, lawful copy, editor cut, sponsor package, witness row, fan ledger, archive docket, permit, memorial copy, or scarred right is cited by a route that requires freshness;
4. an unselected asset from the roster should degrade but remains unchanged;
5. one faction can plausibly default-select the asset because production did not maintain it.

This event must not fire from fixed numbered timing.

Default actors

Default actor	Event meaning	Typical consequence
archive_default	Archive treats stale proof as inadmissible or seals it privately.	Lawful route narrows; archive debt or inspection heat rises.
inspector_default	Inspector requires fresh chain or rejects the asset.	Custody clarity may improve; schedule, bureau debt, or admissibility cost rises.
sponsor_default	Sponsor supplies a clean private version.	Immediate relief may improve; contract capture and public distrust rise.
fan_public_default	Public keeps using the asset without production control.	Legitimacy may rise; fan resentment, exposure, or sponsor pressure rises.
editor_default	Cutroom auto-patches around the stale asset.	Continuity improves; edit debt, source ambiguity, or reality drift rises.
claimant_default	Rival claimant narrates the asset first.	False-owner pressure or hostile route state hardens.
route_asset_default	The asset itself fails, leaks, refuses, or goes silent.	Future use becomes blocked, hostile, captured, or recovery-only.

Event branches

Branch A — False freshness exposed

The asset looked usable until a route checked it.

event_branch: false_freshness_exposed
asset_state_before: false_fresh_asset | stale_asset | degraded_asset
asset_state_after: degraded_asset | lost_asset | recovery_only_asset | captured_asset
future_route_effect: rejected | costlier | contradiction_pending | recovery_only

Branch B — Rival default selects asset

Another faction uses the maintenance gap to claim the asset.

event_branch: rival_default_selects
asset_state_after: captured_asset | hostile_asset | false_owner_hardened | sponsor_package_captured | lawful_copy_narrowed
claimant_pressure_up: true
future_route_effect: blocked_or_requires_recovery

Branch C — Emergency degraded use

The show still uses the asset, but only at reduced quality.

event_branch: emergency_degraded_use
current_relief: partial
asset_state_after: degraded_asset | scarred_route_asset
future_route_effect: costlier_or_narrower
armed_followup: true

Branch D — Recovery-only freeze

The event forces the asset out of clean use before it is destroyed.

event_branch: recovery_only_freeze
asset_state_after: frozen_asset | recovery_only_asset
current_route_effect: blocked | delayed | alternate_required
recovery_bridge_required: true

Branch E — Asset loss

The maintenance gap consumes the asset.

event_branch: asset_loss
asset_state_after: lost_asset | cannibalized_asset | terminal_scar
future_route_effect: removed | replacement_required | appeal_required

Counter contract

Every fired branch must mutate at least three counters or durable states. At least one can be short relief, but at least one must be future cost or route restriction.

Primary deltas:

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

Event record shape

event: storyteller.event.route_asset_maintenance_default.v1
source_roster: storyteller.card.route_asset_maintenance_roster.v1
source_rite: storyteller.rite.route_asset_maintenance_triage.v1 | explicit_absence
asset:
  asset_id: <stable asset>
  source_surface: <surface>
  asset_state_before: <state>
  maintenance_pressure: <pressure>
  intended_use: <route or rite>
default:
  actor: archive_default | inspector_default | sponsor_default | fan_public_default | editor_default | claimant_default | route_asset_default
  reason: false_freshness | missing_handler | missing_bridge | no_cost | wrong_substitute | hidden_roster | unselected_asset_unchanged
result:
  event_branch: false_freshness_exposed | rival_default_selects | emergency_degraded_use | recovery_only_freeze | asset_loss
  asset_state_after: <state>
  future_route_effect: <effect>
  recovery_available: true | false
  counter_deltas: {}

Integration notes

• With 来源分岔再浮现, this event can expose that the cited copy was stale.
• With 休眠认领破口, this event can be the asset-level consequence of a resurfaced row being ignored.
• With 证人薪册泄露, this event can convert person-maintenance failure into broader route-asset degradation.
• With 盈余认领默认, this event can mark the dividend proof asset as captured, stale, or recovery-only.

Non-goals

• Not a generic failure scene.
• Not a fixed-delay timer.
• Not valid if the asset state remains unchanged.
• Not valid if the event lacks future route effect.
• Not valid if all recovery and loss branches collapse into the same outcome.