What this capability changes
Normalisation preserves raw records and maps notices to a common schema without overwriting source wording.
Every important field should be traceable to a source, transformation and observation time. The design starts with a commercial question and preserves the trail back to the authoritative record, instead of forcing a team to trust a relevance label it cannot inspect.
How it works in the platform
Dedupe uses identifiers first, then transparent title, buyer, date and value comparisons with reversible merge decisions.
Source identity, observation time, transformations and user decisions remain separate fields. That distinction allows the product to update a notice without erasing what a user saw when a pursuit decision was made.
Production controls
Derived renewal, match and company signals carry confidence and explanation rather than masquerading as source facts.
Deployment begins with a source register, access roles, retention rules and measurable acceptance criteria. Features that depend on customer systems or third-party rights remain disabled until those dependencies are approved.