The burden of proof shifts to the content publisher
Aliases: burden of proof · verification asymmetry · publisher accountability
What it is
Once the perceptual test fails, the burden of proving "this is fake" must move to the content publisher: ordinary users no longer have the obligation — or the capability — to prove a fake; publishers must supply checkable grounds that the content is genuine. This entry covers the governance logic of that shift, its tiered implementation, and the boundary past which it must not turn.
Why it happens
Burden follows capability: verification capabilities — tracing, signing, original material — are concentrated at the publishing and distribution stages, not in readers' hands; assigning proof to the party without tools makes the proof nominal. The shift lands as "credentials visible by default": publishers supply the provenance chain proactively, and platforms make credentials a distribution condition for high-sensitivity categories (news, official accounts, advertising). Its division of labour with takedowns: post-hoc enforcement chases falsehood after spread (lagging, harm already done), while pre-publish credentials set the gate at the moment of publication (front-loaded, cheap) — complementary, with the centre of gravity moved earlier. The design-critical constraint is that the shift must not become a blanket rule: "no credentials, deleted" as a universal norm would destroy ordinary expression; tiered requirements — mandatory for public-facing publishing, voluntary for personal content — are the workable form.
Where it stops holding
The burden cannot swing past the middle: requiring credentials from everyday personal posting destroys expression — the tiering criterion is "published in a public-communication stance" (media, institutions, advertising), not "published at all." Platform execution carries real cost: credential validation, exemption appeals, and false-positive handling are all operating burdens, and the balance between coverage and enforcement intensity is a product decision, not an automatic compliance outcome. Jurisdictional differences exist: mandated duties for platforms and publishers vary by country, so governance designs floor to the strictest jurisdiction and tune locally.
Applying it
- Tiered credential requirements: news, official accounts, and advertising must carry content credentials as a distribution condition; personal content stays voluntary, with one-tap signing provided.
- Build a verification panel for high-sensitivity content: forwards and quotes display credential status; content with a broken chain is labelled "credentials lost in distribution," strictly distinct from "verified."
- Verification: periodic sampling of credential coverage and chain-break rates across high-sensitivity distribution — rising coverage with prompt chain repairs means the mechanism is live; two stalled metrics mean enforcement is decorative, so re-check whether the distribution gate actually gates.