What reconciliation means
The question is whether two source observations describe the same business agent. A deployment, runtime resource or shared technical reference is evidence to review; it is not automatically the complete business identity. Start with the source-qualified ID and scope, then check purpose and ownership with the responsible team.
A deliberate review
- Open Human review and inspect the pair. Source names, IDs, record types, scopes, reported owners, business owners and last-observed state are shown separately.
- Read why the pair was suggested and what differs. Similar names are never sufficient by themselves.
- Choose a decision explicitly. For Link records, choose one source identity to move and the existing destination record from the pair.
- Supply a reason that another reviewer can understand. Recheck the destination owner and purpose before confirming.
The three decisions
| Decision | Effect |
|---|---|
| Link records | Moves exactly one selected observation binding; both business records and their decisions remain. |
| Keep separate | Remembers that the current pair and selected evidence should remain distinct. |
| Defer | Remembers that the pair needs later review. No timer silently reopens it. |
Correct a link
Use Decision history → Reverse link. Give a reason. Reverse returns the moved identity to its previous business record only if the exact binding revision still matches. If someone moved the identity away and back, old undo is blocked. Review the current binding instead. Split into a separate agent is different: it creates a new unreviewed record without copying the old business owner.
When a confirmation is blocked
Reload the pair if evidence, the previous decision, or destination decisions changed. A missing, stale, paused or unhealthy source prevents guided linking. Keep separate and Defer remain available. Release 708b5af additionally blocks guided links involving retired business records and displays the exact server reason.