| # Context: Logistics Operations — Variant 27 | |
| (Variant for logistics_operations domain) | |
| ## Pattern | |
| When two records have very similar names but different key identifiers | |
| (model numbers, version numbers, specification codes), they should be | |
| treated as distinct entities. | |
| ## Application to Insurance | |
| - Policy with same holder but different coverage dates → different policies | |
| - Same risk type but different deductible → different coverage terms | |
| - Same broker with different registration numbers → different legal entities | |
| ## Exceptions | |
| - Formatting differences only (hyphens, spaces, abbreviations) → same entity | |
| - System-specific prefixes → same entity with different representation | |
| - Historical name changes due to rebranding → same entity | |
| ## Decision Framework | |
| 1. Strip formatting differences | |
| 2. Compare key identifiers (not just name) | |
| 3. If identifiers match → same entity | |
| 4. If identifiers differ → distinct entities | |
| 5. If ambiguous → escalate to domain expert | |