Route Loadout Reconciliation / 路线装配对表
Route Loadout Reconciliation is the assignable rite for deciding whether a multi-asset route bundle can proceed, must be swapped, must be narrowed, must be split, must be quarantined, or defaults into false compatibility.
The rite is used only after 路线装配清单 records a requested route or rite with at least two asset slots and at least one compatibility risk.
Entry requirements
entry_required:
trigger_kind: state_pressure
manifest_row_present: true
requested_route_or_rite_present: true
required_asset_slots_min: 2
asset_states_visible_or_explicit_absence: true
compatibility_conflict_present: true
harmed_reader_or_claimant_visible_or_explicit_absence: true
future_route_or_reader_consumes_loadout_state: true
no_fixed_turn_trigger: true
no_fixed_day_or_week_trigger: true
no_raw_asset_count_trigger: trueThe rite is invalid if it opens from a fixed sequence, a raw unlocked-asset count, an inventory screen, or a generic readiness check.
Assignment slots
A valid action must fill every slot or record explicit absence:
assignment_required:
manifest: storyteller.card.route_loadout_manifest.v1
selected_row_id: <row id>
requested_route_or_rite: <route rite slot correction recovery lane public table lawful bridge sponsor package or equivalent>
future_reader: <reader>
asset_slots:
- slot_id: <slot>
candidate_asset: <asset or explicit_absence>
asset_state_before: <state>
custodian_or_absence: <custodian or explicit_absence>
accepted_scope: <scope or explicit_absence>
conflicting_slots: [<slot ids>]
conflict_kind: reader_scope_mismatch | custody_owner_mismatch | proof_truth_mismatch | checksum_vs_archive | sponsor_vs_public | lawful_vs_artist_boundary | witness_protection_vs_publicity | carrier_capacity_mismatch | stale_asset_loaded_as_fresh | false_owner_loadout | equivalent
harmed_reader_or_claimant: <reader claimant or explicit_absence>
selected_posture: reconcile_with_scope | swap_asset | narrow_route_use | split_loadout | quarantine_combination | sacrifice_slot | allow_incompatible_default
handler_or_absence: <handler or explicit_absence>
proof_bridge_or_absence: <proof bridge or explicit_absence>
cost_or_scar_or_absence: <cost scar or explicit_absence>
future_route_effect: <effect>No famous handler, sponsor payment, legal seal, editor checksum, or public outrage may resolve the loadout without filling the conflict, harmed-reader, bridge, and future-effect slots.
Branch families
Reconcile with scope
The bundle proceeds only with named boundaries.
selected_posture: reconcile_with_scope
loadout_state_after: compatible_with_scope
relief_any:
- route_access_unlocked
- proof_bundle_legible
- custody_conflict_contained
cost_any:
- handler_burden_up
- inspection_heat_up
- public_receipt_distrust_up
- sponsor_stop_loss_pressure_up
future_effect_any:
- accepted_with_scope
- bridge_required
- reader_scope_requiredSwap asset
One slot is replaced. The old asset does not vanish; it becomes unused, stale, recovery-only, or owed an explanation.
selected_posture: swap_asset
loadout_state_after: substituted
relief_any:
- incompatibility_down
- route_access_unlocked
- false_clean_bundle_blocked
cost_any:
- substitute_wear_up
- old_asset_resentment_or_staleness_up
- route_asset_pressure_up
future_effect_any:
- costlier
- substitute_required
- old_asset_recovery_or_notice_requiredNarrow route use
The route proceeds for fewer readers, fewer claims, or a narrower proof use.
selected_posture: narrow_route_use
loadout_state_after: narrowed
relief_any:
- one_reader_route_opens
- contradiction_risk_down
cost_any:
- excluded_reader_resentment_up
- sponsor_or_public_claim_narrowed
- future_reconciliation_cost_up
future_effect_any:
- public_only
- lawful_only
- sponsor_only
- route_costlierSplit loadout
The route is separated into two or more bundles.
selected_posture: split_loadout
loadout_state_after: split_required
relief_any:
- incompatible_readers_can_proceed_separately
- private_capture_down
cost_any:
- schedule_pressure_up
- source_ambiguity_up
- carrier_burden_up
future_effect_any:
- split_required
- reconciliation_requiredQuarantine combination
The player blocks clean use until a bridge exists.
selected_posture: quarantine_combination
loadout_state_after: quarantined
relief_any:
- false_compatible_use_down
- archive_fraud_down
- broadcast_reality_drift_down
cost_any:
- route_delay_up
- sponsor_stop_loss_pressure_up
- fan_oxygen_resentment_up
future_effect_any:
- bridge_required
- recovery_only
- blocked_until_manifest_updateSacrifice slot
The player burns one asset slot to keep a higher-value route alive.
selected_posture: sacrifice_slot
loadout_state_after: slot_sacrificed
relief_any:
- higher_value_route_survives
- immediate_pressure_down
cost_any:
- sacrificed_asset_lost_or_hostile
- claimant_retaliation_up
- route_asset_integrity_down
future_effect_any:
- costlier
- recovery_only_for_sacrificed_asset
- hostile_claim_armedAllow incompatible default
The fastest desk, claimant, or system files the bundle as compatible.
selected_posture: allow_incompatible_default
loadout_state_after: false_compatible | captured | blocked | recovery_only
emits_or_arms: storyteller.event.incompatible_loadout_default.v1
cost_any:
- false_clean_bundle_up
- public_receipt_distrust_up
- reality_drift_up
future_effect_any:
- hostile
- captured
- blocked
- recovery_only
- contradiction_pendingCounter contract
Every non-default branch must mutate at least three durable surfaces: one relief, one cost, and one future route effect.
Suggested counters and states:
loadout_integrityroute_asset_integrityasset_slot_pressurecompatibility_conflicthandler_burdencarrier_burdeninspection_heatsponsor_stop_loss_pressurefan_oxygen_resentmentpublic_receipt_legitimacypublic_receipt_distrustarchive_debtedit_debtsource_ambiguitybroadcast_reality_driftfuture_route_acceptancerecovery_route_cost
Replay evidence
rite_evidence:
rite: storyteller.rite.route_loadout_reconciliation.v1
session_id: <session>
seed: <seed>
manifest_row: <row>
selected_posture: <posture>
assigned_slots: []
conflict_kind: <kind>
harmed_reader_or_claimant: <reader claimant or explicit_absence>
handler_or_absence: <handler or explicit_absence>
proof_bridge_or_absence: <bridge or explicit_absence>
loadout_state_after: <state>
future_route_effect: <effect>
counter_deltas:
relief: []
cost: []
future: []Invalid shortcuts
The rite fails if any branch treats individually valid assets as mutually compatible without scope, proof bridge, harmed-reader visibility, and future route mutation.