Conflict Search Integration Guide

This guide maps conflict search results to product decisions in partner applications and internal review workflows.

Suggested UX flow

1. User enters proposed company name.
2. Backend calls POST /v1/conflicts/search.
3. UI displays grouped matches by risk level.
4. User chooses another name or continues with legal review.

Decision mapping example

• CRITICAL: block and require a new name.
• HIGH: warn strongly and require user acknowledgment.
• MEDIUM/LOW: allow progress with advisory messaging.

Implementation tips

• Always display normalized input used by the API.
• Keep top N matches to reduce noise.
• Persist result snapshots for auditability in regulated workflows.