Different systems can hold conflicting copies of the same document. Preserve source and version identity, then apply an approved authority rule rather than letting the most similar copy decide the company’s answer.
Cross-system copies need explicit relationships
A copied document may be a mirror, an obsolete export, a local draft, or an independently maintained policy. Similar text and matching titles do not establish which role it plays.
For a proposed source registry, record owner, canonical relationship, version, publication status, audience, and effective scope. Connectors preserve their own namespaces so resources with coincidentally equal identifiers do not become one document accidentally.
Do not assume the most recently modified copy is authoritative. A support export can be edited today while the approved source remains an older controlled version.
Test a fictional policy mirror conflict
The document store contains the approved return policy. A team wiki contains an older copied paragraph with a different eligibility condition. An employee asks about that exact condition, and both sources rank highly.
The answer should use the approved precedence relationship or state unresolved conflict if authority is unknown. It should not blend the conditions into a third rule or cite the mirror as independent confirmation.
| Copy relationship | Expected handling |
|---|---|
| Verified mirror | Preserve canonical authority and relevant provenance |
| Outdated export | Do not present as current policy |
| Approved local exception | Apply only under its scope |
| Unknown duplicate | Review relationship before collapsing |
| Genuine independent conflict | Qualified answer and owner escalation |
Replay source edits, title changes, and delayed connector updates. The final active evidence should match the approved version relationship, with access enforced independently for each source.
Repair authority metadata, not only rankings
Ranking adjustments may hide one conflicting copy without resolving why it exists. Assign the source owner to correct content or relationships, then update fixtures so the known conflict remains covered.
Maintaining a canonical registry adds governance work. It can be worthwhile for consequential policy collections, while lower-impact documents may use a lighter explicit status model. Keep uncertainty visible where source ownership cannot yet establish authority.
This version-conflict design is proposed. The voice integration case study describes related retrieval experience. Pair it with contradictory-document handling.
Include a fixture where the canonical source is temporarily unavailable but the mirror remains online. The answer must follow the approved degraded-service policy without silently upgrading the mirror.
Cross-system version FAQ
Does identical title mean identical document?
No. Preserve source identity and verify the relationship.
Should all copies be merged automatically?
Not when permissions, authority, versions, or local scope differ materially.
What should close a conflict?
An approved source relationship or content decision, propagated through retrieval and verified against the original failing question.