INQUIRING LINE

Slapping an 'AI was used' label on something is easy — so why does it rarely prove who actually did the work?

How does disclosure of AI use differ from proof of who did the work?

This explores the gap between telling people AI was involved (a label or statement) and actually establishing who did what work (verifiable evidence of authorship), and why the first rarely delivers the second.


This explores the gap between saying "AI was involved" and being able to show who actually did the work. The corpus suggests these are almost separate problems, and disclosure is the weaker one. A disclosure is a claim made by someone. Proof is something a reader or a system can check. Most of the research here shows that claims about AI involvement change less than you'd expect.

Start with what disclosure does to readers. Telling an audience that AI wrote something makes them more critical, but 34-62% were still persuaded (Does telling people an AI wrote something actually stop them from believing it?). A label about identity can also do close to nothing. In a 1,500-person experiment, an "this is an AI" label didn't change persuasion at all, probably because people had already guessed from the chatbot's style. Disclosing the chatbot's persuasive intent and instructions cut persuasion roughly in half (Does telling people they are talking to AI change how persuaded they become?). So the useful disclosure describes what the AI was asked to do, and says nothing about the fact that it's an AI. Even a disclosure that has an effect can be unstable: people's initial bias against an AI partner fades only after they see repeated outcomes, and disclosure without that feedback produces no calibration (Does revealing AI identity help or hurt user trust?).

Proof of authorship faces a different obstacle: the people making the claims often can't say who did the work. Users declare authorship of AI-assisted output without feeling cognitive ownership of it. This isn't dishonesty. The intermediate steps are opaque, and people build the story of what they did after the fact (Do users truly own the AI-generated content they produce?). It also feeds a self-assessment error: fluent, seamless output leads people to count AI-produced results as evidence of their own skill (Do AI-assisted outputs fool users about their own skills?). A sincere "I wrote this, and AI helped a bit" can be wrong without anyone lying. Self-report is a shaky base for either disclosure or proof.

The corpus points to three approaches that skip self-report and look at evidence. One is process data. AI contributions in writing and programming arrive in concentrated bursts outside an author's normal rhythm, which flags wholesale delegation reliably. The same signal can't tell ordinary collaboration from minimally assisted work (Can process data distinguish AI delegation from ordinary collaboration?). That is a real limit: it can detect handing off the whole task but not who contributed which ideas. A second is provenance built into the artifact. Data2Story binds every number, quote and asset to its origin, so a newsroom can audit the work instead of trusting a label (Can source traceability make AI writing trustworthy?). That proves where claims came from, which is a different question from who typed them. A third is shared visibility. Paired writers preferred editors that showed each other's prompting activity, which let them see when and where AI was used and check the text, though some found full sharing intrusive (Do writers want to see each other's AI prompts in shared editors?).

The stakes show up in institutions. An audit of 30 universities found policies that clearly say which AI uses are allowed but rarely say what evidence shows a credential still certifies learning (Do university AI policies actually protect what credentials mean?). That is disclosure-style thinking (declare and permit) applied where proof is what matters. The pattern across the notes is that disclosure tells readers to be wary, and proof gives them something to check. Readers who tend to accept fluent output without checking (When do users stop checking whether AI output is actually backed?) will not act on a warning alone, so they're the ones who most need the checkable evidence. The corpus has no note that ties the two together, for example one that tests whether process evidence changes how readers judge authorship.


Sources 10 notes

Does telling people an AI wrote something actually stop them from believing it?

Audiences aware of AI involvement became more critical and scrutinizing, yet 34–62% across groups remained persuaded. Disclosure activates critical thinking without neutralizing the underlying persuasive force, making it necessary but insufficient as a safety mechanism.

Does telling people they are talking to AI change how persuaded they become?

In a preregistered experiment with 1,500 UK adults, an AI-identity label produced no measurable change in persuasion, while disclosing the chatbot's persuasive intent and instructions cut persuasion roughly in half. Participants likely already inferred they were talking to AI from the chatbot's style.

Does revealing AI identity help or hurt user trust?

Users initially avoid AI partners when identity is revealed, but this preference reverses after repeated interactions with visible results. The learning mechanism—observing consistent outcomes—is essential; disclosure without feedback produces no calibration.

Do users truly own the AI-generated content they produce?

Research shows users declare authorship at a social level while lacking genuine cognitive ownership of AI-generated content. This dissociation arises from opaque intermediate steps and post-hoc narrative construction, not dishonesty, and leads to inflated self-assessments of independent competence.

Do AI-assisted outputs fool users about their own skills?

Research identifies a systematic cognitive attribution error where individuals integrate AI-generated outputs into their capability identity, believing they possess skills they don't actually have. This occurs when task output is seamless and fluent, obscuring the human-AI boundary.

Show all 10 sources
Can process data distinguish AI delegation from ordinary collaboration?

Analysis of writing and programming corpora shows AI contributions arrive in concentrated bursts outside authors' baseline rhythms, creating a categorical signature for wholesale delegation while leaving collaborative assistance indistinguishable from minimally assisted work.

Can source traceability make AI writing trustworthy?

Data2Story's Inspector binds every number, quote, and asset to its origin, making provenance rather than fluency the adoption gate. Across 18 samples, human raters favored this approach, showing that verifiable derivation—not surface polish—enables professional newsrooms to adopt agent output.

Do writers want to see each other's AI prompts in shared editors?

Sixteen paired writers showed strong preference for higher levels of prompt visibility in shared editors, valuing awareness of when, how, and where AI was used. Benefits included understanding collaborators' thinking and verifying AI-generated text, though some found full sharing intrusive and self-conscious.

Do university AI policies actually protect what credentials mean?

An audit of 30 universities found policies clearly classify allowed AI use but rarely specify what evidence and safeguards show a credential still certifies learning. Permission categories alone cannot protect the validity of credentials.

When do users stop checking whether AI output is actually backed?

Users systematically accept AI outputs without verification because checking is costly and fluent output builds false confidence. This receiver-side surrender—measured in studies showing 80% unchallenged adoption—is what enables inflationary token systems to function at scale.

Papers this line draws on 8

The research behind the notes this line reads — ranked by how closely each paper relates.