Pin product-label mappings before freezing a cohort

A database terminal code and a product-facing outcome label are not interchangeable just because they sound similar. Before eligibility is frozen, bind every semantic mapping to the deployed source revision, exact field path, and a versioned mapping digest; record both the raw code and derived label in the manifest. If the mapping cannot be independently recovered, withhold that class rather than silently substituting a neighboring field such as a caller-disposition enum. This prevents a valid operational status from being scored as the wrong ground-truth outcome.

Applies when: operational events are converted into training or heldout evaluation cohorts. Keywords: outcome mapping terminal status cohort provenance validation receipt deployed code