False Route Crossover Default / 虚假路线交叉默认

False Route Crossover Default fires or arms when a future route consumes a route crossing as clean hybrid permission while source rows, route verbs, scars, hinge state, harmed reader, or future effect are hidden.

Fire when

fire_when:
  route_crossover_docket_present: false
  false_crossover_claim: true
  future_reader_or_route_consumes_crossover: true
  hidden_or_flattened_inputs:
    - source_route_rows
    - primary_route_verb
    - secondary_route_verb
    - hinge_surface_or_explicit_absence
    - crossover_scars
    - harmed_or_deferred_reader
    - future_reader_or_route_effect

Payload

false_route_crossover_default:
  false_crossover_claim: company_resistance_clean | intimacy_exit_clean | company_intimacy_clean | liquidation_resistance_clean | staging_resistance_clean | hybrid_route_clean | equivalent
  hidden_or_flattened_inputs:
    - source_route_rows_absent
    - route_verbs_collapsed
    - hinge_surface_hidden
    - scar_or_cost_hidden
    - harmed_reader_hidden
    - future_effect_hidden
  capturing_reader: producer | sponsor | public_table | lawful_desk | archive | route_asset_holder | ending_reader | broadcast_reality | equivalent
  harmed_or_omitted_reader: public | lawful | sponsor | archive | character | route_asset | ending | explicit_absence | equivalent
  crossover_state_after: false_crossover | false_consent | false_authority | sponsor_captured | contradiction_pending | recovery_only | equivalent
  future_reader_effect: addendum_required | split_required | route_costlier | hostile_reader | blocked | ending_scar_required | recovery_only
  counter_deltas_min: 3
  durable_mutation: true

Common failures

• a company plus resistance route hides who can betray whom;
• an intimacy plus exit route treats bound affection as clean departure;
• a liquidation plus resistance route makes public trial erase the reader harmed by cleansing;
• a staging plus resistance route treats a safehouse as both commodity and refuge without split scope;
• a clean hybrid ending ignores the hinge surface that made the crossing possible.

Recovery

Recovery requires one of:

• reopen Route Crossover Docket;
• run Route Crossover Review;
• split route verbs;
• name or protect the hinge surface;
• publish a contradiction addendum;
• quarantine the crossover claim;
• spend the route crossing with scar;
• route the claim to recovery-only play.

Non-goals

• Not flavor for route drama.
• Not valid unless false_crossover_claim, hidden_or_flattened_inputs, crossover_state_after, future_reader_effect, and counter_deltas_min are recorded.