Resolving entities only at request time means the same ambiguous pair gets re-evaluated on every query that touches it; maintaining the match set as a standing asset is what makes KPI-G001 (entity match accuracy) improve over time rather than staying flat.
Any match below the confidence threshold set by CON-G05, and any existing confirmed match a later signal contradicts.
Silently overwrite an existing confirmed match — any change must be recorded as a new lifecycle event on the affected Canonical Entity Match, never an in-place edit, per ATT-G023's own retention requirement.
New and updated records from connected systems; existing Canonical Entity Match records; match-confidence signals
New or updated Canonical Entity Match records, each with a recorded confidence and basis