Route Tag Momentum Collision / 路线标签动量撞车线

Route Tag Momentum Collision is the storyline for the moment when several route tags from prior broadcasts, legacy rows, scars, or cycle audits are about to be consumed as one future route direction.

路线矩阵 says routes should emerge from accumulated tags instead of a start-menu faction choice. On-Screen Slot Readback proves one final broadcast’s claimed route tag against visible ritual slot rows. This storyline fills the next seam: the game must not let several scarred route rows collapse into a clean dominant route just because one tag family has the highest count.

Playable question

When a future reader, route, forced main, character gate, deck unlock, or ending tries to consume accumulated route momentum, does the producer bind the dominant route with scope, split incompatible momentum, convert one tag through an explicit cost, quarantine a false momentum claim, spend momentum with a scar, publish an addendum, or let false route momentum default?

The answer must name:

• the source broadcast, legacy, cycle, or explicit-absence rows;
• the route tag on each source row;
• the scope and scar attached to each tag;
• the conflicting route families;
• the dominant route claim;
• the reader or route attempting to consume the momentum;
• the selected posture;
• the momentum state after resolution;
• the future reader, route, or ending effect.

Gap diagnosis

The current corpus covers nearby surfaces:

• On-Screen Slot Readback prevents one aired show from gaining a clean route tag while slots are hidden or invalid.
• Weekly Broadcast Cycle Audit prevents a cycle close from hiding blackouts, license debt, or legacy pressure.
• Ending Scar Ledger keeps final scars from being erased after a result.
• Explicit Absence Register makes missing rows citeable instead of silently absent.

The uncovered seam is route momentum reuse. A run can preserve every individual broadcast row and still let a future route say company wins, resistance opens, or clean chaos ending unlocked from raw tag count. That erases whether the company tags were sponsor-captured, whether resistance tags came from blackout folds, whether liquidation tags injured a future reader, or whether intimacy tags were only lawful, public, or private.

State-triggered entry

Open this storyline only when accumulated route momentum is visible and about to be consumed:

entry_state_required:
  trigger_kind: state_pressure
  accumulated_route_tags_visible: true
  source_broadcast_or_legacy_rows_min: 2
  conflicting_route_families_min: 2
  dominant_route_claim_visible: true
  future_reader_or_route_consumes_momentum: true
  prior_route_tag_scars_visible_or_explicit_absence: true
  player_can_bind_split_convert_quarantine_spend_publish_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

A chapter boundary, ending gate, forced main queue, route deck threshold, or character gate may explain why the review is happening. It cannot be the canonical trigger. The trigger is visible accumulated route momentum that a future reader will consume.

Bound content pack

• 路线标签动量撞车机制 defines how accumulated route rows collide.
• 路线标签动量账本 records source rows, route tags, scopes, scars, dominant claim, conflicting families, selected posture, and future reader effect.
• 路线标签动量复核 resolves bind, split, convert, quarantine, spend, addendum, or default branches.
• 虚假路线动量默认 fires or arms when raw tag count or hidden rows produce a false dominant route.
• Route Tag Momentum Collision Lens observes the implementation contract.

Storyline spine

Beat 1 - Momentum enters review

Two or more source rows are about to become route pressure. A route deck may unlock, an ending reader may ask for route family, a forced main may look for dominant demand, or a character may test whether the player is company, intimacy, liquidation, resistance, chaos, or mixed.

Create or refresh Route Tag Momentum Ledger. It is not a tally sheet. It is the row table proving what kind of route pressure is about to travel.

Beat 2 - Source rows expose scars

Each row must name a source broadcast or legacy surface, route tag, route tag scope, scar or cost, reader that accepted the row, reader that rejected it or explicit absence, and the future claim trying to use it.

Valid route families include:

• company
• intimacy
• liquidation
• resistance
• chaos
• public_only
• lawful_only
• sponsor_captured
• blackout_fold
• recovery_only
• equivalent custom family

Beat 3 - Review prices momentum

Run Route Tag Momentum Review. The player decides whether the route can be bound, split, converted, quarantined, spent with a scar, corrected by addendum, or defaulted.

Beat 4 - Future route consumes a visible state

The future route, character gate, forced main, card pool, or ending must consume momentum_state_after, not a hidden score. A route can become dominant, but only with named scope and cost. Conflicting families can remain playable instead of being rounded away.

Beat 5 - False momentum becomes durable

If the game uses raw tag count, hidden rows, unpriced scars, or a universal winner claim, False Route Momentum Default fires or remains armed. It records the false route claim, hidden or ignored inputs, state after, future reader effect, and at least three counter deltas.

Branch map

Branch	Immediate relief	Cost/scar	Future state
Bind dominant route	route pressure becomes legible	losing family gains reader pressure or addendum right	dominant_bound_with_scope
Split route momentum	incompatible route families remain playable	contradiction pressure and handler burden rise	split_momentum, future reader selects family
Convert route tag	one scarred tag can serve another route claim	conversion cost, proof burden, or relationship debt rises	converted_with_cost, route asset marked
Quarantine false momentum	hidden or sponsor-captured dominance blocked	route delay, recovery-only branch, or public distrust rises	quarantined_false_momentum
Spend momentum with scar	future route unlocks without pretending clean	ending scar, costlier gate, or harmed reader remains named	spent_with_scar
Publish route addendum	conflicting reader gets a durable correction	addendum debt, lawful/public split, or sponsor heat rises	addendum_required, route family narrowed
False route momentum default	fast dominant route may proceed	raw count or hidden row becomes durable contradiction	false_dominant, sponsor_captured, hostile_split, recovery

No branch may turn hidden source rows or unpriced route scars into universal clean momentum.

Integration notes

• With on-screen-slot-readback, a route tag that passed one broadcast readback can still collide with tags from other broadcasts later.
• With weekly-broadcast-cycle-audit, cycle legacy rows can supply route momentum only if the consuming reader sees the audit state.
• With route-matrix, route families are pressures with verbs and costs, not pure faction labels.
• With ending-scar-ledger, any spent scar must remain citeable by ending readers.
• With explicit-absence-register, a missing source row can be explicit only if it weakens, narrows, delays, or defaults the momentum claim.

Missability and recovery

This storyline is missed when implementation:

• selects the dominant route from a raw route tag count;
• hides the source broadcast or legacy rows behind a single route score;
• treats sponsor-captured, public-only, lawful-only, blackout-folded, or recovery-only rows as universal route proof;
• consumes a route tag without preserving scar, reader scope, or rejection;
• lets a future route, character, forced main, card pool, or ending unlock without momentum_state_after;
• creates no harmed reader, addendum right, scar, or default when conflicting route families collide.

Recovery requires visible scar: reopen the momentum ledger, split route momentum, convert a tag with cost, quarantine false dominance, publish route addendum, spend with ending scar, or route to recovery-only state.

Replay evidence expectation

storyline_id: storyteller.storyline.route_tag_momentum_collision.v1
session_id: lens-route-tag-momentum-collision-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  accumulated_route_tags_visible: true
  source_broadcast_or_legacy_rows_min: 2
  conflicting_route_families_min: 2
  future_reader_or_route_consumes_momentum: true
  no_fixed_turn_trigger: true
offered:
  card: storyteller.card.route_tag_momentum_ledger.v1
  rite: storyteller.rite.route_tag_momentum_review.v1
branch_result:
  selected_posture: bind_dominant_route | split_route_momentum | convert_route_tag | quarantine_false_momentum | spend_momentum_with_scar | publish_route_addendum | false_route_momentum_default
  momentum_state_after: <state>
  future_reader_or_route_effect: <effect>
  event_seen_or_armed: storyteller.event.false_route_momentum_default.v1 | none
  counter_deltas:
    relief: []
    cost: []
    future: []

Non-goals

• Not a replacement for final-air slot readback.
• Not a weekly cycle audit duplicate.
• Not a pure route score or faction picker.
• Not valid if a route unlocks from raw tag count without source rows, scars, conflicting families, and future reader effect.