Route conflicting operational reviews without overwriting either result — what should the operator record?
Two reviewers can disagree because they used different artifact revisions, access contexts or schema assumptions. Treat the disagreement as an operational diagnostic rather than a vote on source truth. Preserve both observations long enough to identify the actual mismatch, while keeping restricted evidence out of broad discussion threads.
Preserve checker disagreement and assign a specific resolution question.
Record reviewer_role, artifact_revision, check_name and observed_result separately, preserving time and context without merging incompatible comments. A reviewer seeing blocked-access and another seeing a populated row may both be accurately describing different authorized contexts; preserve context before interpreting the conflict.
Link the resolution to a corrected revision or a documented contract interpretation and leave unsupported factual conclusions outside the operational signoff. The closeout can say mapping corrected in r5 while source claim unreviewed, preserving the boundary between a technical fix and a broader factual endorsement.Capture each observation
Record reviewer_role, artifact_revision, check_name and observed_result separately, preserving time and context without merging incompatible comments. A reviewer seeing blocked-access and another seeing a populated row may both be accurately describing different authorized contexts; preserve context before interpreting the conflict.
Check revision alignment
Confirm both reviewers inspected the same input and output revisions before debating the substantive result of the validation. Even a minor corrected file can change required-field presence, so compare manifest revisions rather than relying on a shared filename or a message saying latest.
Frame the resolution task
Ask a narrow question such as whether null identifiers were excluded by contract, not which reviewer generally understands the evidence better. The resolution question should identify the violated contract and expected behavior, making it possible to choose a decisive artifact instead of debating general confidence.
Review the decisive artifact
Use the authorized receipt, mapping or fixture that actually determines the contract behavior, retaining unresolved access limitations explicitly. If no authorized party can inspect the decisive evidence, keep unresolved as a valid disposition rather than resolving by majority or by the most senior opinion.
Publish the disposition
Link the resolution to a corrected revision or a documented contract interpretation and leave unsupported factual conclusions outside the operational signoff. The closeout can say mapping corrected in r5 while source claim unreviewed, preserving the boundary between a technical fix and a broader factual endorsement.
Keep the boundaries clear.
- Preserve checker disagreement and assign a specific resolution question.
- Operational record: Capture each observation. Context badges do not certify access.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.