# Proof friction
- Updated: 2026-04-28
- Tags: proof friction
- Canonical: https://archive.citrusgate.com/themes/proof-friction
The buyer still needs concrete proof they can check before the team gets a clean comparison at all.
## Angle
For these selected cases, the useful artifact is a concise review packet that maps product behavior to the buyer's security, legal, and operating questions.
## Diagnostic Questions
- Which trust artifact would unblock the next meeting: security posture, data-use language, approval workflow, or exception handling?
- Does the public product message match the legal and procurement language the buyer will review?
- Who owns human review, override rights, and rollout exceptions?
## Patterns
### In selected cases, AI-enabled workflows intensified permission questions.
When software touched sensitive engineering or operational environments, buyers needed governance proof before treating the product as deployable.
### In selected cases, legal language shaped trust.
Buyers compared public product promises with policy and contract terms before allowing sensitive workflow access.
### In selected cases, data minimization made review easier to understand.
Architectures that reduced data movement or external storage gave security teams a narrower review surface.
## Featured Weekly Memos
## Featured Notes
- Trust proof is deciding before product comparison (https://archive.citrusgate.com/notes/trust-proof-is-deciding-before-product-comparison)