Absence of evidence is not confirmation. Mark missing evidence as unknown, unverified, or blocked.
A claim is only safe when the evidence directly supports that exact claim.
Approved source evidence includes official shopper site pages, existing Agent Hub files, verified source ledgers, supplied internal references, and timestamped evidence approved for the lane.
Routing evidence includes endpoint checks, field checks, destination confirmation, alert logs, test submission logs, screenshots, or platform logs that match the route being claimed.
Downstream confirmation comes from the destination system: CRM, CMS, Google Sheets, Apps Script, webhook logs, email platform, SMS platform, social platform, paid media platform, review platform, or alert channel.
Page loads, draft packets, expected routes, stale screenshots, assumptions, copied URLs, old logs, or unverified notes do not prove downstream completion.
Use unknown when the fact or status is not supplied and has not been checked.
Use unverified when a claim may be possible but evidence is incomplete.
Use blocked when required evidence cannot be collected or policy prevents use.
Use downstream confirmed only when destination-system evidence matches the exact claim.
Last updated: 2026-06-11T11:09:15Z
# Evidence Policy Absence of evidence is not confirmation. Mark missing evidence as unknown, unverified, or blocked. ## Core evidence rule A claim is only safe when the evidence directly supports that exact claim. ## What counts as source evidence Approved source evidence includes official shopper site pages, existing Agent Hub files, verified source ledgers, supplied internal references, and timestamped evidence approved for the lane. ## What counts as routing evidence Routing evidence includes endpoint checks, field checks, destination confirmation, alert logs, test submission logs, screenshots, or platform logs that match the route being claimed. ## What counts as downstream confirmation Downstream confirmation comes from the destination system: CRM, CMS, Google Sheets, Apps Script, webhook logs, email platform, SMS platform, social platform, paid media platform, review platform, or alert channel. ## What does not count as evidence Page loads, draft packets, expected routes, stale screenshots, assumptions, copied URLs, old logs, or unverified notes do not prove downstream completion. ## How to mark unknown Use unknown when the fact or status is not supplied and has not been checked. ## How to mark unverified Use unverified when a claim may be possible but evidence is incomplete. ## How to mark blocked Use blocked when required evidence cannot be collected or policy prevents use. ## How to mark downstream confirmed Use downstream confirmed only when destination-system evidence matches the exact claim. ## Evidence examples by lane - Lead routing: CRM or form routing confirmation. - Inventory: current approved official source evidence. - Review: moderation and approved reuse evidence. - Campaign: platform publish, schedule, or handoff confirmation. - Newsletter: email platform confirmation. - Automation routing: endpoint, field, destination, and alert evidence. Last updated: 2026-06-11T11:09:15Z