← Use cases · Provenance pipelines
Detection signals where provenance runs out
Provenance is strong when producers cooperate. dfpn picks up exactly where a signed manifest is missing.
The problem
Provenance standards like C2PA and camera-SDK vendors like Truepic prove where cooperating media came from. But most content in the wild arrives without a manifest. A provenance-first pipeline has nothing to verify against for that content — and that is the majority of it.
Where dfpn fits
- ▸You already run C2PA verification or a capture-time provenance vendor
- ▸You need a detection answer for content that arrives unsigned
- ▸You want detection that does not depend on every camera implementing a standard
- ▸You want an open audit trail alongside your provenance records
How the flow works
- 01
Check provenance
Verify the C2PA manifest or vendor signature first, where one exists.
- 02
Fall through to dfpn
For unsigned content, submit the hash to dfpn and get a consensus detection verdict.
- 03
Combine
Store provenance results and detection verdicts side by side — origin where you have it, detection where you do not.
Honest caveat
dfpn does not replace provenance and does not produce or verify C2PA manifests. It is the complementary detection layer. See the C2PA and Truepic comparisons for exactly where each fits.
Other use cases
Put it to work
Wire verdicts into your pipeline, or read how a verdict is produced end to end.