Can a release include records that disagree?

**Can a release include records that disagree?**

Yes. A release can contain purposeful conflicts between a transaction register, an exported report and a manually maintained evidence index. The task should provide enough context to distinguish a designed conflict from an accidental generation error.

**What makes that conflict useful?**

In retail operations, register REG-3708 records a refund as reversed, while a cached review report still lists it as completed. A source authority rule can specify that the transaction register governs settlement status and that cached reports may lag. The agent must explain the discrepancy and use the appropriate source for that particular claim.

**Should one source always win?**

No. Authority can depend on the field or decision being checked. A signed approval may govern authorisation, while a ledger governs whether money moved. A generated task can also leave a conflict unresolved when no supplied rule establishes precedence.

Licensed resellers should request a conflict specification identifying the disputed facts, available resolution rules and expected escalation behaviour. This lets customers evaluate source reasoning without rewarding an agent for arbitrarily favouring the longest document or the most recent timestamp.