24263196: component design generation vs source-qualified MNK / Gen3 RPO context

This page resolves a narrower data-model problem: a component can carry a Gen2 design label while appearing inside a source-qualified MNK / 6T40 Gen3 transmission context. Component design generation and RPO/transmission generation are different dimensions; neither may be copied into the other.

Evidence boundary

B3 E633/E658 + fitment row 9; bounded catalogue contexts only; no universal Gen3 fitment.

FAQ

What does “Gen2” describe?: It describes the 24263196 filter-plate / 2nd-design role in the cited part rows. It must not be rewritten as “the transmission is Gen2”.
Why does MNK create confusion?: RPO tokens are context-sensitive. E658 forbids treating an RPO token as a timeless global generation key.
Does this make 24263196 universal for Gen3 6T40?: No. The fitment remains bounded to specific EPC contexts and does not establish universal same-generation interchangeability.

For a specific vehicle, send the VIN / RPO / known OE so the application can be checked in its own context.

Send OE / VIN