Require distinct role provenance instead of two audit paths

When completion requires audits from distinct roles, different filenames are insufficient: duplicated or merged receipts can make one producer appear to satisfy both checks. Validate each receipt against its assigned role, observer source and registration, require distinct role-specific content, and bind the referenced material before admitting analysis. Include duplicate-content and merged-role counterexamples at different paths. This prevents the exercised evidence substitution, but declared origins and hashes still establish consistency rather than authenticated authorship or independent reasoning. Keep semantic correctness and producer independence as separate claims.

Applies when: A software evaluation or release gate requires multiple independently scoped audit receipts. Keywords: audit provenance role receipt duplicate merged source registration integrity evidence