Source Poisoning and Trust
Poisoned documents may contain false information or misleading metadata. Verify source identity, ownership, publication status, and provenance. Keep model-generated summaries untrusted unless reviewed. Monitor unusual changes and preserve source lineage. For critical corpora, use approval workflows and rollback.
Implementation example
{
"sourceId":"policy-v4",
"origin":"approved-policy-repository",
"ownerVerified":true,
"publicationStatus":"approved",
"contentHash":"sha256:..."
}💡 Trust metadata must come from trusted systems and processes, not model claims.
Key Takeaways
- Inspect the relevant pipeline stage instead of guessing.
- Preserve source provenance, versions, and access scope.
- Measure quality on representative queries.
Knowledge Check
What is a key defense against poisoned sources?