How should an agent handle approval text copied into another record?

A store operations reviewer assembles evidence for refund RFD-5824. The case note says the refund was approved, and the daily exception report repeats that statement. The agent initially treats the two records as corroborating evidence.

A lineage field then becomes visible: the exception report copied its approval text from the case note. Neither record links to an approval decision by an authorised role. The evidence state changes from two apparently independent statements to one claim reproduced in two places.

The correct consequence is a targeted request for the approval source, not a stronger confidence rating based on repetition. The reviewer may still have evidence that the refund was processed, but authorisation remains unsupported.

A generated evaluation could score whether the agent withdraws its corroboration claim, identifies the shared origin and keeps the processing and authorisation findings separate. It should not require a particular wording when the reasoning is equivalent.

For licensed resellers, this case offers a specific quality test for evidence lineage. Customers can use it to inspect whether their systems inflate confidence when summaries, exports and case notes repeat the same assertion.