Route Crossover Pressure Readback / 路线交叉压力回读线

Route Crossover Pressure Readback is the storyline for the moment when the route matrix’s promised cross-route drama becomes a claim a later route, character gate, forced main, schedule slot, or ending wants to consume.

Route Matrix says the best drama comes from crossings such as company plus intimacy, company plus resistance, liquidation plus resistance, intimacy plus exit, and staging plus resistance. Route Tag Momentum Collision already prevents accumulated route tags from becoming a clean dominant route. This line covers a different seam: a deliberate crossover can still become too clean if the engine records only company_resistance or intimacy_exit without saying which verb, reader, scar, and future route carries each side.

Playable question

When a future reader tries to spend a route crossover, does the producer certify a bounded crossover, split the route verbs, assign a hinge character, convert one side through explicit cost, publish the contradiction, quarantine the crossover claim, spend it with a scar, or let a false crossover default harden?

Every answer must name:

• the source route rows or explicit absence;
• the crossover pair;
• the primary and secondary route verbs;
• the source scar, debt, or reader limit on each side;
• the hinge character, facility, route asset, or explicit absence;
• the reader trying to consume the crossover;
• the selected posture;
• the crossover state after review;
• the future route or reader effect.

State-triggered entry

Open this storyline only when a route crossing is visible and about to be consumed:

entry_state_required:
  trigger_kind: state_pressure
  route_crossover_pair_visible: true
  source_route_rows_min: 2
  primary_route_verb_visible: true
  secondary_route_verb_visible: true
  hinge_surface_visible_or_explicit_absence: true
  future_reader_or_route_consumes_crossover: true
  crossover_scars_visible_or_explicit_absence: true
  player_can_certify_split_hinge_convert_publish_quarantine_spend_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_route_tag_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

The trigger is not a chapter boundary, route affinity total, relationship score, raw tag count, dashboard state, or lens-health state. It is a named route reader trying to consume a visible route crossing.

Bound content pack

• 路线交叉压力回读机制 defines crossover rows, branch states, and false-clean default behavior.
• 路线交叉案卷 records the route rows, crossover pair, verbs, scars, hinge surface, selected posture, and future effect.
• 路线交叉复核 resolves bounded certification, split verbs, hinge assignment, conversion, publication, quarantine, scar spend, or default.
• 虚假路线交叉默认 fires or arms when a crossover becomes clean route permission while one side’s scar, reader scope, or hinge surface is hidden.
• Route Crossover Pressure Readback Lens observes the contract.

Storyline spine

Beat 1 - A crossover claim appears

A schedule slot, character gate, route asset, sponsor package, public table, lawful reader, archive route, forced main, or ending asks for a crossing such as company plus resistance, intimacy plus exit, liquidation plus resistance, staging plus resistance, or company plus intimacy.

The claim might be valuable and true. It is still incomplete until the player can show what each route side contributed and what it cost.

Beat 2 - The docket separates route verbs

Create or refresh Route Crossover Docket. The docket preserves source rows, route families, route verbs, scars, accepted and rejected readers, hinge surface, and the consuming future route.

Beat 3 - The player prices the crossing

Run Route Crossover Review. The player can certify the crossover for one named scope, split verbs by reader, assign a hinge character or asset, convert one route side through cost, publish a contradiction, quarantine the claim, spend it with a scar, or default.

Beat 4 - Future play consumes crossover state

Later play reads crossover_state_after, not a shorthand route label. A company plus resistance route may stay playable, but only if both company capture and resistance exposure remain legible. An intimacy plus exit route may burn hot, but it cannot hide the person who becomes bound, betrayed, or safely absent.

Beat 5 - False crossover becomes durable

If the route crossing is consumed as clean permission, False Route Crossover Default records the false claim, hidden inputs, harmed or omitted reader, state after, future effect, and counter deltas.

Branch map

Branch	Immediate relief	Cost/scar	Future state
Certify bounded crossover	one route crossing becomes usable	losing or excluded reader keeps addendum right	bounded_crossover
Split route verbs	each route side keeps its own reader and cost	route delay and contradiction pressure rise	split_verbs_required
Assign hinge surface	a character, facility, route asset, or proof row carries the crossing	hinge exposure, payroll, capture, or custody cost rises	hinge_required
Convert route side	one side can serve the other through explicit price	conversion debt, relationship scar, or proof burden rises	converted_with_cost
Publish contradiction	public or route reader sees the mismatch	sponsor pressure, lawful heat, or public distrust rises	addendum_required
Quarantine crossover claim	false clean crossing is blocked	route gate stalls or recovery route opens	quarantined_crossover
Spend crossover with scar	the crossing unlocks without pretending clean	ending scar, hostile reader, or route-asset debt travels	spent_with_crossover_scar
False crossover default	fastest clean hybrid route proceeds	hidden side, false consent, or false authority hardens	false_crossover, costlier, recovery_only

No branch may make one crossover clean across company, intimacy, liquidation, resistance, chaos, public, lawful, sponsor, archive, route-asset, and ending readers at once.

Missability and recovery

This storyline is missed when implementation:

• stores only a compound route label;
• lets a crossing inherit route momentum without source rows;
• hides which route side supplied which verb;
• treats a hinge character, facility, proof object, or route asset as flavor;
• lets an intimacy, resistance, company, liquidation, or staging side erase the other side’s scar;
• consumes a crossover from fixed turn, raw route tag count, dashboard state, or lens health.

Recovery requires a visible scar: reopen the docket, split the route verbs, name the hinge surface, convert one side through cost, publish an addendum, quarantine the crossover, spend it with ending scar, or route the claim to recovery-only play.

Non-goals

• Not a route score.
• Not a replacement for Route Tag Momentum Collision.
• Not an ending selector.
• Not a generic relationship route.
• Not valid unless the crossover has source rows, route verbs, hinge state, scars, and future reader effect.