Tag: GenAI

  • CRediT for AI-generated content: where the line is

    The ICMJE 2023 position is settled: artificial-intelligence systems cannot be authors. The follow-on question that journals and authors continue to negotiate is how to represent, in a contributorship statement, the human work that goes into producing AI-assisted content. When a co-author prompts an LLM to draft a section, verifies the output, edits it, and stands behind it, which CRediT role describes their contribution? This post proposes a working line.

    The shape of the question

    Three scenarios make the question concrete.

    Scenario one: an author uses an LLM to polish prose in a draft they wrote. The intellectual content is theirs; the language is partly the model’s. The CRediT role is straightforwardly Writing – original draft for the author.

    Scenario two: an author uses an LLM to draft a first version of a section, which they then heavily revise. The first draft is the model’s; the final draft is the author’s, but the model substantively shaped what the final draft says. The CRediT role is still Writing – original draft for the author, but the contribution is meaningfully different from scenario one.

    Scenario three: an author uses an LLM to propose a study design, which they then refine. The intellectual content of the methodology was partly the model’s. The CRediT role is Methodology for the author, but again the contribution is meaningfully different from the unaided version.

    In all three, the human author is the role-holder; the model is not a co-author. What is different across the scenarios is the magnitude and the character of the human contribution. CRediT, as currently constituted, does not distinguish these.

    The working line

    Our proposed line is the verification-and-responsibility threshold. A human contributor who has substantively verified the AI-generated content, taken responsibility for it, and is prepared to defend it in correspondence or post-publication discussion is properly credited with the relevant CRediT role. The role describes what they contributed to the paper, which includes verification work even if the first-draft work was the model’s.

    The line shifts where the human contribution is insubstantial — a contributor who pasted a prompt, accepted the output without verification, and added their name to the paper has not discharged the role and should not be credited. This is the same line that has always applied to non-AI cases (a co-author who did not contribute should not be credited; gift authorship is a well-recognised failure mode).

    The line is therefore not about AI use per se; it is about whether the human contribution clears the substantive-contribution threshold. AI use does not displace the threshold; it changes what discharging the role looks like in practice.

    Disclosure runs parallel

    The disclosure of AI use is a separate question, addressed via publisher-mandated AI disclosure declarations. The disclosure says what tools were used and for what; the CRediT statement says who contributed what to the paper. The two run parallel and are both required by most major publishers in 2026. The CASRAI AI disclosure for authors guide walks through the publisher-by-publisher requirements.

    Implications for specific roles

    Writing – original draft

    The most common case. A human author whose draft was AI-assisted is properly credited with Writing – original draft if they verified the content, took responsibility for it, and produced the version that is the paper. The disclosure declaration says the AI was used; the CRediT statement names the human as the writer-of-record.

    Methodology and Formal analysis

    More delicate. If an AI-assisted statistical-discovery tool proposed a method or an analytic approach, the human contributor’s role is partly verification (was the proposal sound?) and partly extension (refining the proposal into the actual method). The CRediT role is still Methodology and/or Formal analysis for the human, but the verification dimension is foregrounded. If the human did not verify — accepted the AI proposal without independent assessment — the contribution is weaker and may not clear the role threshold.

    Investigation

    A subtle case. AI-assisted data extraction (e.g., from imaging, from medical records, from text corpora) involves a human contribution that runs from setup through verification to interpretation. Investigation includes the data-gathering activity; an AI-assisted version still has a human Investigation lead, who is responsible for the setup, the verification of extracted data, and the handling of errors.

    Validation

    Perhaps the most directly affected. Where AI tools are used for cross-checking, sensitivity analyses, or reproduction of results, the human Validation contributor is responsible for setting up the validation, interpreting its results, and acting on discrepancies. The AI does the mechanics; the human does the judgement.

    Visualization

    AI-assisted figure generation is increasingly common. The human Visualization contributor is responsible for the figure-design decisions, for verifying that the AI-generated figure accurately represents the data, and for the final version that appears in the paper. Where the AI generated an image that the human did not substantively verify, the threshold may not be cleared.

    The role-as-recognition trap

    A failure mode to flag explicitly. The temptation, when AI did most of the actual production work, is to inflate the human contributor’s role assignment to compensate. “The AI wrote the draft, but I prompted it, so I should still be Lead on Writing – original draft.” This is a misreading. The CRediT role is a description of contribution; if the human contribution was “prompted and accepted”, that is a smaller contribution than “drafted, verified, revised, took responsibility.” Calling both “Lead” obscures the difference.

    The remedy is the degree-of-contribution qualifier. A human contributor whose AI-assisted contribution was substantial may be Lead; one whose contribution was lighter may be Supporting. The qualifier discipline forces an honest assessment of magnitude.

    Where this leaves the AI-assistance-role question

    We have argued elsewhere that a 15th CRediT role explicitly for AI assistance is worth considering. The argument from this post is partly orthogonal: the existing 14 roles can accommodate AI-assisted work if the verification-and-responsibility threshold is honoured and the qualifier is used honestly. The case for a 15th role rests on whether the structured disclosure-of-AI-use is better placed inside the contributorship statement or outside it. Reasonable people disagree; we lean toward keeping AI disclosure parallel to CRediT rather than inside it, with attention to the verification-and-responsibility line.

    Practical recommendations

    Three for authors. First, treat AI assistance as a tool, not a substitute. Verify, edit, and take responsibility for what appears in the paper. Second, assign CRediT roles based on what you contributed including verification, not based on what the AI produced. Third, disclose AI use in the publisher-mandated declaration; the disclosure runs parallel to CRediT, not inside it.

    Three for editors. First, treat the verification-and-responsibility threshold as the operating standard for AI-assisted contributorship. Second, require both the CRediT statement and the AI-use disclosure at submission. Third, where a contributorship statement looks like it may reflect AI-assistance role inflation, ask the standard editorial question: what did this contributor actually do?

    Three for the broader system. First, harmonise AI-disclosure formats across publishers (work the NISO and COPE community has begun). Second, maintain the contributorship-versus-disclosure separation; do not collapse them. Third, evaluate the case for a 15th CRediT role on its merits, including the costs of taxonomic expansion.

    Related dictionary entries

  • Making sense of the EU AI Act for research administration

    The EU Artificial Intelligence Act entered into force in August 2024 with a staged implementation timeline that runs through 2027. By February 2025 the prohibited-AI-practices provisions and the AI-literacy obligation became binding; through 2025 the general-purpose-AI provisions came into effect; in 2026 the high-risk-AI obligations begin to apply; in 2027 the act is fully in force. Research-administration offices across Europe (and at non-EU institutions handling EU data subjects or EU collaborators) have been working through the implications. This post is a practical orientation, not legal advice, on what the act requires of research administration in 2026.

    What the act actually covers

    The EU AI Act is risk-tiered. Prohibited practices (social scoring, real-time biometric identification in public spaces with narrow exceptions, exploitative manipulation) are out, full stop. High-risk AI systems — defined in Annex III to include AI used in education, employment, law enforcement, critical infrastructure, and several other domains — face substantial obligations around risk management, data governance, technical documentation, transparency, human oversight, accuracy, and post-market monitoring. Limited-risk AI (chatbots, emotion-recognition systems, AI-generated content) faces transparency obligations. Minimal-risk AI faces none specific to the act.

    The research-specific carve-outs are important but narrower than is sometimes claimed. The act excludes AI systems and models developed solely for the purpose of scientific research and development; it does not exclude AI systems used in the conduct of research that is not itself AI research. A clinical-trial protocol that uses an AI system for patient stratification is not exempt because it is research; the AI system is being deployed in a context (healthcare) covered by the act. The exemption is for AI as an object of study, not AI as a tool of study.

    Where research-administration touches the act

    Five touchpoints in practice.

    1. AI literacy obligation

    Article 4 requires providers and deployers of AI systems to take measures to ensure a sufficient level of AI literacy of their staff and others using AI systems on their behalf. This applies to research-administration staff using AI tools (proposal-screening assistants, plagiarism detection with AI components, AI-assisted compliance review). The required “sufficient level” is not specified in detail; the European AI Office and national competent authorities are expected to publish guidance. The CASRAI EU AI Act entry tracks the guidance as it emerges.

    Practically, institutions should be running AI-literacy training for research-administration staff in 2026. This need not be elaborate; an annual two-hour training covering what AI systems the institution uses, what their limitations are, what the disclosure obligations are, and where to escalate concerns is a defensible baseline.

    2. High-risk AI in education and employment

    Annex III includes AI systems used in education (admissions decisions, student assessment, allocation to programmes) and in employment (recruitment, performance evaluation, task allocation). University admissions offices using AI to triage applications fall within high-risk; research-administration offices using AI to score research proposals likely do not, but the boundary is being tested. Employment decisions about research staff — using AI to rank job applicants or to score performance for promotion — clearly fall within high-risk.

    For research administration, the practical question is whether any AI system in current or planned use crosses the threshold. The compliance checklist runs: identify all AI systems in use; categorise each against the act; for high-risk systems, conduct a fundamental-rights impact assessment; ensure human oversight is meaningful, not nominal; document the risk-management system; register in the EU database.

    3. GenAI transparency obligations

    Article 50 requires that AI-generated content be marked as such, with limited exceptions. For research administration, this affects AI-generated text in proposal review, AI-generated summaries of compliance documents, AI-generated translations of regulatory text. Where AI is used to generate content that will be read by a human as if it were human-produced, the act requires a marker.

    This dovetails with the publisher-led GenAI disclosure conventions for scholarly content. The CASRAI institutional GenAI disclosure guidance integrates the publisher requirements and the EU AI Act obligations into a single workflow.

    4. Data governance and GDPR alignment

    The AI Act intersects extensively with the GDPR. High-risk AI systems must use training, validation, and testing data sets that are relevant, sufficiently representative, free of errors, and complete. For systems trained on personal data, the GDPR’s purpose-limitation and minimisation principles apply alongside the AI Act’s data-governance requirements. Research administration that procures or deploys AI systems should ensure the AI vendor can document training-data provenance and consent status for any personal data used.

    5. Research-exemption boundary cases

    The research exemption is being tested at the boundary. A university research group developing an AI system as their research output is exempt; the same group using the system in a clinical context with EU patients is not. A university operating a public-facing AI service developed in-house is a provider under the act and subject to the full provider obligations even if the development was research. The European AI Office has indicated it will publish boundary guidance through 2026; until it does, the conservative reading is that any AI use outside the development phase brings the act into play.

    The compliance checklist

    The practical 2026 checklist for a research-administration office:

    • Inventory all AI systems in use or planned use across research administration.
    • Categorise each system against the AI Act risk tiers.
    • For high-risk systems, conduct a fundamental-rights impact assessment.
    • For GenAI use, ensure transparency markers are applied to AI-generated content.
    • For employment-decision systems involving research staff, ensure human oversight is documented and meaningful.
    • Run AI-literacy training for relevant staff.
    • Verify that AI vendors can document training-data provenance and consent.
    • Align AI Act compliance with GDPR processes; do not run parallel programmes.
    • Track guidance from the European AI Office and national competent authority.
    • Document everything; the act’s audit posture is documentation-heavy.

    Non-EU implications

    The act’s extraterritorial reach matters for non-EU institutions. If an institution outside the EU operates an AI system whose output is used in the EU, the act applies. A US university running AI-assisted admissions for an EU campus, a UK research administration office using AI to triage proposals from EU collaborators, a Canadian institution running a GenAI service available to EU users — all may fall within the act’s scope. Non-EU institutions with material EU engagement should run the same compliance checklist as EU institutions.

    What’s still uncertain

    Several material questions remain open through 2026 and will be resolved by Commission guidance, national-authority interpretation, or early case law. Where does the boundary of “research and development” sit? How is “sufficient level of AI literacy” measured? What documentation suffices for the fundamental-rights impact assessment? How does the act interact with existing sectoral regulation (clinical-trials regulation, education-sector law, employment law) in member states? The CASRAI compliance and regulatory domain is tracking these questions and publishing updates as guidance emerges.

    For now, the operating posture for research administration is: take the inventory; do the risk-tiering; document the high-risk systems; run the literacy training; treat the act as a serious ongoing compliance programme, not a one-off exercise. The penalties under the act are substantial and the enforcement architecture is being built; the institutions that started in 2024-2025 are well placed, those that haven’t started should begin now.

    Related dictionary entries

  • Why the next CRediT version should include ‘AI assistance’ as a role

    The 14 roles of CRediT were designed in 2013-2014 with a model of contribution that did not include large language models or generative AI systems. A decade on, the taxonomy is robust and widely adopted, but the AI question is hard to ignore. This post makes the case — tentatively, and with attention to the counter-arguments — that the next CRediT revision should add a 15th role explicitly covering AI assistance. We are publishing it here to invite community pushback before any formal proposal goes to the CRediT stewardship group.

    Why this question is not solved by disclosure alone

    The current consensus around generative AI in scholarly authorship rests on two pillars: AI cannot be a co-author (the ICMJE 2023 position), and AI use must be disclosed in a structured declaration. CASRAI agrees with both. They do not, however, resolve the question of how AI assistance shows up in CRediT.

    A worked example. Suppose a paper has four authors. Author A wrote the first draft with substantial assistance from a large language model, which she prompted, edited, fact-checked, and revised. Author B ran the formal analysis using an AI-assisted statistical-discovery tool that proposed model specifications. Author C generated several of the figures using a GenAI visualisation tool. Author D supervised. Each used AI; each used it differently; each took human responsibility for the output. How does the CRediT statement represent this?

    Under current CRediT, AI use is invisible. Author A gets Writing – original draft (lead). Author B gets Formal analysis (lead). Author C gets Visualization (lead). Author D gets Supervision. The AI assistance shows up only in the publisher-mandated AI disclosure, which is a free-text field in the methods or acknowledgements. The structured contributorship record has no place for the granular fact that AI was a tool in each of those role-discharges.

    The proposed 15th role

    The draft scope we are testing is this:

    AI assistance. The use of artificial-intelligence systems, including generative AI, machine-learning models, and automated analytical tools, in the production of the work. Includes prompt engineering, model selection, validation of AI output, and human verification of AI-generated content. Does not include use of AI as a routine tool (e.g., grammar checkers, citation-formatting tools) below a disclosure threshold defined by the publisher.

    The role would carry the standard degree-of-contribution qualifier. A human author whose primary contribution was prompting and verifying an AI system would be marked Lead for AI assistance; a co-author who occasionally checked AI outputs would be Supporting. The role would not be a substitute for the existing roles — the human who used AI for the first draft still gets Writing – original draft — but it would add the structured fact that AI was involved.

    The arguments for

    First, structured disclosure is more useful than prose disclosure. A free-text AI declaration cannot be queried, cross-referenced, or aggregated. A CRediT-style structured role can. Integrity offices investigating a fabrication can query for papers with AI assistance roles; funders tracking AI use in grant outputs can roll up the data; bibliometric studies can analyse patterns. None of this is possible with the current free-text disclosure.

    Second, granularity matters for accountability. Knowing that a paper used AI is less useful than knowing which contributor used AI for which task. The CRediT role assignment makes the accountability specific. If a fabricated reference appears in the introduction, the question of who is responsible for verifying it has a structured answer.

    Third, the boundary is becoming a fiction. Modern statistical workflows include AI components (autoML, AI-assisted exploratory analysis); modern writing workflows include AI components (Copilot for prose, Claude for editing); modern visualisation workflows include AI components. The pretence that these are separable from the role they support is increasingly hard to maintain. If AI is being used to discharge a role, the role assignment should say so.

    The arguments against

    Three serious counter-arguments deserve engagement.

    First, the scope-creep concern. CRediT has held to 14 roles deliberately. Each addition raises the cognitive load on authors filling out the statement, increases the integration burden on publishers, and risks the taxonomy becoming unusable through over-specification. The argument from Liz Allen and the original CRediT designers has been that the taxonomy gains its value from being small enough to use.

    Second, the boundary problem. What counts as AI assistance? A grammar checker is plausibly AI; a citation formatter increasingly is; a search engine ranking results by relevance certainly is. If every modern research tool counts as AI, the role becomes meaningless. A workable scope requires a non-trivial threshold (the draft language above gestures at “below a disclosure threshold defined by the publisher”), and that threshold is hard to define without ending up with either everything or nothing.

    Third, the disclosure-versus-contribution distinction. CRediT is a contributorship taxonomy. AI is not a contributor — that is the settled position. Adding an AI role to CRediT risks blurring this. The alternative is to keep AI in a separate disclosure form, structurally similar to a competing-interests declaration or a funding statement, rather than in the contributorship statement.

    A possible middle path

    The middle path is to keep CRediT at 14 roles and to define a parallel AI assistance declaration with comparable structure: a controlled vocabulary of AI-use types, a per-contributor breakdown linked to ORCID iDs, a model-and-version field, and a verification statement. This would sit alongside CRediT in publisher submission systems and JATS XML, rather than inside it.

    This is closer to where the current publisher disclosure forms are heading, and it preserves the conceptual clarity that CRediT roles describe what humans did, while a separate declaration describes what AI tools were used. We are increasingly inclined to recommend this path, with the caveat that the disclosure must be structured to the same standard as CRediT — not free-text, with controlled vocabularies, deposited to Crossref, and surfaced on ORCID.

    What the CRediT stewardship group should do next

    Three concrete steps. First, run a structured community consultation through 2026 on whether to add AI assistance as a 15th CRediT role, with the alternative being a parallel structured declaration. The CRediT governance page outlines the consultation process. Second, in parallel, draft the data model for a parallel AI assistance declaration so that the comparison is concrete and not abstract. Third, coordinate with NISO on whether either option requires a revision to Z39.104.

    The decision is not urgent in the sense that the integrity system is failing today; the existing disclosure forms work, badly. It is urgent in the sense that every year of delay produces another year of unstructured AI-use data that cannot be aggregated or analysed, which makes the eventual transition harder.

    Related dictionary entries