# V2 Racing Ecosystem Bridge

`@v2/racing-ecosystem-bridge` is the cook-time composition surface for the V2
racing component (§96-119). It binds:

- Galatea `@galatea/kinematics` and `@galatea/whole-body-control` for
  vehicle-as-articulated-body driver/ragdoll probes.
- Saraswati `@saraswati/ev` for hybrid and electric vehicle powertrain
  selection, gear ratios, regeneration, thermal assumptions, and efficiency.
- Maya `@maya/genesis-terrain` and `@maya/genesis-urban` for deterministic track
  terrain, road topology, city districts, and open-world traversal readiness.

The bridge emits authoring manifests for `V2Vehicles`, `V2RacePhysics`, and
`V2RaceTracks`. It is off rollback, rejects live race-frame RPCs, and may not
influence deterministic match/race simulation after the cook manifest is
published.

## Section 96 Product Integration

The section 96 overview is `V2/docs/racing/racing-overview-integration.md`, with
launch scope pinned in `V2/balance/racing/racing-launch-scope.json`. Racing and
fighting share roster, online backbone, cosmetic shop, Battle Pass, profile,
match history, and currency ledger while keeping ranked, mastery, and
progression stats split by genre. The main menu mode-pivot contract exposes
Fighting Modes Hub, Racing Modes Hub, and Mixed Hub for crossover modes.

CI ownership is enforced by `V2/ue/Tools/check-v2-racing-ecosystem-bridge.py`.
The checker verifies the package wiring, reciprocal Galatea and Saraswati spec
sections, Maya package references, V2 architecture/dependency docs, and workflow
presence.