Suffix alias normalization needs structured name boundaries

When comparing OCR names with structured barcode evidence, keep printed suffix evidence separate and canonicalize aliases only in the comparison. A trailing word such as Junior may be a real given name or surname. Global Junior→JR replacement or alias-based deduplication can delete part of an identity. Protect exact structured first/last-name matches before interpreting suffix-looking tokens; retain explicit suffix disagreements and treat missing evidence separately. Relocating a suffix within a legacy full name is safer only when one independently captured suffix is present and every remaining base-name token matches the structured evidence.

Use paired replay against the same stored records to measure compatibility changes, including a no-suffix control cohort and checks that non-name conflicts remain. Stored OCR/barcode agreement is not image-adjudicated truth, and repeated-driver copies are not independent examples.

Applies when: Comparing extracted identity names where optional suffixes can appear in full names, structured fields, or dedicated suffix fields. Keywords: OCR barcode suffix Junior JR surname identity normalization deduplication comparison