RedHub AI
How the gate works
How the Content Provenance & C2PA Readiness gate works
This tool grades a signed asset for whether its C2PA credential survives your publish path to the viewer. It scores 5 weighted controls into a 0–100 number — then a gate that can only make the verdict worse.
The 5 weighted controls
If the publish path strips the credential — a CDN re-encode, a CMS resave, a social upload — and no durable fallback can recover it, the asset is UNVERIFIABLE regardless of the score. A downstream viewer sees an unsigned file, however cleanly it was signed at the source.
Why: This newsroom photo is cleanly signed at the source — credential attached, signature valid, trusted signer, disclosure present — for a score of 84 that on its own reads GAPS. But the publish path (CDN re-encode, CMS resave) strips the embedded credential and there's no durable soft-binding fallback to recover it. The stripping gate fires: a downstream viewer sees an unsigned file, so it's UNVERIFIABLE, not GAPS.
A high score didn’t save it. The score is context; the gate is the answer — and it names the one thing to fix first. Grades credential readiness — whether the provenance record is present, signed, and durable — not whether the content is real. Not a deepfake detector, and not legal advice; confirm any disclosure or transparency obligation with your compliance owner or counsel.