AI can help scientists publish less
Abstract: We can do more than defend science from a flood of AI-assisted papers. Used well, AI offers a historic opportunity to correct distortions in the publication system, help us publish fewer and better papers, and give scientists back the time to do their best work.
Paper Prompts
Sign up for free to create and run prompts on this paper using GPT-5.
Top Community Prompts
Explain it Like I'm 14
A simple explanation of “AI can help scientists publish less”
Overview: What is this paper about?
This paper argues that AI can make science better by helping researchers publish fewer, higher‑quality papers. Today, it’s getting much easier and cheaper to write papers with AI, but it’s not any faster to carefully read, check, and judge them. If we don’t fix this imbalance, the scientific record could be flooded with more papers than people can properly review. Used well, AI can reduce busywork, make important non-paper work visible (like code and data), and support fairer, smarter evaluations—so scientists have more time to do their best thinking.
Key questions the paper asks
- What happens when writing papers becomes cheap and fast, but reading and reviewing them stays slow and human?
- Can AI help fix the problems caused by pressure to “publish more”?
- How can AI help us recognize valuable scientific work that’s not a traditional paper (like software, datasets, or careful replications)?
- What changes do we need—in tools and in rules—to use AI to improve science rather than overwhelm it?
How the author makes the case (methods and approach)
This is a thinking and analysis piece, not a lab experiment. The author:
- Points to real trends: AI tools speed up planning, coding, and writing, while peer review (experts checking papers) is already overloaded.
- Uses a simple comparison: it’s like homework getting easier to write, but grading staying just as hard; teachers get buried.
- Explains a key idea, “negative epistemic value”: a paper can be harmful to knowledge not because it’s wrong, but because it costs more attention to read and place in context than the value it adds.
- Draws on studies about falling disruptiveness in science (fewer big breakthroughs), the peer‑review crunch, and classic ideas from philosophy of science about how fields grow.
Quick definitions:
- Epistemic = related to knowledge.
- Peer review = experts read and judge a paper before it’s published.
- Incremental work = small, careful steps forward (which can be very useful).
- Triage = early sorting to decide what needs deep review and what doesn’t.
Main points and why they matter
The author says the real danger is an imbalance: AI makes it easy to produce more papers, but it doesn’t make it easier to fairly judge them. That can bury important work under a pile of “urgent‑but‑not‑important” writing.
Used well, AI can flip from “poison” to “medicine” in three practical ways:
- Recognize valuable work beyond papers
- Many scientists create code, datasets, benchmarks, and reproducible notebooks. These matter, but committees often only “count” the paper that describes them.
- AI can help present these contributions clearly—showing what they do, who uses them, and their impact—so they can be recognized directly, not only through a paper.
- Give scientists back time
- AI can handle routine chores: mapping the literature, scaffolding code, checking reproducibility, comparing related work, and drafting summaries.
- With less busywork, scientists can focus on tough questions, explore new ideas, and stop weak paths sooner—without worrying that fewer papers will hurt their careers.
- Strengthen evaluation and peer review
- AI can help editors and panels with early checks: novelty, overlaps, basic consistency, and obvious pitfalls—so scarce human attention is spent where it matters most.
- Judgment stays human, but AI reduces low‑level labor, lowering the risk that the system gets clogged by low‑value submissions.
A key lesson: “Publish less” does not mean “do less science.” It means:
- Reward more types of real contributions (code, data, careful replications) on their own terms.
- Reduce papers whose attention cost is higher than their knowledge benefit.
- Make space for careful, significant work.
What needs to change to make this work
To get the good outcomes, two big shifts are needed:
- Build public, trustworthy AI for science
- Create shared, open infrastructure (like big scientific labs do) with transparent models, open knowledge bases, and tools that support review and evaluation.
- Don’t rely only on private systems whose goals may not align with science’s goals.
- Update how we judge researchers
- Move beyond “how many papers?” and journal prestige.
- Use narrative CVs and recognize non-paper outputs as first‑class contributions.
- Adopt a “responsible publication” norm: judge whether a paper’s value is worth the community attention it will consume. Fewer papers can be a sign of maturity, not laziness.
The paper also invites philosophy of science back into everyday scientific decisions, with questions like: Is a field truly deepening or just multiplying? Are we making real progress or just continuing a crowded line of work?
Simple conclusion: Why this matters
If we use AI carelessly, it will flood science with more papers than people can fairly review, wasting attention and slowing real progress. If we use AI wisely, it can:
- Lift routine burdens from scientists,
- Make important non-paper work visible and valued,
- Help reviewers focus on what truly deserves attention,
- And encourage a culture that prizes significance and good judgment over sheer volume.
That way, AI doesn’t just defend science from overload—it helps make science, and scientists’ lives, better.
Knowledge Gaps
Unresolved gaps, limitations, and open questions
Below is a concise list of concrete gaps and open questions the paper leaves for future research and policy experimentation.
- Define and operationalize “negative epistemic value”: develop metrics that estimate attention cost versus knowledge gain at the paper, project, and field levels; establish actionable thresholds and validate them on real corpora.
- Measure AI’s causal impact on publication volume, review load, and disruptiveness: run institutional pilots, quasi-experiments, and time-series analyses across multiple disciplines.
- Design and test “responsible publication” criteria: field-specific rubrics and norms that weigh community attention costs; evaluate effects on innovation, equity, and career outcomes.
- Build and benchmark AI-assisted editorial triage: quantify accuracy of novelty/overlap detection and technical consistency checks; report false accept/reject rates, bias profiles, and calibration.
- Compare governance models for public scientific AI infrastructure: consortia vs distributed federations; funding, accountability, sustainability, and inclusive global participation.
- Specify requirements for transparent, community-run AI models: data provenance, documentation, reproducibility tooling, compute/energy footprints, and reference implementations.
- Create standards/interfaces that render code, data, and benchmarks legible without papers: interoperable metadata schemas, dependency/provenance graphs, usability metrics, PIDs, and versioned credit.
- Establish robust credit and evaluation frameworks for non-paper outputs: extensions to CRediT/ORCID, citation standards, usage/impact indicators acceptable to hiring and grant committees.
- Redesign incentives for hiring, promotion, and funding: policies that reward fewer, higher-contribution outputs; prospective trials assessing impacts on early-career researchers and field mobility.
- Anticipate and mitigate gaming/perverse incentives in new metrics and AI tooling: auditability, red-teaming, transparency standards, and community oversight mechanisms.
- Characterize disciplinary and regional heterogeneity: comparative studies across STEM/SSH, clinical vs basic research, Global South/North, and multilingual/non-English literatures.
- Guard against automation bias in review: protocols to sustain human judgment, explainability/traceability requirements for AI flags, and clear appeal mechanisms.
- Clarify authorship, credit, and accountability when AI contributes: disclosure standards, contributorship taxonomies, and responsibility allocation for errors or misconduct.
- Resolve legal/IP issues for training and deploying public AI on scientific corpora: licensing pathways, data protection, publisher contracts, and fair-use exceptions across jurisdictions.
- Secure and scale AI-enabled reproducibility checks: safe code execution (sandboxing), dependency management, cross-language/domain coverage, and reporting standards for verification outcomes.
- Ensure sustainable maintenance of “living syntheses” and infrastructure: funding/stewardship models, long-term archiving, governance of updates, and sunset criteria.
- Realign publisher economics with lower volume: evaluate business models (overlay journals, diamond OA, subscribe-to-open) that decouple revenue from publication counts.
- Quantify community “attention budgets” and review capacity: formal models of reviewer supply/demand, incentive experiments for reviewing, and market-design approaches.
- Distinguish salami-slicing from legitimate incrementalism: operational markers, linkage to replication/robustness evidence, and improved similarity/lineage analyses for text, code, and data.
- Manage preprint proliferation without suppressing openness: layered triage, transparent evaluation badges, community-curation tools integrated with archives.
- Standardize benchmarks for AI used in evaluation workflows: domain-specific test suites, adversarial stress tests, and continual-evaluation protocols.
- Assess environmental impacts of the proposed AI infrastructure: lifecycle analyses, energy/carbon targets, and trade-offs with openness and access goals.
- Integrate and evaluate research assessment reforms (e.g., COARA) under AI-saturated conditions: implementation case studies, KPIs, and scalability across institutions.
- Operationalize philosophy-of-science constructs for practice: measurable indicators of progressive vs degenerative research programmes usable by panels and funders.
- Track longitudinal effects on diversity, risk-taking, and career mobility: cohort studies through policy changes, impacts on field switching, and outcomes for underrepresented groups.
Practical Applications
Immediate Applications
Below are concrete, deployable use cases that translate the paper’s recommendations into tools, workflows, and policy tweaks across sectors. Each item notes sectors and key dependencies that may affect feasibility.
- AI-assisted editorial and grant triage — sectors: academia, publishing, policy/funding
- Use AI for novelty checks, literature comparison, reference validation, and technical consistency to prioritize human review where it matters most.
- Tools/workflows: editor dashboards; similarity/overlap detectors; automated checklists for reporting standards; grant pre-screeners.
- Dependencies/assumptions: human-in-the-loop oversight; transparent, auditable models; access to open bibliographic/metadata sources; safeguards against bias and false negatives.
- Artifact-first visibility portals for code/data/benchmarks — sectors: academia, software, ML, open science
- Deploy “living” AI interfaces that read repositories (e.g., GitHub, Zenodo) to auto-generate documentation, usage examples, dependency graphs, and impact traces.
- Tools/workflows: AI-generated READMEs, API docs, provenance graphs; DOI linkage; artifact “impact” dashboards.
- Dependencies/assumptions: repository access; FAIR metadata; persistent identifiers; acceptance by evaluation committees.
- Reproducibility agents in continuous integration — sectors: academia, software, healthcare/biomed R&D
- Automate notebook execution, environment recreation, and methods cross-checking during submission or release.
- Tools/workflows: GitHub Actions + containerized pipelines; LLM agents for parameter sanity checks; checklists for reporting completeness.
- Dependencies/assumptions: containerization or workflow standards (e.g., RO-Crate); compute budgets; data licensing and privacy.
- Lab “attention budget” dashboards — sectors: academia, industry R&D, daily scientific work
- Track time spent reading/reviewing vs. expected knowledge gain to prioritize fewer, higher-value outputs and collaborations.
- Tools/workflows: literature intake meters; lab-level Kanban with attention-cost scoring; personal reading copilots.
- Dependencies/assumptions: alignment with lab policies and evaluation norms; privacy-aware telemetry; culture that values quality over volume.
- Narrative CV and portfolio assembly — sectors: academia, hiring/promotion
- Auto-curate a candidate’s code, data, benchmarks, and syntheses into narrative CVs aligned with research assessment reform (e.g., COARA).
- Tools/workflows: artifact aggregation; impact/context summaries; reviewer-facing portfolio links.
- Dependencies/assumptions: committees willing to credit non-paper outputs; verification of artifact provenance; clear disclosure of AI assistance.
- Targeted literature mapping and scoped syntheses — sectors: academia, pharma/biotech, energy, finance R&D
- Rapidly produce scoped state-of-the-art maps that surface gaps and duplications, enabling early abandonment of dead ends.
- Tools/workflows: LLM-based literature graphs; claim-by-claim comparison; contradiction and replication detectors.
- Dependencies/assumptions: access to open and proprietary content (license-compliant); evaluation of model hallucination; domain calibration.
- Benchmark curation and de-duplication — sectors: ML, robotics, software
- Use AI to scan for redundant benchmarks, identify coverage gaps, and document evaluation pitfalls.
- Tools/workflows: benchmark registries with AI curators; coverage/novelty heatmaps.
- Dependencies/assumptions: community participation; machine-readable metadata; agreement on quality criteria.
- Internal R&D proposal and study de-duplication — sectors: pharma, healthcare systems, energy, finance
- AI flags overlap with internal/external work, estimates marginal knowledge gain vs. effort, and suggests consolidation.
- Tools/workflows: secure on-prem LLMs; similarity-to-portfolio scoring; VOI (value-of-information) heuristics.
- Dependencies/assumptions: data security; change management; leadership buy-in to reduce redundant projects.
- Preprint/server-side low-value duplication alerts — sectors: publishing, open science
- Provide authors and moderators with overlap and redundancy reports at submission to discourage incremental duplicates.
- Tools/workflows: cross-repository similarity scanners; author-facing “attention-cost” statements.
- Dependencies/assumptions: transparent, opt-in deployment; clear appeals process; community governance to avoid gatekeeping.
- Course modules and AI tutors on “significance over volume” — sectors: higher education, professional development
- Embed training on attention cost, replication value, and responsible publication in graduate curricula and lab onboarding.
- Tools/workflows: interactive cases; AI tutors that simulate editorial triage and reviewer tradeoffs.
- Dependencies/assumptions: curricular flexibility; faculty champions; assessment alignment with new norms.
Long-Term Applications
The following opportunities require further development, scaling, coordination, or policy change, but directly operationalize the paper’s vision.
- Public scientific AI infrastructure — sectors: policy, academia, national labs
- Create CERN/EMBL-like or distributed consortia providing public compute, community-hosted transparent models, and open knowledge bases for science.
- Tools/products: open, auditable LLMs tuned for scientific tasks; curated public corpora; reviewer support stacks.
- Dependencies/assumptions: sustained public funding; international governance; IP/licensing solutions; robust privacy/security.
- Cross-publisher evaluation signals and shared triage services — sectors: publishing, funders
- Interoperable AI services for novelty/consistency signals that travel with manuscripts and grants across venues to reduce redundant review.
- Tools/workflows: standardized “review signal” schemas; APIs for editorial systems; audit trails.
- Dependencies/assumptions: data-sharing agreements; common standards; incentives for publishers to collaborate.
- Artifact-centric hiring and promotion systems — sectors: academia, industry R&D
- Formalize credit for code, datasets, benchmarks, reproducibility packages, and living syntheses as first-class outputs.
- Tools/products: portfolio platforms with verifiable artifact provenance and usage; committee training modules; rubric redesign.
- Dependencies/assumptions: reassessment of tenure criteria; community norms; anti-gaming safeguards.
- Attention-cost-aware publication norms — sectors: academia, publishing, policy
- Adopt “responsible publication” criteria that weigh expected knowledge gain against community attention demanded.
- Tools/workflows: author’s attention-cost justification; reviewer prompts on incremental value; field-level attention budgeting.
- Dependencies/assumptions: consensus on metrics; field-specific baselines; monitoring for perverse incentives.
- Living, AI-updated syntheses and dynamic reviews — sectors: publishing, healthcare guideline bodies
- Replace static reviews with continuously updated, versioned syntheses that surface what changed and why.
- Tools/products: version-controlled review platforms; change-logs tied to new evidence; clinician-facing digests.
- Dependencies/assumptions: stable funding models; citation/versioning standards; editorial accountability.
- Provenance-rich artifact graphs and standards — sectors: software, ML, open science infrastructure
- Standardize machine-readable metadata to link artifacts to downstream usage and impact (e.g., RO-Crate, schema.org extensions).
- Tools/workflows: “Artifact Impact Graphs” for hiring, compliance, and reproducibility; cross-repo provenance resolvers.
- Dependencies/assumptions: standards adoption; persistent identifiers; community curation.
- Registries for null results, replications, and negative findings — sectors: healthcare/clinical research, psychology, social science
- AI-curated registries that summarize and connect null/replication outcomes to reduce redundant trials and publications.
- Tools/products: structured registries with LLM summaries; contradiction maps; funder-integrated reporting.
- Dependencies/assumptions: policy mandates; cultural value for null results; data-sharing frameworks.
- Knowledge-value and VOI models for prioritization — sectors: meta-science, funders, industry portfolio management
- Quantitatively estimate expected marginal epistemic value vs. attention/effort costs to guide funding and review allocation.
- Tools/workflows: Bayesian VOI models; field-specific priors learned from historical outcomes; decision dashboards.
- Dependencies/assumptions: high-quality outcome data; model transparency; acceptance of probabilistic decision-making.
- Integrated training in philosophy of science with AI tools — sectors: education, professional societies
- Use AI to teach and operationalize concepts like progressive vs. degenerative research programmes for evaluation practice.
- Tools/products: case-based AI tutors; evaluation playbooks; reflective practice modules for reviewers and panels.
- Dependencies/assumptions: curricular space; interdisciplinary faculty; assessment alignment.
- Legal, ethical, and audit frameworks for AI-mediated review — sectors: policy, publishing, legal/compliance
- Define accountability, contestability, bias auditing, and record-keeping for AI use in scientific evaluation.
- Tools/workflows: audit logs; bias/robustness benchmarks; appeals and redress mechanisms.
- Dependencies/assumptions: regulatory clarity; cross-jurisdiction harmonization; resources for oversight.
These applications collectively aim to rebalance the cost of producing vs. evaluating scientific work, recognize non-paper contributions, and reserve scarce human attention for the most epistemically valuable efforts—delivering fewer, better papers and more time for deep science.
Glossary
- attention cost: The time and cognitive effort the research community must expend to read, review, and integrate a work. "attention cost exceeds their contribution to knowledge."
- code scaffolding: Automatically generating boilerplate or structural code to speed up development. "literature mapping, code scaffolding, documentation, reproducibility checks"
- curated benchmarks: Carefully assembled and maintained datasets or tasks used to fairly compare methods across studies. "such as code on GitHub, data on Zenodo, curated benchmarks, public notebooks, reproducibility packages, and living syntheses."
- disruptiveness: A bibliometric notion indicating how much a work displaces prior approaches rather than building directly on them. "declining disruptiveness6,7,"
- evaluation panels: Committees that assess submissions or proposals for journals, institutions, or funders. "helping editors, evaluation panels, and funders"
- front end of review: The initial screening and pre-assessment phase before full, in-depth peer review. "strengthen the front end of review"
- journal impact factors: Citation-based metrics estimating the average citations received by articles in a journal; often (controversially) used as a proxy for quality. "away from journal impact factors,"
- literature mapping: Systematically surveying and organizing existing research to understand a field’s structure and gaps. "literature mapping, code scaffolding, documentation, reproducibility checks"
- living interface: An interactive, continuously updated interface that explains, demonstrates, and contextualizes a research artifact. "a living interface that shows what it does, how it is used, what depends on it, and what difference it has made."
- living syntheses: Continuously updated overviews that synthesize and integrate findings across a research area. "such as code on GitHub, data on Zenodo, curated benchmarks, public notebooks, reproducibility packages, and living syntheses."
- narrative CVs: Researcher CVs emphasizing qualitative narratives of contribution and impact over purely quantitative metrics. "toward narrative CVs,"
- negative epistemic value: When a publication detracts from collective understanding because it consumes more evaluative attention than knowledge it adds. "scientific papers can acquire negative epistemic value:"
- normal science: Kuhn’s term for routine puzzle-solving within an accepted paradigm during non-revolutionary periods of science. "Kuhn described mature research as "normal science","
- novelty checks: Procedures to assess whether a submission’s ideas or results are genuinely original relative to existing literature. "with triage, novelty checks, literature comparison"
- null result: A finding showing no effect or failure to confirm a hypothesized relationship. "a null result that closes off an appealing but ultimately wrong hypothesis."
- pharmakon: A concept from Greek philosophy meaning something that is both a remedy and a poison. "writing appears as a pharmakon: both a remedy and a poison."
- replication: Repeating a study or experiment to verify whether its results are robust. "a replication that clarifies whether a result is robust,"
- reproducibility checks: Verifications that independent researchers can reproduce results using provided code, data, and procedures. "literature mapping, code scaffolding, documentation, reproducibility checks"
- reproducibility packages: Bundled code, data, and instructions that enable others to fully reproduce a study’s results. "such as code on GitHub, data on Zenodo, curated benchmarks, public notebooks, reproducibility packages, and living syntheses."
- research programme: In Lakatos’s philosophy, a structured line of inquiry appraised as progressive or degenerative over time. "Is a research programme progressive or degenerative?"
- systematic uncertainties: Non-random errors stemming from measurement or methodological biases that affect results consistently. "a careful reanalysis of systematic uncertainties,"
- triage: Prioritizing and filtering submissions to allocate review resources to the most promising or relevant ones. "with triage, novelty checks, literature comparison"
- Zenodo: An open-access repository for research outputs (e.g., datasets, software), supported by CERN/OpenAIRE. "data on Zenodo"
Collections
Sign up for free to add this paper to one or more collections.